Skip to main content

HX108 Market Data And Order Flow

HX108 teaches data provenance: which provider, instrument, clock, and source produced the rows on screen. That question must be answered before using chart, depth, or trade-print data for an order decision.

Lesson 1: Check The Capability Matrix

Provider names are not capability promises. In 1.1.10:

  • KuCoin and Rithmic expose current market-data and eligible account/routing paths, subject to credentials, entitlements, environment, and certification.
  • Hyperliquid market data is Current; wallet trading is Preview and unreleased for general live use.
  • Binance is Unavailable / Coming Soon for a clean supported setup. The connection picker is locked, and any legacy preconfigured state is not release-certified.
  • Jupiter, o1.exchange, and Tradovate are visible placeholders and unavailable.
  • DxFeed, Interactive Brokers, and CQG adapters are internal/legacy and not enabled in the supported picker.

Do not preserve this summary in an integration. Check Feature And Provider Status for the maintained matrix at the start of each test.

Lesson 2: Verify Instrument Metadata

Instrument metadata affects chart precision, order validation, sizing, PnL, margin, and historical results. Record:

  • provider symbol and venue
  • asset/contract type
  • base, quote, settlement, and currency fields that apply
  • tick size and price precision
  • minimum size and quantity step
  • multiplier and minimum notional
  • contract/expiry identity for futures

For crypto, distinguish Spot, Futures, and Perpetual products. Two rows with similar display symbols can have different quantity, margin, and routing rules.

Lesson 3: Label The Data Clock

For every observation, write down whether it came from:

  • stored historical data
  • live provider updates
  • Playback
  • a chart-derived price context
  • generated/sample fallback rows

Playback changes the data clock but not the selected account. In the current release-candidate build, Broker and Server Paper submissions, changes, and cancellations are rejected while Playback is active. Use an explicitly selected LocalPaper account and see Accounts And Trading Environments.

Lesson 4: Import History Without Losing Provenance

Use Historical Data And Import for the current file format and storage behavior. The key 1.1.10 checks are:

  1. Keep the original file and note its vendor and stated time zone.
  2. Import a short sample first.
  3. Review duplicates, gaps, out-of-order rows, and rejected lines.
  4. Compare chart timestamps with a trusted reference.
  5. Record that the visible time-zone selector is not passed to the parser for local tick imports.
  6. Record that the overwrite path merges by timestamp rather than guaranteeing a clean replacement.
  7. Validate any generated minute/day candles against the source ticks.

Do not hand-edit active market-data files while HyperionX is running.

Lesson 5: Prove Level II Provenance

Level II is Preview. When provider depth is unavailable, empty, or fails, the current window can populate generated price, size, timestamp, and side rows while also reporting an unavailable state.

Before reading a depth row:

  1. Confirm the connection and symbol shown by the window.
  2. Confirm that the provider supports depth for that market.
  3. Read the status and last-update time.
  4. Reject the view if it reports unavailable, fallback, empty, or stale state.

Visible rows are not sufficient proof of provider depth.

Lesson 6: Open Time And Sales From A Chart

Chart-linked Time and Sales is Current for ticks delivered by the active chart stream. Standalone or workspace-restored Time and Sales is Preview because it can open with seeded sample rows when no chart is attached.

  1. Click the intended chart.
  2. Open Time and Sales from that chart context.
  3. Confirm the instrument in the title.
  4. Confirm timestamps advance with the intended live or Playback clock.
  5. Compare a sample with another trusted provider view when the tape matters to a decision.

Do not use a standalone seeded view as a live tape.

Lesson 7: Use MegaDOM Carefully

MegaDOM is the public product name for the ladder/order-entry window. SuperDom is an internal class name, not a second public product.

MegaDOM can show provider depth where available and can fall back to chart price context when depth is unavailable. It routes orders directly to the selected account. Playback does not automatically select LocalPaper; the current release-candidate build rejects external-account order mutations while Playback is active.

Before touching an order control, verify:

  • provider and instrument
  • depth versus chart-derived price context
  • selected account and account type
  • quantity, time in force, and OCO preset
  • cancel/close/flatten procedure

Follow Market-Data Tools for the detailed safe-use checks.

Lesson 8: Know What A Workspace Restores

HyperionX 1.1.10 preserves instrument context for MegaDOM and Level II. It can reopen supported tool windows, but it does not preserve standalone Time and Sales instrument context, provider sessions, live orders, positions, running strategy state, or active research jobs.

After restoring a workspace, recheck every provider, symbol, timestamp, and account. See Save And Restore Workspaces for the complete state boundary.

Troubleshooting Order

When a market-data tool looks wrong, check:

  1. active chart and intended window
  2. provider connection
  3. instrument/contract identity
  4. live, historical, or Playback clock
  5. provider capability for history, ticks, or depth
  6. status and last update
  7. tick size, quantity precision, and multiplier
  8. fallback/sample state
  9. Logs and provider status

Completion Check

  • You can name the provider, instrument, clock, and provenance for every displayed row.
  • You can reject Level II fallback rows and standalone Time and Sales samples.
  • You can explain that MegaDOM may have price context without provider depth.
  • You can verify imported timestamps despite the current selector limitation.
  • You re-verify context after a workspace restore.