Ordo Validator · Robinhood Chain · chain 4663

Robinhood publishes the state. We replay it.

Every half hour or so, Robinhood Chain posts an assertion to its rollup contract on Ethereum saying what the L2 state should be. This page compares the asserted L2 block hash with what our node has. WASM replay is on and catching up, it has not yet re-executed through the current head, so a match here is not yet a WASM proof of the tip.

first scan in progress
Assertions matching
0
Disagreements
0
Not on this node
0
What this is, and is not. Ordo runs a Nitro validator node (Watchtower strategy, WASM block validation on) against rollup 0x23A19d23e8…272D94 on Ethereum. It is an alarm with a proof, not a defence: this chain's validator set is closed, so we cannot post a challenge even if an assertion were wrong, only say so, with the replay behind it. The table is a hash comparison anyone can redo. A row reading DIFFERS means the asserted block is not the block this node has at that height. That is still not a filed fraud proof.

The assertions

The block hash each assertion commits to, and whether our node has that exact hash as its canonical block at that height.

Nothing scanned yet. The first cycle reads the last few thousand Ethereum blocks; come back in a few minutes.

Check it yourself

Take any row. The assertion's transaction on Ethereum carries the L2 block hash it commits to; ask any Robinhood Chain RPC what it has at that height.

curl -s https://rpc.ordofi.network \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getBlockByHash","params":["0x…",false]}'

Machine-readable: /replay.json · /watchtower.json · RPC comparison · /llms.txt