Networks and addresses

Testnet. Nothing in this protocol has been deployed to mainnet. The deploy script refuses chain 4663 outright, regardless of configuration.

#Robinhood Chain

An Arbitrum Orbit (Nitro) chain running ArbOS 116.

#block.number is not a clock

On an Orbit chain, block.number returns an estimate of the L1 block, not a local counter. It does not advance once per L2 block and cannot be used to measure elapsed time.

Every piece of elapsed-time logic in this protocol uses block.timestamp instead: pending expiry, epoch boundaries, price staleness. This is the single most common way an EVM protocol ported to an Orbit chain breaks.

#Finality

The sequencer gives fast soft confirmation, but an L1 reorganisation can still reorganise unfinalised L2 blocks. The indexer treats a configurable depth as final and labels everything shallower as unfinalised rather than hiding it.

#Address verification

Every address the system uses must pass an onchain verification predicate before it is accepted into configuration. A name is not evidence: this chain hosts six verified contracts called Quoter, two of which point at fork factories.

The check runs as a command and refuses any address lacking a predicate:

pnpm verify:chain

Security. Production addresses are never hardcoded before they have been verified against a live node. Testnet addresses come from the verified deployment configuration; nothing renders an unresolved production address as though it were settled.

#Local development

The whole stack runs against a local Anvil node configured with the testnet chain ID. The keeper asserts the chain ID at startup and refuses to run against the wrong one — a check that immediately caught Anvil defaulting to 31337 while the configuration said 46630.

Deployed addresses for a local run are printed by the deploy script and are deterministic for a given Anvil seed. They mean nothing on any real network.