How SEDA’s Burn Works

How SEDA token burn works: deterministic burn tied to Oracle Program execution, network computation, and inherited security across SEDA Onchain and SEDA Fast.

The SEDA Network executes data requests across two delivery paths:

• SEDA Onchain, where Oracle Programs execute directly on the SEDA Chain.

• SEDA Fast, where execution inherits security and computation from the SEDA Chain.

In both cases, each data request consumes network resources, as Oracle Programs and Data Proxies are stored, executed, queried, and secured on the SEDA chain.

The value of that computation and inherited security is reflected in a deterministic token burn tied directly to execution across both delivery systems. As execution rates increase, the token burn scales proportionally with network activity.

Data requests, Oracle Program deployments, and transactions can be tracked on the SEDA explorer.

With SEDA, network usage, security, and burn grow together.