LogoLogo
  • Entangle
    • Overview
    • Security Audits
    • Community
  • Universal Interoperability Protocol
    • Overview
    • Architecture
      • Transmitter Network
        • What are Super Transmitters
        • Transmitter Grouping and Rotation
      • Scalability and Network Stability
        • L2 Utility Blockchains
          • Message Routing in L2 Utility Networks
          • L2 Blockchain
      • Security and Consensus Mechanism
        • Smart Contract Immutability
      • Finality
      • Execution Latency
      • Compatibility and Interoperability
    • Developer Guides
      • Getting Started
      • Solidity
        • Simple Abstract Messenger Example
        • Deploying Your Custom EVM Protocol
      • Solana
      • Calculate Cross-Chain Transaction Cost
      • Becoming a Transmitter
      • Customizable Message Transmission Options
      • How to Debug Sent Messages
    • 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
      • Data Publishing
    • 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
  • Data Endpoints & Omnichain Infrastructure
  • Omnichain Messaging & Cross-Chain Data Propagation

Was this helpful?

Export as PDF
  1. Universal Data Feeds
  2. Architecture

Oracle Contract & User Interaction

PreviousPush ModelNextDeveloper Guides

Last updated 1 day ago

Was this helpful?

UDF’s oracle contracts provide two distinct interfaces, Pull and Push, designed to deliver flexible data access for dApps. Please refer to the section for implementation details.

The Pull interface enables on-demand verification within user transactions, supporting both Pay-As-You-Go (PAYG) and subscription-based models. The Push interface offers subscribed users seamless access to pre-verified, on-chain data updates.

These interfaces, detailed in the table below, leverage VerificationLib to ensure data integrity and adaptability across diverse use cases.

Interface
Function
Purpose
Use Case

Pull

verifyWithFee()

Processes the protocol fee for the PAYG pull model during a transaction, verifies transmitter votes, and returns the aggregated data value.

Ideal for dApps with sporadic data needs.

Pull

verifyAsSubscriber()

Confirms the user has an active pull subscription, verifies votes, and returns the aggregated data value without additional protocol fees.

Suited for protocols (e.g. lending) needing frequent, real-time price checks with predictable costs.

Push

getFeedPrice()

Allows subscribed users to read the latest push feed data stored on-chain without verification overhead.

Suited for DEXs or stablecoin issuers requiring continuous price updates for liquidity pools.

Data Endpoints & Omnichain Infrastructure

  • Multiple Chains: Each supported chain has UDF Oracle Push and Pull contract deployments. See the page for more information.

  • Push Node Authorization: Authorization mechanisms manage the push nodes that are permitted to submit updates on each chain, ensuring controlled data propagation through access control mechanisms.

  • Cross-Chain: If a protocol operates on multiple chains, EIB bridging can propagate the final snapshot from the aggregator through the EIB and towards multiple chains, ensuring uniform data across all deployments.

Omnichain Messaging & Cross-Chain Data Propagation

UDF ensures seamless omnichain data propagation by leveraging Entangle’s cross-chain messaging protocol. Transmitter nodes monitor the Entangle Interoperable Blockchain (EIB) to efficiently relay oracle data across different networks. This setup enables push updates to be mirrored on multiple chains simultaneously, reducing inconsistencies and ensuring real-time availability of oracle data for multi-chain dApps.

developer guides
data endpoints