Skip to content
Indexer Access

Chains

Robinhood Chain today, more coming. How chain scoping works, and what stays separate per chain.

The chain segment is required:

GET /index/v1/{chain}/tokens/{address}

Deployment-configured slug required; raw chain IDs are unsupported. Unknown slugs return typed refusals listing supported slugs; no default fallback.

Available today

ChainSlugChain idNative assetStatus
Robinhood Chainrobinhood4663ETH (18 decimals)Serving

Additional chains: planned configuration/ingest adapters.

Robinhood ingests its sequencer feed with sequencer-ordered finality and bounded maximum reorg depth. Read response snapshots/coverage; these are deployment properties.

Chain configuration

Incomplete declarations prevent startup.

PropertyMeaning
Ingest adapterHow blocks arrive, whether a sequencer feed or plain JSON-RPC
Finality modelWhether the chain exposes tiers beyond its head
Reorg depthHow far the chain may rewind, which bounds cursor validity
Native assetSymbol and decimals
Wrapped nativeThe ERC-20 wrapper, required for USD marking
AMM authoritiesWhich pool-creating protocols this build recognises
Launchpad tableWhich launchpads this build decodes

Undeclared properties remain absent. Without AMM authorities, pool identity and dependent routes report unavailability.

Chain isolation

  • Stores: independent indexes, reorg state, and cursors; cross-chain cursors are refused.
  • Snapshots: independent heads/reorg timelines; multi-chain responses carry one (block, hash) and status per chain.
  • Coverage: exactly the requested chains, including typed unavailable entries. Unreachable chains are never omitted.

Read each chain's snapshot independently.

View this page as Markdown