Independent verification layer · Robinhood Chain
Detected.Verified.Confirmed.
Gapwatch watches the Robinhood Chain sequencer feed, independently recomputes every corporate-action event, and records the result on-chain — separate from Robinhood Predictor, verifiable by anyone.
How a corporate action gets confirmed
Sequencer feed
Robinhood Chain mainnet feed
Filter check
isTransactionFiltered
L1 confirmation
block finality
Reference model
recorded on testnet registry
Feed monitored: Robinhood Chain mainnet. The four stages above run unattended and record to the testnet registry (V1). Confirmed events can then be promoted to the mainnet consensus registry (V2), which requires 2-of-3 node signatures and is written manually rather than by this pipeline — so detection is continuous while consensus confirmation is a deliberate step.
Shipped so far
- On-chain registry with challenge bonds and a downstream lending-pool consumer, live on Robinhood Chain Testnet and running unattended
- 2-of-3 consensus registry and Stylus verifier deployed to Robinhood Chain Mainnet, with the first real consensus confirmation now recorded on-chain
- API and database layer reading both registries directly
Manual by design
Writing to the mainnet registry stays manual. Each record needs 2-of-3 node signatures, and automating that would mean putting all three node keys on the same server — collapsing the separation the 2-of-3 scheme exists to create. Detection is automatic; consensus confirmation is reviewed and signed deliberately.