ONCHAIN STATE. OFFCHAIN EVIDENCE. ONE CLEAR VIEW.Frontend preview
Documentation /

Architecture & network

Separate chain observations, offchain attestations and deterministic evaluation.

Data flow

An RWA token address is submitted to the reconciliation API. Onchain RPC readers, PoR/oracle monitors and attestor ingestion provide evidence to a deterministic rules engine. The API returns an operational status and its verification context.

The engine is specified to use deterministic rules, not an opaque statistical model or non-deterministic AI decision.

Source: PDF p1 §3; p2 §6; p4 §10

Network configuration

Official configuration: https://docs.robinhood.com/chain/connecting/

Chain ID 46630 in the PDF is Testnet. Production/mainnet is a separate deployment decision, not a label to substitute into the sample. Public RPCs are rate-limited and not recommended by Robinhood for production. No RPC credentials belong in browser assets.

NetworkChain IDCurrent Comms integration
Robinhood Chain Testnet46630Not connected
Robinhood Chain mainnet4663Not deployed

Source: PDF p3 §7; https://docs.robinhood.com/chain/connecting/

Technology choices

LayerSpecified technologyDelivery state
FrontendNext.js, React, TypeScript, Tailwind CSSImplemented frontend preview
BackendNode.js / Fastify or Python / FastAPIPlanned; backend selection open
Chain accessviem, ethers.js, RH Chain RPCNo live reads in this preview
DatabasePostgreSQL + TimescaleDBPlanned
CacheRedis with tiered expiryPlanned

Source: PDF p4 §10

Specified cache windows

Cache TTL does not override evidence validity or an asset-specific heartbeat. A cached response must retain observation times and block context.

ObservationCache window
PoR & reserves30–60 seconds
Pause / freeze state15–30 seconds
Sequencer health5–10 seconds
Contract bytecode24 hours

Source: PDF p4 §10; integration guidance