torihiki
recorded session
BTC-PERPtorihiki
Last$68,000.70
Mark$68,000.00
Oracle$68,000.00
Equity$2,500,000.00
Block1
Order bookprice / size / total
Price (USD)Size (BTC)Total
68,002.700.0910.692
68,002.300.0780.601
68,001.900.1170.523
68,001.500.0390.406
68,001.100.0260.367
68,000.700.3410.341
$68,000.70spread
67,999.700.1670.167
67,999.300.3730.540
67,998.900.0260.566
67,998.500.0390.605
67,998.100.1170.722
67,997.700.0780.800
67,997.300.0910.891
Tradesengine fills
PriceSizeBlock
68,000.300.1671
68,000.700.0321
Position

No open position.

Chainsequencer
Block1
Resting orders17
Funding (1h)+0.0%
Oracle$68,000.00

Margin and liquidation read the MARK, never the last print. The mark is the oracle plus a banded, size-weighted book premium — one lot lifted through a thin book cannot move it, which is otherwise a way to liquidate other people.

state root ae654b18b8b58d08e9aaf386a043f1fe

SHA-256 over a canonical encoding of the live state. A validator replays the block and recomputes this; if it differs, the sequencer lied.

What you are looking at

Every number on this page was produced by torihiki, an open reimplementation of the exchange state machine that Hyperliquid keeps closed. The order book, the fills, the position and its unrealized PnL, the funding rate and the state roots all came out of the real engine: prices are integer ticks, matching is price-time priority, and the roots are SHA-256 over a canonical encoding.

It is a recording, not a live venue. The engine ran 240 blocks ahead of time and this page replays the frames. The engine does run in a browser — the same ClojureScript sources reproduce a JVM validator's state root byte for byte — but executing it in your tab is a separate build that has not been done. Saying which one you are looking at seemed better than letting the animation imply the other.

3,155,313 ops/sec

Measured matching throughput, 317 ns/op — 15.8x HyperCore's documented 200,000 orders/sec. Execution only; no consensus.

Sequencer, not consensus

One writer decides the order. Nothing votes. The log is checkable by replay, which is a different guarantee from tamper-evidence and the stronger one.

No floating point

Every value is an integer inside the range both the JVM and JS represent exactly, so two validators cannot disagree in the last bit.