> 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/powering-intents-and-chain-abstraction-with-seda.md). # Powering Intents and Chain Abstraction with SEDA Learn how SEDA powers frameworks for Interoperability. The SEDA IVM fits into the settlement and execution part of the intent stack. SEDA is perfectly designed to provide the technical framework for facilitating settlement for intent escrows. When an Intent is processed on the target network, a data request is forwarded to the SEDA Prover Contract. This sends instructions to the Interoperability Verification Module on SEDA to query a selected set of RPC providers that monitor the chain state and events of contracts on the target network. If the Solver successfully filled the user’s intent, then SEDA will provide a proof that allows the escrow issuer to trigger an unlock. Resource efficiency and speed are crucial factors when Solvers are evaluating protocols to participate in. Leading intent-based bridges today can feature 2-4 hour dispute windows for settlement, locking Solver’s funds and reducing the potential earnings and rate at which capital can be redeployed. With SEDA, Intent protocols can theoretically lower settlement time to 15 seconds, enhancing resource efficiency for Solvers and increasing security for protocols, solvers, and users. --- # 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/powering-intents-and-chain-abstraction-with-seda.md?ask=&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.