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.
| Network | Chain ID | Current Comms integration |
|---|---|---|
| Robinhood Chain Testnet | 46630 | Not connected |
| Robinhood Chain mainnet | 4663 | Not deployed |
Source: PDF p3 §7; https://docs.robinhood.com/chain/connecting/
Technology choices
| Layer | Specified technology | Delivery state |
|---|---|---|
| Frontend | Next.js, React, TypeScript, Tailwind CSS | Implemented frontend preview |
| Backend | Node.js / Fastify or Python / FastAPI | Planned; backend selection open |
| Chain access | viem, ethers.js, RH Chain RPC | No live reads in this preview |
| Database | PostgreSQL + TimescaleDB | Planned |
| Cache | Redis with tiered expiry | Planned |
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.
| Observation | Cache window |
|---|---|
| PoR & reserves | 30–60 seconds |
| Pause / freeze state | 15–30 seconds |
| Sequencer health | 5–10 seconds |
| Contract bytecode | 24 hours |
Source: PDF p4 §10; integration guidance