LogoLogo
  • Entangle
    • Overview
    • Security Audits
  • Universal Interoperability Protocol
    • Overview
    • Architecture
      • Scalability and Network Stability
        • L2 Utility Blockchains
        • Transmitter Groups
      • Security and Consensus Mechanism
      • Finality
      • Execution Latency
      • Compatibility and Interoperability
    • Developer Guides
      • Getting Started
      • Solidity
        • Simple Abstract Messenger Example
        • Deploying Your Custom EVM Protocol
        • Bridging Tokens with UIP
        • Become an EVM Transmitter
      • Solana
        • Simple Abstract Messenger Example
        • Deploying Your Custom Solana Protocol
        • Become a Solana Transmitter
      • Calculate Cross-Chain Transaction Cost
      • Customizable Message Transmission Options
      • How to Debug Sent Messages
      • SDK Setup
      • Revenue Sharing for Transmitters
      • How to Become a Super Transmitter
    • Endpoints
  • Universal Data Feeds
    • Overview
    • Architecture
      • Data Delivery Methods
        • Pull Model
        • Push Model
      • Oracle Contract & User Interaction
    • Developer Guides
      • Custom Data Feeds
      • Fetch Data via Pull Model (PAYG)
        • EVM Smart Contracts
        • Solana Smart Contracts
      • Fetch Data via Pull Model (Subscriptions)
        • EVM Smart Contracts
        • Solana Smart Contracts
      • Fetch Data via Push Model
        • EVM Smart Contracts
        • Solana Smart Contracts
    • User Guides
      • Accessing Feeds
      • Subscribe to a Data Feed
      • Check Subscription
      • Manage Subscription
      • Renew Subscription
    • Data Endpoints
  • Universal Token Standard
    • Overview
    • Architecture
      • Fee Components
    • Developer Guides
      • Manual Deploy
        • Token Deployment Types
        • Create a Custom Token
        • Factory Blueprint Deployment
        • Examples
          • Initial Setup
          • UTS Connector
            • Mint & Burn Connector Scheme
            • Lock & Unlock Connector Scheme
            • Connector Over Native Currency
          • UTS Token
            • Simple Token
            • Token with Messages
      • Bridge SDK
      • Token Verification
      • Fees Calculation & Gas Estimation Logic
      • Estimations
    • User Guides
      • Launch Universal Token
      • Create a Liquidity Pool
      • Expand Existing Token
      • Transfer Liquidity to Connector
      • Bridging
    • Contract Addresses
  • Entangle Interoperable Blockchain
    • Overview
    • Architecture
    • Developer Guides
      • Set up a Validator Node
      • Delegating to Validators
      • Undelegating from Validators
      • Supported Accounts
  • More
    • Media Kit
    • FAQ
    • Report an Issue
    • Become a Partner
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Universal Data Feeds
  2. Architecture
  3. Data Delivery Methods

Push Model

PreviousPull ModelNextOracle Contract & User Interaction

Last updated 1 month ago

Was this helpful?

Entangle's Push Model delivers continuous, automated updates for critical data, such as prices and asset values, across multiple blockchains. These updates are delivered periodically, making them ideal for scenarios requiring data at set intervals or infrequently, without the need for user requests. This is particularly useful for applications like monitoring dashboards or dApps that display market prices or feed metrics, ensuring optimal performance without user-initiated transactions.

The Push Model transmits verified information across blockchains when specified deviations occur and at set heartbeat intervals. All updates undergo a secure, consensus-driven verification process before being published on-chain, ensuring data accuracy and security.

Scheduled or Triggered Updates

UDF push nodes post the current aggregated feed to a target chain at given price deviations of 0.25%, 0.5%, 1%, 2.5%, or 5% depending on the deviation parameter selected by users, or based on a predefined heartbeat of 24 hours to guarantee sufficient data freshness even when price variations are minimal.

This means users with stricter update frequencies bear a proportionally higher cost, increasing a user's cost share. This ensures that users requiring frequent updates pay more, while those with wider deviation tolerances contribute adequately less, maintaining fairness and economic efficiency.

Single On-Chain Storage

The UDF push oracle contract holds the verified value so that authorized users’ dApps can read it without paying additional verification overhead. This is managed by the PushMarketplace contract, and whitelisted addresses can read via the getFeedPrice function.

Fee Model

UDF charges a small percentage on deposits to the push marketplace contract. The push oracle updates cost is shared across subscribed readers, making it cheaper for the UDF push oracle user base wanting continuous access.

Summary

  • Gas Efficiency for Consumers: Price reads are restricted to subscribed users and data updates are shared across multiple users, reducing individual verification costs.

  • Cost Efficiency for Consumers: Cost sharing mechanisms amongst subscribed users makes subscriptions cost efficient.

  • Slight Delay in Data Freshness: Updates happen periodically (price deviation triggers or time-based heartbeats).

  • Best for Continuous Data Access: Suited for DEXs, stablecoin issuers, and liquidity protocols needing steady price updates.

Subscribed users can share the cost of running the same feed which guarantees cost efficiency for users. As more consumers subscribe to a feed, the cost per user decreases, making the model more economical at scale. Consider checking out our for indepth details on the cost sharing formula.

whitepaper