Most oracles make developers pick one data delivery model. That’s limiting—and risky. Different smart contracts fail for different reasons, so a one-size-fits-all approach doesn’t work. APRO fixes this by supporting both Data Push and Data Pull.
The Problem
Smart contracts break when data is late or too expensive. High-speed systems like perpetuals need instant updates. Governance and conditional automation need efficiency. No single delivery method can serve both well.
Data Push
- How it works: APRO automatically sends updates to smart contracts in real time.
- Why it matters: Crucial during volatile markets or sudden price swings.
- Use cases: Perpetual trading, liquidations, high-frequency strategies.
- Tradeoff: Frequent updates can increase gas costs. Best for applications where latency is more expensive than the cost of updates.
Data Pull
- How it works: Contracts request data only when they need it.
- Why it matters: Avoids unnecessary updates and saves costs.
- Use cases: Governance votes, event-driven automation, conditional logic.
- Tradeoff: Not ideal for high-speed market actions, but efficient for planned or occasional updates.
Why Both Matter
DeFi today is diverse. Real-World Assets, gaming, automated protocols—each has different data needs. APRO doesn’t force a single approach. Developers get the flexibility to choose the right model for their application while maintaining security.
Key Takeaways
- Different applications need different oracle behaviors.
- Data Push mitigates risks from volatility.
- Data Pull optimizes cost and efficiency.
- APRO supports both without compromising security.
