> For the complete documentation index, see [llms.txt](https://docs.intents.aurora.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intents.aurora.dev/intents-connect/deep-dive/security-and-trust-model.md). # Security & Trust Model ### What the user signs Every action through Intents Connect requires an explicit user signature. The signed message contains the complete specification of the action: * Source wallet and source chain * Destination chain and target protocol * Asset, amount, and receiver * Maximum fee * Allowed execution path * Deadline and nonce Nothing outside this authorisation can be executed. The message is structured so it can be displayed clearly to the user before signing — the intent is human-readable, not an opaque hash. ### Replay protection Each intent includes a nonce and an expiry deadline. A signed intent cannot be replayed after it expires, and each nonce can only be used once per wallet. ### Scope of the intermediary account The intermediary account on the destination chain is fully controlled by the origin wallet that signs the intent. It: * Cannot act outside the scope of the specific signed intent * Cannot be triggered by any party outside the authorised execution path * Cannot execute any transaction without the explicit authorisation from the origin wallet ### Failure handling If execution cannot be completed due to gas spikes, protocol pauses, or other unexpected conditions, the system doesn't control the intermediary account, so explicit user authorisation is required. Unspent or stranded funds are not silently abandoned. The failure reason is surfaced to the UI, and recovery paths are available for every failure state. Read more about failure handling under [Execution Lifecycle](/intents-connect/deep-dive/execution-lifecycle.md). --- # 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.intents.aurora.dev/intents-connect/deep-dive/security-and-trust-model.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.