.hoodForked Blocks (Reorgs)
✓ No chain reorganizations
On Ethereum L1, two validators can propose competing blocks at the same height; the network converges on one and the losers become forked (uncle/ommer) blocks. Robinhood Chain has no such competition: a single sequencer assigns every transaction a definitive position, so exactly one block exists at each height and the canonical chain never re-orders.
Where finality comes from
L2 Ordering
Instant & deterministic (sequencer)
L1 Finality
When the batch is posted & finalized on Ethereum
Batch Pipeline
Reversibility
Only via an L1 reorg of the settlement layer (extremely rare, ~2 epochs)
What replaces it here
Instead of watching for uncles, the meaningful trust signal on an L2 is batch inclusion on L1. Once a block's transactions are part of a finalized L1 batch, they are as immutable as Ethereum itself. Track that under L1 Batches and the L1↔L2 message flow under Cross-Chain Transactions.
This page will populate with forked blocks only if the sequencer model ever changes to allow competing block proposals. Under the current single-sequencer design, the count is definitionally zero.