Flux docs
Data Request Cycle
Description and life cycle of data requests
Data requests are the basic mechanism for data provision and resolution on the Flux Oracle. They are always created by Requester Contracts (or by user proxy if the requester contract is set up that way), resolved on the oracle, and finalized when the request is resolved and the outcome is returned to the requester contract.
The life cycle of a data request is 1) creation, where a user or contract queries a Requester Contract to query the oracle to begin a new data request, 2) resolution, where validators stake FLX on the correct outcome to receive a reward, 3) dispute, where FLX holders can dispute a bonded outcome by staking and trigger an escalation game, and 4) finalization, where the outcome is set on the target contract.
A high-level overview of the data request cycle
The security of any data request directly correlates to the duration of its challenge period; the longer the duration, the more robust the challenge can be. This duration is always defined by the data request parameters and set between a window of 5 minutes and 24 hours. If a data request is more arbitrary or doesn’t have a pool of automated validators actively settling requests, it is typical to have a relatively large challenge period. It is important to note that every resolution window, including challenges after the first resolution window, is challengeable up until finalization.
Last modified 1mo ago
Export as PDF
Copy link