Data Delivery Methods
Last updated
Was this helpful?
Last updated
Was this helpful?
UDF provides both push and pull oracle solutions through dedicated marketplace contracts deployed on target chains. These contracts enable seamless data access tailored to different use cases. Pull model is like ordering data on demand; push model is like subscribing to a live feed.
At the core of this system is VerificationLib, a smart contract deployed on target chains to aggregate signed oracle votes into a single, consensus-driven value. It supports multiple data types, including price feeds and high-precision floating-point values, ensuring adaptability across various applications.
Both push and pull marketplace contracts operate alongside VerificationLib, leveraging its validation mechanism to guarantee the integrity and reliability of oracle data.
The Pull Model (On-Demand) fetches data only when required, ensuring it is up-to-date and reducing unnecessary updates. This method optimizes for accuracy and cost efficiency since the data is retrieved in real time based on the application’s needs. It eliminates delays caused by maintaining an on-chain state and is ideal for scenarios requiring real-time precision, such as DeFi trades or event-based actions.
On the other hand, for the Push Model (Continuous), data is delivered periodically, irrespective of immediate need, by maintaining an on-chain state. While it ensures that data is consistently available, this approach can introduce delays and inaccuracies due to the cost and technical limitations of frequently updating the on-chain state. As a result, this model is best suited for DEXs or stablecoin issuers requiring continuous price updates for liquidity pools at fixed intervals or price deviations.
UDF’s flexible monetization covers both subscription-based payments for push and pull feeds and a pay-as-you-go (PAYG) model for pull verifications, allowing users to choose plans based on their data needs and cost preferences. Pricing details are implemented via the PullMarketplace and PushMarketplace contracts.
The Push Model delivers regular oracle updates based on configurable price deviations (0.25%, 0.5%, 1%, 2.5%, 5%) or a default heartbeat (every 24 hours). Users deposit funds upfront, and subscription costs are shared among all users. This becomes increasingly cost-effective as more subscribers join the same feed.
The Pull Model lets users fetch oracle data directly within their transactions using either Pay-As-You-Go (PAYG) or monthly subscriptions. PAYG users pay a small fee per data request, ideal for occasional queries, while subscriptions offer unlimited data access at predictable monthly rates. Since data updates occur continuously off-chain, users only pay transaction verification costs, regardless of usage frequency.
Please refer to the UDF for in-depth details on how the prices are calculated.
PAYG (Pay-As-You-Go): Users pay a small protocol fee per request, including the aggregator’s proof in their transaction. This model is best for dApps with sporadic or low-frequency data needs, as costs scale with usage. Learn more about the exact formula we use in our . PAYG is solely programatic and cannot be purchased through the marketplace, learn more .
Subscription: Users can subscribe to continuous data access for a fixed periodic (e.g. monthly) fee, eliminating per-request costs and the protocol fee. This model is ideal for applications with consistent data consumption, reducing transaction overhead while ensuring predictable expenses. You can manage your subscriptions through the marketplace or .
Fair Pricing Model: The protocol ensures pricing transparency by dynamically estimating costs based on gas prices and cost sharing mechanisms. Users prepay for updates with a minimum, 7 day suggested deposit, covering a few updates and gas costs upfront. Additionally we advise users to also consider the buffer deposit to cove for gas spikes and volatility.
Exclusive Access: On-chain price data is restricted to paying users, ensuring that only those contributing to the ecosystem benefit from updates.
Cost Sharing Mechanism: As more consumers subscribe to a feed, the cost per user decreases, making the model more economical at scale.
Gas prices vary significantly (e.g., Ethereum vs. an L2) and UDF must adapt. Fees vary based on the target chain’s gas costs; higher fees apply to expensive chains, while cheaper chains benefit from lower costs. Pricing is periodically adjusted to reflect changes in network fees, ensuring sustainable operations across all supported chains.
The Pull Model ensures that data updates are available in real-time, with minimal delay since users fetch and verify updates themselves, making it particularly useful for time-sensitive applications where immediate data updates are crucial, such as trading platforms or live dashboards.
In contrast, the Push Model, may introduce some latency since data is fetched periodically on-chain, an expensive process. While it is generally fast, it is better suited for applications where real-time updates are not as critical.
The Pull Model provides excellent scalability for applications requiring frequent updates. It is best suited for scenarios with lower transaction volumes, where the cost impact of update verification remains minimal.
On the other hand, the Push Model scales efficiently across all scenarios by minimizing redundant updates and maintaining low gas costs. It's particularly advantageous for applications with medium-to-high transaction volumes, where gas usage is a significant concern. Push users simply read the latest data from storage without incurring additional gas charges, making this model a more cost-effective solution for handling high transaction volumes.
