Skip to content
Docs

Market data

Where charts, trades, stats and holders come from: how the engine follows every NEAR block and what it builds from them.

The charts, trades, stats and holder counts in the terminal come from our engine. It reads every NEAR block, decodes the trades in it, and pushes the results to the terminal over a WebSocket. This data is for display only: the terminal signs nothing on the strength of it, and re-reads from the chain whatever a trade depends on (Prices and guardrails).

Following the chain

Section titled “Following the chain”

The engine reads blocks before they are final, which keeps the feed close to the chain’s head. The price of reading early is that a block can still drop out of the chain, and the engine has to notice when it does: it drops every trade first seen in such a block and rebuilds what was derived from those trades.

Contracts talk to each other through receipts, and a receipt runs on the shard of the account it is sent to (Nomicon: Receipts). So the engine decodes receipts, not transactions. A trade carries the time of the block its receipt ran in.

What the engine builds

Section titled “What the engine builds”
  • Candles at 1s, 15s, 30s, 1m, 5m, 15m, 1h, 4h and 1d.
  • Stats over rolling windows, from the raw trades.
  • Holders. For a token the engine has followed since its creation, an exact ledger of every transfer, mint and burn, reversed when a block is orphaned.
  • Token origin: which launchpad made a token, across 36 launchpad adapters, and never from a stored label.
  • Social: posts and profiles from X.

From swaps to candles

Section titled “From swaps to candles”

A candle comes only from trades decoded from the chain, each dated by its block. A trade’s price is NEAR per whole token, its volume is the NEAR leg, and its time is the block’s timestamp, not the moment the engine saw it. Times are in UTC, so a day candle starts at 00:00 UTC.

Because the build is a pure function of the trades in chain order, a rebuild gives the same candles that the live feed would have. A trade that turns up late is merged into its own bucket, so its open and close come out as if it had arrived on time.

Sources

  1. NEAR docs, NEAR Data Flow: a block is the chunks of all shards; a receipt runs on the receiver's shard (read 2026-10-15)
  2. Nomicon, Receipts: cross-contract calls are receipts; a postponed receipt waits for its data (read 2026-10-15)

Last verified 15 October 2026 against R4.