Docs
Docs
Home
Getting Started
Agent Tooling
CLI
Supported Chains
Acala
Aptos
Arbitrum
Arc
Asset Hub
Astar
Avalanche
Base
Berachain
Bifrost
Binance Smart Chain
Bittensor
Blast
Boba Network
Bridge Hub
Celo
Centrifuge
Chiliz
Cronos
Enjin
Ethereum
Etherlink
Flow EVM Gateway
Gnosis
Hydration
Hyperliquid
Immutable
Ink
IoTeX
Kusama
Linea
LISK
Manta Atlantic
Manta Pacific
Mantle
MegaETH
Monad
Movement
Neuroweb
opBNB
Optimism
Plasma
Polkadot
Polygon
Pulsechain
Robinhood
Ronin
Scroll
Sonic
Starknet
Taiko
Tempo
Sui
TRON
Unichain
Viction
World Chain
XDC Network
XX Network
Zetachain
zkSync Era
Zora
Supported ChainsHyperliquidData CatalogNode-written data

Hyperliquid TWAP Statuses - Node Data

Inspect node_twap_statuses_by_block files, lifecycle fields, sample data, and access methods.

Hyperliquid RPC endpoint: endpoint URLs, plans and pricing.

node_twap_statuses_by_block records lifecycle updates for time-weighted average price (TWAP) orders. Each event includes the TWAP identifier, current aggregate state, and lifecycle status.

Access

AvailabilityAccessDetails
Live / replayStreamTwapStatuses and GetTwapStatusesV3 selects with position.block_number or position.timestamp; Record.block_number and Record.timestamp are transport cursors. V3 supports the documented users and coins filters. V2 selects with block_height or timestamp_ms and returns source JSON bytes in BlockTwapStatuses.data; it does not use the V3 record fields or filter contract.
ArchivalS3 BucketS3 coverage for node_twap_statuses_by_block: 2026-07-01 to today, stored as hourly .lz4.

File layout

Text
node_twap_statuses_by_block/<YYYYMMDD>/<hour>.lz4

Files contain JSON block envelopes with TWAP lifecycle objects in events.

For download planning, see compressed size and file count. Measure TWAP statuses and fills separately for the same date range when you need both.

Sample data

JSON
{
  "local_time": "2026-01-01T00:00:00.100000000",
  "block_time": "2026-01-01T00:00:00.000000000",
  "block_number": 12345,
  "events": [
    {
      "time": "2026-01-01T00:00:00.000000000",
      "twap_id": 101,
      "state": {
        "coin": "kPEPE",
        "user": "<redacted-user>",
        "side": "B",
        "sz": "555555.0",
        "executedSz": "555555.0",
        "executedNtl": "1371.51378",
        "minutes": 5,
        "reduceOnly": false,
        "randomize": false,
        "timestamp": 1704067200000
      },
      "status": "finished"
    }
  ]
}

This is synthetic representative data. The production account identifier uses a visible <redacted-user> marker, and the TWAP identifier is synthetic.

Important fields

FieldDescription
twap_idTWAP order identifier.
state.user, state.coin, state.sideAccount, market, and side.
state.szTarget size as a numeric string.
state.executedSz, state.executedNtlAggregate executed size and notional at this lifecycle boundary.
state.minutesRequested duration in minutes.
state.timestampTWAP creation time in Unix milliseconds.
statusLifecycle string or an object carrying an error. Treat the set as non-exhaustive.

This is lifecycle state, not a fill-by-fill log. Use fills for individual executions.

Join twap_id to a fill's twapId, not its child-order oid. Aggregate execution fields describe lifecycle boundaries rather than continuous progress.

Use signed block actions and responses for submission attempts and cancellations. A fills-derived sample excludes TWAPs that never execute.

For activity already running at your selection's start, include earlier lifecycle records or a matching state seed. See TWAP research validation.

Observed fields

[] marks an array element, [0] a tuple position, <name> an object whose type is that name, and {key} a map keyed by user, asset, or ID. Values after a colon are every distinct value seen for a short enum field. A field missing here can still appear in record types the sample did not contain.

Generated from 49,867 records in node_twap_statuses_by_block/20261021/14.lz4 (2026-10-21).

Text
block_number                     number
block_time                       string
events                           array
events[]                         object
  state                          object
    coin                         string
    executedNtl                  string
    executedSz                   string
    minutes                      number
    randomize                    bool
    reduceOnly                   bool
    side                         string: A, B
    stopPx                       null | string
    sz                           string
    timestamp                    number
    trigger                      null | object
      above                      bool
      px                         string
    user                         string
  status                         object | string: activated, finished, stopped, terminated, waitingForTrigger
    error                        string
  time                           string
  twap_id                        number
local_time                       string

Related pages

  • TWAP order action — Decode the signed payload that starts a TWAP.
  • TWAP cancel action — Decode TWAP cancellation payloads.
  • Indexed TWAP summaries — Query execution-derived summaries for one user.
  • Indexed TWAP slice fills — Query the individual executions produced by TWAP slices.

Hyperliquid Misc Events - Node Data

Inspect misc_events_by_block files, event variants, sample data, and live or archival access.

Hyperliquid Periodic ABCI State - Binary Data

Understand periodic_abci_states RMP files, their layout, and archival, dedicated gRPC, or snapshot access paths.

On this page

AccessFile layoutSample dataImportant fieldsObserved fieldsRelated pages