Veyronn Documentation
Mainnet Oracle
The implemented Chainlink Data Streams path and why it is not yet deployed.
Veyronn's production oracle target is official Chainlink Data Streams verification on Robinhood Chain.
Implemented path
The mainnet OracleRouter and service adapters support:
- Chainlink Data Streams schema v3 and v8
- benchmark, bid, ask, and report timestamps
- v8 market-status enforcement
- official verifier-proxy verification
- per-market report-age limits
- independent
AggregatorV3reference-feed deviation checks - sequencer uptime checks and post-recovery grace period
- atomic one-report and multi-report execution
- WebSocket-driven keeper updates with REST recovery
- server-only Vercel transaction building
- router-funded LINK fees when a verifier fee manager requires them
LINK and subscriptions
Data Streams access is subscription-based and requires Chainlink-issued API credentials. Users do not ordinarily hold LINK. If the on-chain verifier quotes LINK fees, governance funds the oracle router and the router pays the configured reward manager.
Why it is not live
No mainnet contracts have been broadcast. Production needs:
- commercial Data Streams access
- exact reviewed stream IDs, schemas, decimals, and reference feeds
- official sequencer and verifier addresses
- real collateral and vault policy
- multisig and timelock governance
- managed keeper keys and redundant regions and RPCs
- reviewed market economics and limits
- external smart-contract and oracle/economic audits
- legal and compliance approval for RWA markets
- load, latency, reorg, outage, stale-report, market-close, and failover acceptance tests