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.
Glossar
Margin Collateral
Function ⎊ Margin Collateral is the security deposit required by derivative counterparties or exchanges to guarantee the performance of open contracts, serving as the primary mechanism for mitigating credit and settlement risk.
Perpetual Futures Funding Rates
Mechanism ⎊ Perpetual futures funding rates represent a dynamic fee structure embedded within perpetual contracts, a cornerstone of cryptocurrency derivatives markets.
One-off Events
Event ⎊ In cryptocurrency, options trading, and financial derivatives, an event signifies a discrete occurrence impacting contract valuation or exercise conditions.
Smart Contract
Code ⎊ The contract is fundamentally self-executing code deployed on a distributed ledger, embodying the terms of the agreement in an immutable format.
Data Updates
Frequency ⎊ Data updates refer to the temporal rate at which new, validated price information is written onto the blockchain for smart contract consumption.
Publisher-Subscriber Model
Architecture ⎊ Publisher-Subscriber Model is a messaging pattern where data providers, the publishers, broadcast information streams that are received by interested consumers, the subscribers, often used in oracle networks for price dissemination.