> For the complete documentation index, see [llms.txt](https://docs.seda.xyz/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seda.xyz/home/archvie/interoperability-verification-module-ivm.md).

# Interoperability Verification Module (IVM)

IVMs are a plug-and-play solution for interop protocols, increasing security, providing horizontal scaling, and enhanced decentralization.

The SEDA IVM is a powerful framework built on top of the SEDA Network and designed to lead the emerging verification market by addressing default verification challenges through programmability, horizontal scalability, and a distributed network architecture consisting of layer one chain security inherited from the SEDA Main Chain. \
\
The SEDA IVM was designed around **three core pillars** that form the foundation of the IVMs powerful framework:

<figure><img src="https://4237789557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTQafbsjeB6Wu0r07ksa%2Fuploads%2F3TRHtQhkaX0OZT3Metme%2FScreenshot%202025-02-07%20at%2012.07.12%E2%80%AFPM.png?alt=media&amp;token=c35e1950-6ef4-418e-abf6-cd2ee19b409a" alt=""><figcaption></figcaption></figure>

**Security**

Unlike customizable verification stacks, SEDA provides a single security zone encompassing all chains with a permissionless SEDA Prover contract. Applications, protocols, and networks can join this unified security zone through a simple IVM deployment.&#x20;

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfPTC3s0q0eF_NQ0jEQPy1hyMYrNAwWFTpbhJGjMovt10MNpNjgD07TgRx7QhE26Him4TacMBDTbQ7YgnMnaggFJdY5Nfx1P37q8vRzPkrMyt3UD9E9G4y6ZenArZ5BRrU-DFdB1A?key=wMtggz7OaEY_UO1Gpzg7KkrR" alt=""><figcaption><p>A visual representation of the SEDA shared security zone for interoperability routes.</p></figcaption></figure>

The SEDA IVM framework seamlessly integrates into interoperability protocols as part of their security stack.

<figure><img src="https://4237789557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTQafbsjeB6Wu0r07ksa%2Fuploads%2FBW65DvusMZI6n866fhR2%2FScreenshot%202025-02-07%20at%202.18.43%E2%80%AFPM.png?alt=media&amp;token=6e73fa4f-a943-40b7-9609-156525520f8a" alt=""><figcaption><p>SEDA Verification Module security as compared with current verification and relay setups.</p></figcaption></figure>

**Scalability**\
\
SEDA's architecture combines a Proof-of-Stake main chain secured by over 100 validators with a distributed Overlay Network of thousands of nodes. This design prevents downtime through workload distribution. If nodes on the main chain or Overlay Network go offline, the distributed nature of SEDA’s model ensures other nodes can step in.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXf4qJjGboh0ou2YU1b9m_WXdZCHIq8D0buqeaX8ada6Dy-cBmRJG1BCwteNGuPDVspUtDJ7IQgXOl5Ilh-MlNZdtOteRg87VNWlfOy8837Xi-rvPfbZ0YZIjyC1HjzPMTHUGorkBg?key=wMtggz7OaEY_UO1Gpzg7KkrR" alt=""><figcaption><p>A visual overview of liveness guarantees within the SEDA Network.</p></figcaption></figure>

**Programmability**

Unlike traditional multi-sigs, where protocols can only use limited signers (1/1 or 2/3), SEDA IVMs allow protocols to customize their verification committee size from the Overlay Network. Decentralization in SEDA is a sliding range that can be adjusted to include more nodes in a committee leading to increased decentralization for verification.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfDHL4D_5LH8e1hGhKTlv7Xyb2m5Hz0eXaoBFNunn3mtZ2z4uI7bYUrKBZOkeewnHTsFJKM5Znl22Srb_TWvNGiFe3hvFcBal0in_fMiONz0soApq7geFeg-E2wFan2YQDAy6EbnQ?key=wMtggz7OaEY_UO1Gpzg7KkrR" alt=""><figcaption></figcaption></figure>

The SEDA IVM is designed to a light-weight integration with horizontal scaling as a default. Integrating the SEDA to your network requires one simple SEDA Prover deployment. Integrating the SEDA IVM into your existing interoperability stack is straight-forward and fast. Learn more about the benefits of SEDA at a glance below:&#x20;

Learn more about how SEDA can be leveraged to create permissionless verification below.

{% content-ref url="/pages/Xa5Z44ODeHGtIQa4CYqT" %}
[Interop Verification Module for Message-Based Bridge Protocols](/home/archvie/interoperability-verification-module-ivm/interop-verification-module-for-message-based-bridge-protocols.md)
{% endcontent-ref %}

{% content-ref url="/pages/hO1z1eJHgWj8YqEBXEtK" %}
[Powering Intents and Chain Abstraction with SEDA](/home/archvie/interoperability-verification-module-ivm/powering-intents-and-chain-abstraction-with-seda.md)
{% endcontent-ref %}

<figure><img src="https://4237789557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTQafbsjeB6Wu0r07ksa%2Fuploads%2FjGKHycEN6ayB1eUSKbya%2FScreenshot%202025-02-11%20at%2010.26.03%E2%80%AFAM.png?alt=media&amp;token=5a03f2bd-bc6a-4c71-88e7-27e54da5b1ff" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.seda.xyz/home/archvie/interoperability-verification-module-ivm.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.