---
title: When the app is unavailable
description: The safety boundary and direct-access expectations during outages.
---

> **For AI agents:** the complete documentation index is at [llms.txt](/llms.txt). Append `.md` to any page URL for its markdown version.

The on-chain market is authoritative. The web app, API, indexer, media store, and
keeper improve access and liveness but cannot authorize an unsupported floor,
mint unbacked tokens, withdraw backing, or decide advance capacity.

When presentation services are unavailable:

- verify the chain, market address, implementation revision, and pause state;
- use the published SDK or verified contract interface for current reads;
- obtain a fresh on-chain quote and simulate the exact transaction before signing;
- set explicit slippage and a short deadline;
- reconcile any pending transaction or nonce before retrying; and
- avoid a site, RPC, contract, or token whose identity differs from the published
  deployment record.

Historical charts and indexed portfolio data may be stale even when direct chain
reads work. Conversely, if independent RPC providers disagree on chain ID, head,
or contract code, writes should stop until the disagreement is resolved.

During full pause, direct calls do not bypass the pause: repayment, surrender,
claims, and other state-changing actions can remain blocked. No operator or
off-chain service can promise that the pause will expire automatically.