Pull Model

Entangle's Pull Model ensures real-time data availability for user transactions, eliminating dependency on scheduled updates. This approach enhances the precision and reliability of blockchain applications by providing up-to-date information when needed.

When a transaction is initiated, the application requests the latest data directly from Entangle's decentralized sources. The data is retrieved instantly from a snapshot of verified data, and is authenticated within the same transaction. This ensures only accurate, real-time data is used, minimizes costs, and provides a reliable foundation for cross-chain applications.

User Transaction

When a dApp user wants to perform an action (e.g., open a leveraged position, or open a lending/borrowing position), the latest data feed proof is included in the transaction’s calldata. This action uses the PullMarketplace contract with the functions verifyWithFee and verifyAsSubscriber for PAYG and Subscription methods respectively.

On-Chain Verification

The UDF oracle contract verifies signatures from the aggregator (transmitters). If valid, the feed value is accepted for that user’s transaction.

Gas & Fee Implication

Each user pays a “verification fee” in native tokens (either through Pay-As-You-Go (PAYG) approach or predefined monthly subscriptions) to cover the cost of verifying the aggregator’s signatures and for the aggregator’s services. This suits lower-frequency but latency-sensitive use cases.

Summary

• Minimal Data Staleness: The feed is as fresh as the aggregator’s most recent update with an update frequency of 200ms.

• Lower Latency: Data is fetched during transaction creation and verified during execution, ensuring real-time accuracy.

• Decentralized Access: Each user includes the proof, removing reliance on a single push node.

• Fine-Grained Cost: Perfect for dApps using PAYG with moderate or unpredictable usage, as they pay only when they need the data.

• Transaction Gas Costs: Each transaction requiring oracle verification incurs verification overhead.

• Best for On-Demand Use Cases: Ideal for lending protocols, derivatives, and real-time settlement applications.