Documentation
How the floor works
Product mechanics, contracts, data and fees
Onchain state is authoritative for balances, ownership, fees, launch progress, settlement, and receipts. The database is a non-authoritative cache, policy store, and audit log.
Chains
- Robinhood Chain (mainnet)
- Chain ID 4663 · gas ETH · writes enabled Source: config/chains.ts
Robinhood Chain is an EVM-compatible Arbitrum L2. Production reads go through a dedicated server-side RPC proxy; public endpoints are read-only fallbacks and are never treated as production infrastructure.
Launch engine
The application never calls a factory ABI directly. Everything goes through a provider-neutral LaunchEngine interface that returns typed supported, unsupported, blocked, stale, and error states and fails closed.
Pending verification
Testnet and demo only
Disabled stub
Contract manifest
Every required address is declared in a typed manifest carrying chain ID, contract role, address, ABI or source hash, expected bytecode hash, creation block, SDK version, explorer link, verification status, enabled environment, and last verification timestamp.
At startup and in the admin release check we confirm each address has contract code and matches the approved manifest. On mismatch, reads may continue but every write is disabled. No address from any reference project is reused.
Fee model
- Protocol fee
- Unavailable
- Launch fee
- Unavailable
- LP fee
- Unavailable
- Network fee (ETH)
- Unavailable
- Creator economics
- Unavailable
Fees are bounded in both the interface and the contracts, and are itemised before any signature. Values remain unavailable until a verified deployment publishes them.
Data sources
- Robinhood asset registry
- Official assets endpoint — symbol, contract, decimals, ISIN, status.
- Robinhood reference prices
- Official per-symbol price endpoint — indicative offchain reference only.
- Corporate actions
- Official corporate-action data — multiplier and pause state.
- Onchain reads
- Robinhood Chain via a server-side RPC proxy — balances, code, oracle answers, sequencer state.
- Indexed events
- Confirmed logs keyed by chain, transaction hash, and log index, with reorg handling.
