Architecture & Consensus
TL;DR: ORCAFI uses a Hub-and-Spoke model where multiple node operators independently fetch data from Multi exchanges, filter outliers with AI, reach consensus through BFT, and publish cryptographically signed prices on-chain.
Data Pipeline
Sources
Multi CEXs & DEXs
AI Filter
Outlier Detection
On-Chain
Verified & Stored
Multi-Source Ingestion
To prevent single-point failures, we ingest three distinct categories of data:
🔄 DEX TWAPs
Time-Weighted Average Prices from Uniswap V3, Curve, and Balancer. Liquidity-derived weighting ensures prices are backed by real capital.
✍️ Signed CEX Feeds
Cryptographically signed feeds from Binance, Coinbase, and Kraken. Signatures verified against the on-chain Source Registry.
📊 Health Signals
Real-time liquidity pool depth, utilization rates, and protocol health metrics directly from the blockchain.
AI-Driven Filtering
Before entering consensus, all data passes through rigorous validation:
Data deviating significantly from the group median is rejected
Timestamps older than 500ms acceptance window are discarded
Price moves not backed by order book depth are excluded
Off-chain feeds must pass cryptographic verification
Consensus Mechanism
Liquidity-Weighted Median
Unlike basic medians, we weight prices by actual liquidity depth. A $10M order book on Binance influences the price more than a $1k pool on a DEX.
Quorum Enforcement
Minimum 67% of nodes must agree. If quorum isn't met, the round aborts — preventing any single compromised source from affecting the price.
On-Chain Verification
Once consensus is reached, the data packet is signed by a threshold (t-of-n) of node operators and submitted on-chain. The smart contract verifies:
- Signature validity — Schnorr signatures from participating nodes
- Timestamp freshness — Unique round ID prevents replay
- Quorum met — Required number of validators signed
🔐 Security Note: No single entity — including the ORCAFI team — can manually alter prices on-chain. All updates require multi-party consensus.