> For the complete documentation index, see [llms.txt](https://docs.evodefi.com/evodefi-the-next-generation-cross-chain-bridge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.evodefi.com/evodefi-the-next-generation-cross-chain-bridge/evodefi-bridge/evodefis-cross-chain-bridge-deep-dive/risk-mitigation.md).

# Risk mitigation

As we are a permissionless bridge and not a liquidity pool, a customers funds are only ever under our custody during the few seconds it takes to pick up a transaction and forward it on another chain. There is no human interaction with any funds or data during this process, it is entirely automated by the operator and the smart contracts on each protocol.

We have complex alert systems and staff on hand 24/7 to address any concerns and update users on any questions they may have. To date we have never had customers lose funds, and we plan to keep it that way. We care very much about our community and understand that without you, EvoDefi could not exist.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.evodefi.com/evodefi-the-next-generation-cross-chain-bridge/evodefi-bridge/evodefis-cross-chain-bridge-deep-dive/risk-mitigation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
