Skip to main content

How Does This Model Differ from a “Publisher-Subscriber” Model?

In the request-and-response model, the smart contract initiates the data fetch only when needed, making it suitable for one-off events or specific settlement times. In the publisher-subscriber model, the oracle continuously publishes data updates to the blockchain at fixed intervals or based on deviation thresholds.

This is more suitable for continuous, high-frequency data needs like perpetual futures funding rates or margin collateral price feeds.

How Can a Miner Use ‘Demand Response’ Programs to Lower Their Effective Electricity Cost?
What Is a “Rug Pull” and How Does It Relate to Contract Immutability?
What Is the Difference between a “Pull” and “Push” Oracle Model?
How Does a DAO’s Governance Model Respond to a Real-Time Security Exploit of Its Financial Contracts?