Network Participation

SEDA network participation model covering builder execution costs, solver token balances, validator staking, delegation, and the role of tokens in sustaining network operations.

Builder Participation

SEDA tokens are required to enable core network operations by covering native network costs associated with computation, data request execution, and deployment of Oracle Programs and Data Proxies within the SEDA Network.

As more builders and data providers join the SEDA Network this increases exposure to network participants requiring SEDA tokens for specific actions on the network.

Solver Participation

Solvers operating on the SEDA Network relay data requests and data results between requestors and the Network. Requestors settle data request costs with Solvers in any currency accepted by the Solver.

Solvers maintain a balance of SEDA tokens which are used to relay requests from the Solver to the SEDA Network. As Solvers continue to participate in the Network, their token inventory is consumed through the execution process, requiring ongoing replenishment of SEDA tokens for ongoing participation.

Validator & Delegate Participation

Participation in the SEDA Network security requires staking.

Validators stake SEDA tokens to participate in consensus by producing blocks and signing batches. Overlay node operators stake tokens to operate nodes used to query data sources within the onchain delivery execution. Delegators bond tokens to validators to participate in securing the network.

Increased network participation reinforces network security and integrity, which reinforces trust, which flows on to reinforce adoption — indirectly resulting in adding to more data requests on the SEDA Network.