The On-Demand Oracle System
Broadly speaking, the contracts can be categorized in five ways. On the far left of the diagram are the contracts that hold permanent user data that is independent of any data request. The contracts in the bottom half of the middle handle deployment of the on-demand contracts that handle each request. The right side of the diagram contains the contracts that work together to handle all of the data that is sent in. These contracts also play a big role in consensus. The contracts towards the top of the diagram are the contracts that handle dataset configuration, staking, and disputes. The contracts with a name that looks like OD* are deployed when a new request batch is registered. The last category of contracts help connect and control the other contracts by acting as data stores (e.g., RequestDetails) or, in the case of the OnDemandMain, coordinate interactions across branches of the system.
In the first section of the manual, we'll cover all the ways in which the ODO can be interacted with. We'll cover the roles that system users can fill, the tasks they can perform, and how they can perform them.
In the second part of the manual, we'll go into great detail, covering how the ODO handles various occurrences and why it behaves the way it does.
Last updated
