For: CCIP, protocol-specific price feeds, risk metrics, proof-of-reserves, AI signals

Problem

Most oracle systems are rigid and permissioned, with fixed committees and bespoke integrations per chain. Expanding coverage is expensive, updates can be slow or stale, and manipulation risk remains due to weak incentives, limited slashing, MEV at publication time, and unclear dispute processes. Portability across chains is poor and auditability is fragmented.

Relay Solution

Relay acts as a universal oracle engine. Any approved operator can fetch off-chain data and produce a stake-backed attestation that is:

• Verifiable on chain with BLS aggregation and anti-replay.
• Backed by bonded validators with explicit slashing for bad data, equivocation, or missed SLAs.
• Programmable via schemas for prices, TWAPs, risk scores, proof-of-reserves, or custom metrics.
• Cheaper at scale by batching many feed updates into one verification.
• Composable across EVMs and compatible with CCIP-style routing through thin adapters.
• Auditable with on-chain receipts and clear freshness guarantees.

How it Works

1. Register and bond. Operators join the feed and lock stake as collateral.
2. Define the feed. You set what data to track, how often to update, how to combine sources, and the service levels.
3. Collect and compute. Operators fetch data from chosen sources and calculate the feed’s current value.
4. Attest. Each operator signs the result with timing and round details.
5. Aggregate. The signatures are combined into a single proof for that update window.
6. Verify on chain. A verifier checks that enough staked operators signed, the update is fresh, and it is not a replay.
7. Publish or trigger. The value is written on chain or passed to protocols that use it.