Components
The SEDA Network Architecture
The blockchain network is responsible for the network’s security, consensus, and generating the proofs for supporting interoperability with sub-chains. The main chain is composed of a contract deployed on a high-scalable L1 blockchain and a P2P overlay network that is used for consensus. It acts as an anchor and a single point of truth for main chain and data request validators.
A blockchain network in the SEDA network where a SEDA contract is deployed to it. This contract allows for full subchain interoperability by parsing proofs generated by the SEDA main chain. Any protocol or smart contract can seamlessly interact with the SEDA protocol and all of its resources without any need to interact with the main chain. Data responses will be forwarded back to the subchain where it was created.
A smart contract deployed to a subchain that allows users and protocols to query cross-chain or real-world data.
Bridging nodes forward requests from subchain contracts to the main chain. From there, the validator nodes will be listening and addressing each data request that comes in. Once the consensus on the data request is reached, the bridging nodes will send the data update out to all of the subchains where the requests required them to be sent to. Bridging nodes will also send the main chain state to the subchains to ensure that the block-containing data requests and their execution are consistent across all blockchains.
A set of data resolvers is randomly and anonymously selected to retrieve information from one or more sources. Their outcomes are transformed, aggregated, and reduced into a single data output which can be later consumed by any subchain smart contract.
Random secret selection will rely on cryptographic primitives such as Verifiable Random Functions (VRFs). Additionally, resolvers will follow a commitment scheme to deter malicious behaviors that may affect data request quality (e.g., coordinated attacks, free-riding. etc.).
Fishermen monitor the network and report malicious behavior from validators and bridges. Anyone can perform the fisherman role. For example, they help protect the system against main chain validators double signing and bridge nodes from relaying non-existent data requests.
Last modified 2mo ago