> For the complete documentation index, see [llms.txt](https://docs.axis.to/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.axis.to/risk/custody-liquidity-risk.md). # Custody & Liquidity Risk USDx depends on assets and operations outside the token contracts. Backing assets sit on the trading venues where the strategy runs, while secondary-market liquidity depends on external venues. Onchain controls cannot guarantee that those assets remain available or that USDx can always be exited near $1. ## Custody and collateral The primary market (`USDxMarket`) settles a mint order by routing collateral to a registered custody channel before USDx is minted. Because the strategy requires liquidity positioned on the venues themselves, the backing is held **on-venue** at trading venues; Axis does **not** currently use off-exchange settlement or off-exchange custody (see [Backing, Custody & Transparency](/backing-reserves-and-transparency/backing-custody-transparency.md)). Safety then depends on key management, legal access, operational processes, and each venue's continued availability and solvency, the venue exposure covered in [Venue & Counterparty Risk](/risk/venue-counterparty-risk.md). A supported collateral asset can also lose value, liquidity, or redemption access. An approved route and channel prove that the contract accepted a settlement path; they do not prove the real-time value or availability of assets held there. The backing is designed to be **over-collateralized** against a target level, so that reserve contractions are intended to be absorbed by that buffer rather than passed straight through to holders, a design intent sized against reserves, not a reserve fund and not a guarantee. What can and cannot be independently verified about this backing is documented separately in [Backing, Custody & Transparency](/backing-reserves-and-transparency/backing-custody-transparency.md). ## USDx liquidity and redemption USDx can trade above or below its $1 target. Secondary-market liquidity can disappear or become expensive during stress. The mint and redemption path can support price alignment, but it relies on authorized operators, available collateral, custody access, and configured capacity limits. Those dependencies can delay or constrain exits. The protocol does not guarantee continuous AMM liquidity or an immediate $1 redemption for every holder. ## sUSDx redemption timing sUSDx adds vault and redemption-process risk. Redeeming sUSDx is **asynchronous** (modeled on ERC-7540), not instant. The cooldown is currently **7 days**. When you `requestRedeem`, the vault burns your sUSDx and moves the corresponding USDx out of active vault assets (`accountedAssets`) into a reserved **pending** liability, where it earns no further vault rewards. The cooldown lives inside the vault as pending and claimable liabilities. There is no separate cooldown-escrow (silo) contract. Once the cooldown elapses, the request must be **serviced** (an account holding the redemption-servicer role marks it claimable), which shifts the reserved USDx from the pending bucket to the **claimable** bucket. Only then can you claim the underlying USDx. A request can be **cancelled while it is still pending**, which restores the burned shares. So exit is not immediate: servicing depends on an operator acting, and the USDx price and market conditions can change between request and claim. Reserved pending and claimable assets are tracked as vault liabilities, but the vault must actually hold enough USDx to honor them. Vault rewards themselves come from Axis's trading results, a market-neutral yield whose structural edge is cross-venue and cross-asset fragmentation, a durable source that does not rely on any single mechanism. Funding is one component (and can be the larger share in a given period); see the Transparency Dashboard for current attribution. A period with weak or undelivered results simply produces no new rewards, and reward delivery is not guaranteed. See [What is sUSDx?](/susdx-the-rewards-vault/susdx.md) for the full lifecycle. ## Risks can compound A custodian or venue failure can make assets unavailable, leave a hedge incomplete, reduce redemption capacity, and weaken confidence in USDx at the same time. Diversification and limits can reduce concentration, but they cannot guarantee access during a correlated event. Read [Backing, Custody & Transparency](/backing-reserves-and-transparency/backing-custody-transparency.md) for what can and cannot be independently verified, [How USDx Targets $1](/usdx-the-synthetic-dollar/peg-stability.md) for the price-stability path, and [Venue & Counterparty Risk](/risk/venue-counterparty-risk.md) for venue controls. --- # 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.axis.to/risk/custody-liquidity-risk.md?ask=&goal= ``` `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.