SEDA’s Intent-Centric Framework

Omni-chain Data Transmission For Any Network

As previously mentioned, traditional oracle models were built to serve a blockchain landscape consisting of relatively few networks. The main use case for on-chain apps were DeFi, and oracles were designed to meet the needs of that time. In the current blockchain landscape, with hundreds of current chains and thousands more set to deploy, new networks require day-one access to oracle feeds.

Traditional oracles are built on network-centric architecture, which is designed to be compatible with the specific blockchain to which it is deployed. When an oracle wants to integrate with a new network, it is required to redeploy its entire infrastructure stack. With current demand rates, traditional oracles may face integration delays of anywhere between 3 - 9 months, depending on what architecture they use.

SEDA’s intent-centric framework mitigates the need for infrastructure redeployments by leveraging a decentralized network of Solvers that monitor SEDA Prover Contracts for inbound data requests. Solvers manage the cost of a data request by accepting any of their selected currencies. Solvers then relay the data request to the SEDA Chain, covering the value of the data request in SEDA Tokens. This is explained further in SEDA Token Primer.

The initial integration of the SEDA Network and the first access to any data is made up of a Prover Contract deployable to any network, decentralized Solvers monitoring the network, and access to or initial deployment of an Oracle Program.