> For the complete documentation index, see [llms.txt](https://docs.vortexfinance.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vortexfinance.co/fund-security-and-resilience.md).

# Fund Security & Resilience

Vortex is designed with built-in safeguards and non-custodial infrastructure to ensure user funds remain secure throughout every transaction. From cross-chain transfers to fiat settlement, our system combines automated validation, fallback logic, and regulated partners to deliver reliability you can trust.

***

## 🔍 What Happens If…

### A Cross Chain Transfer fails

* Funds are only committed after full route validation.
* If any part fails, assets are returned to a fallback address on Moonbeam.
* SquidRouter and Axelar enable automatic retry logic.

### The FX rate changes mid-transaction?

* FX rates are locked when the user confirms the transaction.
* Any deviation is subsidized by Vortex—users receive the expected output.
* Oracle-based pricing and liquidity checks are performed before execution.

### A bridge to fiat fails?

* EURC & ARS.s via Spacewalk: Transfers only complete with bridge validation. If an issue occurs, funds remain recoverable on Pendulum.
* BRL via XCM: Transfers define fallback destinations in advance, ensuring asset return.

### The local partner doesn’t deliver fiat?

* Fiat redemption is handled by regulated fintech partners with audited, segregated accounts.
* Vortex holds direct SLAs and control processes to ensure reliability and compliance.

### 🔐 Core Security Features

* **Pre-Signed Transactions**\
  All steps are validated before funds move—preventing execution drift.
* **Fallback Mechanisms**\
  Recovery paths exist at every stage of the process.
* **No Custody by Vortex**\
  Vortex never holds user funds—smart contracts and partners manage all flows.
* **Rate Guarantee**\
  FX rates are locked at the start; slippage is covered by Vortex.
* **Ephemeral Accounts**\
  Temporary user-side accounts isolate funds and reduce exposure risk.

***


---

# 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.vortexfinance.co/fund-security-and-resilience.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.
