Decentralized Oracle Network

Node operators are required to post collateral (stake) that is slashed if they provide erroneous data or deviate from the protocol. This aligns economic incentives with honest behavior.

• Implicit Incentives: Revenue from data requests.
• Explicit Penalties: Loss of staked tokens for downtime or manipulation.
• Sybil Resistance: The cost of running malicious nodes scales linearly with the number of nodes, making attacks financially infeasible.

A DON fetches data from multiple independent sources and nodes, then uses consensus algorithms to aggregate a single deterministic answer. This prevents a single compromised API or node from corrupting the on-chain value.

• Medianization: Filters out extreme outliers.
• Weighted Aggregation: Prioritizes nodes with higher historical accuracy and uptime.
• Threshold Signatures: Combines multiple signatures into one compact proof for gas efficiency.

An efficiency upgrade that allows all oracle nodes to aggregate their observations into a single transaction on the blockchain. Instead of N nodes submitting N transactions, OCR generates one verifiable report.

• Cost Reduction: Drastically lowers gas fees.
• Scalability: Enables higher-frequency data updates.
• Fair Ordering: Prevents front-running by committing to data before revealing it on-chain.

Advanced DONs utilize hardware-based privacy (like Intel SGX) to allow nodes to process sensitive data without being able to read it. This enables confidential computation where the node operator cannot see the raw API response.

• Data Privacy: Enables enterprise use cases requiring secrecy.
• Verifiable Compute: Hardware attestation proves the correct code ran in the enclave.
• MEV Protection: Prevents node operators from extracting value by reordering transactions.

On-chain reputation systems track the historical performance of node operators regarding uptime, latency, and deviation. Users can select nodes based on strict SLAs.

• Dynamic Weighting: New nodes earn trust over time.
• Penalty Mechanisms: Repeated failures lead to permanent slashing and ejection.
• Transparency: All performance metrics are publicly auditable on-chain.

The architecture splits logic between the on-chain contract (deterministic settlement) and the off-chain DON (non-deterministic computation). This allows smart contracts to react to real-world events without sacrificing the finality of the blockchain.

• Scalable Computation: Heavy logic runs off-chain.
• Cross-Chain Interoperability: DONs bridge data between disparate blockchains.
• Keepers/Automation: DONs trigger contract functions based on external conditions.

A Layer 2 scaling solution that bundles hundreds of off-chain transactions into a single batch and generates a cryptographic validity proof posted to the Layer 1 blockchain. In the context of oracles, ZK-Rollups can compress multiple data feed updates into a single proof, dramatically reducing the cost of on-chain data delivery. The validity proof mathematically guarantees that all batched transactions were executed correctly without requiring the L1 to re-execute them.

A public-key pseudorandom function that produces an output along with a proof that the output was computed correctly. Anyone holding the public key can verify the proof without needing the secret key. Oracle networks use VRFs to:

• Select node committees fairly and unpredictably
• Generate tamper-proof randomness for smart contracts
• Prove that data feed aggregation was performed by a randomly selected, unbiased subset of nodes

A technique allowing light nodes to probabilistically verify that block data is available for download without downloading the entire block. This is critical for oracle networks operating on modular blockchain architectures where data is published to a separate availability layer. By randomly sampling small chunks of data and checking erasure-coded redundancy, nodes achieve high confidence that the full dataset is recoverable.

A Layer 2 scaling solution similar to a ZK-Rollup but stores transaction data off-chain with a data availability committee rather than posting it to the Layer 1 blockchain. For oracle networks, Validium architectures offer a trade-off: lower data costs in exchange for trusting a committee to keep data available. This is suitable for high-frequency price feeds where the data is ephemeral and full on-chain storage is unnecessary.

An Ethereum Improvement Proposal introducing blob-carrying transactions for temporary data storage. Blobs are large data chunks (up to 128 KB) that persist for only ~18 days, designed specifically to reduce costs for rollups and oracle networks posting data to Ethereum. Oracle networks leverage EIP-4844 to post batched data feed updates at a fraction of the cost of traditional calldata, with blobs priced on a separate fee market.