Understanding Data Requests on SEDA Core

This page explains the data request life cycle when posting Data Requests to SEDA Core.

1. Developers build and deploy a new Oracle Program to the SEDA Network, OR access existing Oracle Programs and post/trigger requests using the Oracle Program ID

2. A data request starts a life-cycle via either a Push Solver triggering the request on predefined intervals, or a Pull Solver watching for published data requests.

3. The Push and Pull Solver post data requests to the SEDA Network for processing. A data request has an ID that matches the Oracle Program ID ensuring it is executed according to the correct computation logic.

4. An Overlay Network queries data sources listed in the execution phase of an Oracle Program returning raw data via a commit-reveal scheme to a data Tally Module.

5. The Tally Module applies the computation logic in the tally phase of an Oracle Program such as VWAPs, TWAPs, or any other custom logic embedded.

6. A single consumable data result is returned to the SEDA Chain for batching and tamper-proof resistance is applied.

7. The data result is relayed back to the Prover Contract on the target chain via Solvers where it can be consumer by User Contracts reading the SEDA Prover.