🛸Powering Message-Based Interoperability with SEDA

The SEDA Interop Program

The leading interoperability protocols today leverage Relayers, which in some designs are referred to as ISMs (Interchain Security Modules) from Hyperlane or DVNs (Decentralized Verifier Networks). A Relayer is a piece of middleware infrastructure that monitors for messages on an origin chain, and forwards the message for settlement on a destination chain. Relayers in most bridge designs today either feature a mixture of external third parties that run the software internally, or a multisig run by the protocol itself.

Introducing the SEDA Interoperability Program — a powerful and customizable framework designed to connect any interoperability protocol to any blockchain's chain state in a permissionless and decentralized manner. This powerful framework enables existing bridge protocols to plug in to SEDA's infrastructure in minutes and unlock +500,000 new routes between networks, millions of native tokens, and benefit from 15-second settlement, all with little added cost to the end user.

How Does SEDA Power Interoperability?

SEDA plugs into the existing interoperability frameworks providing a decentralized alternative to commonly centralized co-signers that usually manage message attestations. SEDA’s interoperability programs can be used to add a layer of decentralization to any bridge route, resulting in:

• additional security

• support for any token, instantly

• permissionless deployments

• Liveness guarantees*

• interoperability with any network

The diagram below outlines an example of the flow of data and actors powering the Interoperability Program. In this framework the SEDA Network is tasked with verification of chain state and message passing from the Origin Network (e.g., Ethereum) to the target network (e.g., Solana). The Interop Program drastically improves the experience for bridge developers by removing the need for building and maintaining the Relayer and attestation piece of the stack, while reducing centralization risk.

To learn more about the architecture of the SEDA Network please follow along in the Litepaper Section of our docs.

*Liveness Guarantees - ensure a system will continue to provide data, and that no single centralized entity can shut down or limit access to data. In the case of SEDA, a data request that has been submitted, with the transaction fee paid, will always reach consensus. In this context, “Liveness Guarantee” is a technical term and the term “guarantee” should not be construed as any kind of legal guarantee.