Oracles & Daten-Feeds
Reale Daten on-chain bringen
Dezentrale Oracle-Pools liefern externe Daten für DeFi & Vorhersagemärkte.
Schnellstart
Oracle-Funktionen
Zuverlässige externe Daten für Smart Contracts
Dezentrale Oracle-Pools
Mehrere Datenprovider gewährleisten Zuverlässigkeit und verhindern Manipulation
On-Chain-Aggregation
Smart Contracts aggregieren und validieren Daten aus mehreren Quellen
Preisfeeds
Echtzeit-Preisdaten für DeFi-Protokolle und Vorhersagemärkte
Benutzerdefinierte Datenquellen
Beliebige externe API oder Datenquelle mit der Blockchain verbinden
Konsensmechanismen
Verschiedene Konsensmodelle für unterschiedliche Datenzuverlässigkeitsanforderungen
Anreizausrichtung
Wirtschaftliche Anreize gewährleisten genaue und zeitnahe Datenbereitstellung
Oracle-Architektur
Wie Oracle-Pools auf Ergo funktionieren
Ergos Oracle-System liefert zuverlässige externe Daten:
- Dezentrale Datenerfassung
- On-Chain-Aggregation und -Validierung
- Wirtschaftliche Anreize für Genauigkeit
- Flexible Konsensmechanismen
- Unterstützung für beliebige Datentypen
Oracle Comparison: Ergo vs Leading Alternatives
Six different approaches: eUTXO pools (Ergo), off-chain reporting (Chainlink), pull feeds (Pyth), hybrid models (RedStone), permissionless bonds (Tellor), and optimistic assertions (UMA).
| Dimension | Ergo | Chainlink | Pyth | RedStone | Tellor | UMA |
|---|---|---|---|---|---|---|
| Update Model | Push pools on eUTXO; epoch-based publishing | Push feeds with Off-Chain Reporting (OCR) | Pull/on-demand price feeds | Hybrid: Push/Pull/X models | Permissionless reporters with bonds | Optimistic assertions with disputes |
| Aggregation Method | On-chain pool logic (boxes) + off-chain agents | Off-chain committee → single on-chain submit | Pyth program + confidence; dApp commits on demand | Push on-chain; Pull/X signed bundles in tx | On-chain consensus via economic incentives | Accepted unless disputed; DVM arbitrates |
| Who Pays Updates | Pool treasury pays rewards to reporters | Operator set; gas costs amortized | Consumer/updater pays tx fees on demand | Push: provider pays; Pull/X: tx sender pays | Reporters pay bonds; rewards in TRB | Asserter posts; participants fund disputes |
| Update Frequency | Configurable per pool (minutes/blocks) | Infrequent batched; high off-chain frequency | Very high off-chain; on-chain when consumed | Push: periodic; Pull/X: on demand | Request/reward-driven; variable timing | Fast if undisputed; slower when escalated |
| Permissions Model | Community-defined pools/reporters | Curated operator set per feed | Approved publishers; open reads | Signed by providers; open consumption | Fully permissionless participation | Open roles (asserter/disputer) |
| Data Types | Prices; extensible to events via scripts | Prices, VRF, Automation, Functions, CCIP | Primarily prices (crypto/FX/equities/commodities) | Prices, RWA data; automation hooks | Flexible (prices/events) via query spec | General truths: prices, events, KPIs |
| Primary Use Cases | Ergo DeFi (SigmaUSD), protocol metrics | General DeFi feeds, randomness, upkeep | Perp DEX/derivatives, high-frequency pricing | EVM rollups, cost-sensitive apps, RWA | Censorship-resistant feeds, open data | Prediction markets, insurance, non-standard data |
| Key Limitations | Need disciplined reporters; stale data risk | Service cost; curated operators dependency | Must handle confidence intervals; updater dependency | Signature validation complexity; bundle availability | Latency variance; dispute economics sensitivity | Trust window pre-dispute; arbitration delays |
Note: For production integrations add safety belts — averaging windows, deviation thresholds, signature/source checks, fallback feeds, and circuit breakers on anomalies. Each oracle model has unique trade-offs between decentralization, latency, cost, and data quality.
Live-Oracle-Lösungen
Aktive Oracle-Implementierungen auf Ergo
Spezialisierte Oracles für DeFi-Protokolle
Häufig gestellte Fragen
What's Next?
Start using or building oracle solutions on Ergo today