Check data sources, aggregation, update delay, failure controls and change authority. An automated contract still depends on its inputs.
Traceable and diverse
Timestamp and thresholds
Explicit failure rules
Trace the data path
Data originates offchain, is collected and sometimes aggregated, then published to contracts. Each step can add error, delay or manipulation.
Inspect safeguards
Identify independent sources, aggregation rules, update cadence, deviation limits and historical transparency. Multiple nodes using one source are not truly independent.
Plan for anomalies
Look for pause rules, limits, stale-data handling and responses to extreme markets. Accurate but old data can still trigger harmful decisions.
Connect to economic risk
For a lending or exchange contract, simulate bad input: liquidation, mispricing and loss may occur before correction.
Checks to make
| Item | Check |
|---|---|
| Source | Traceable and diverse |
| Freshness | Timestamp and thresholds |
| Fallback | Explicit failure rules |
Frequently asked questions
Does an oracle prove a fact is true?
No. It delivers data under a trust model.
Are multiple nodes enough?
Not if all rely on the same failing source.
Verifiable sources
Independent educational content reviewed against primary documentation. No personalized recommendation or promise of returns. Reviewed September 24, 2026
