> 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/seda-overview/secure-and-trustless-verification-the-seda-ivm/an-ivm-summary.md).

# An IVM Summary

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXd545pPkFH6kJAW9iXpR5Dn9I4uzWOnYIR5jYe57qhg64zy9ColBvU_t2THJUR4wUm_GXaNggurk3FdcvPRGBzPYW0w5OlEv2Xb6iqZQIbub2yKNqzAG2yAPgI8O8y-ppZ-r4517Q?key=h0ufnoXm9WpA6FLzGDL0I2bS" alt=""><figcaption></figcaption></figure>

IVMs are a direct response to the emerging market need for hyper-specialized verifiers to support interop’s secure expansion across every network and VM.

SEDA IVMs are accessible by networks, interop providers, abstraction layers, or any other infrastructure that requires them. Deploying any module, including the prover contracts required to pass proofs on target chains, is permissionless on SEDA.

Where default security verification creates single points of failure, with a high risk of downtime, SEDA IVMs specialize in mitigating common attack vectors, offering a customizable and scalable method to integrate interop to any route for any token swap on day one.

Learn More About SEDA for Interop in the following sections:

1. [Powering Interoperability Across Web3](https://docs.seda.xyz/home/for-developers/powering-interoperability-across-web3)
2. [Powering a Permissionless Future For Interoperability](https://docs.seda.xyz/home/learn/powering-a-permissionless-future-for-interoperability)


---

# 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/seda-overview/secure-and-trustless-verification-the-seda-ivm/an-ivm-summary.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.
