> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useotto.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Hyperliquid retirement & recovery

> Otto Hyperliquid trading is retired. Market research remains; existing accounts require protected recovery and reconciliation.

**Otto Hyperliquid trading is retired.** Do not fund an Otto Hyperliquid account, open a new position or construct a Hyperliquid order through Otto. This applies to ACP, x402, MCP and installable skills. There is no planned trading launch through the `otto-perps` skill.

Hyperliquid market research remains available through Otto's research and market-data services. Research about prices, funding or open interest does not authorize execution or establish an account's balance.

## Existing accounts

Retirement does **not** establish that every account is empty, that every position is closed or that every withdrawal has settled. Existing balances, orders and positions need a current account read and reconciliation before any recovery action. If that read is unavailable or stale, the account state remains unknown.

The legacy execution path uses a separate provider-hosted margin account and Otto-managed signing authority. It is distinct from a connected wallet and from the trading Safe associated with the buyer identity. Connecting to the app does not transfer control of that account or export its key. See [Accounts & permissions](/account-and-settings/accounts-and-permissions).

## Protected recovery only

Recovery is limited to the affected existing account under its existing owner authorization. The service's current recovery contract determines which account reads, cancellations, exposure-reducing closes and withdrawals remain supported. Do not infer permission from a historical offering, a cached catalog or an old order example. New deposits, new positions, increased exposure and order construction are outside recovery.

1. Establish the account identity, owner authorization and a current balance, position and open-order snapshot. Keep the original request and transaction identifiers for any unresolved action.
2. Reconcile outstanding orders and fills. Where the protected recovery contract permits it, cancel orders and reduce or close existing exposure; verify the amount actually closed. A partial close leaves exposure, and an unknown result requires reconciliation before another request.
3. Request only an authorized withdrawal of established available funds. The retained x402 withdrawal returns to the mapped **Arbitrum Safe** and accepts no recipient override. The retained ACP withdrawal alias also returns there first, but `deliverToButler` defaults to `true` and can automatically start an onward bridge to the buyer wallet on **Base**. For withdrawal-only recovery, explicitly set **`deliverToButler: false`** to leave funds in the Arbitrum Safe. Authorize any onward bridge separately and verify its destination receipt; do not assume that submission proves delivery.
4. Verify the remaining account state and the destination receipt separately. A submitted withdrawal, a service response or an intended bridge does not prove settlement.

There is no promised close-everything-and-withdraw operation or self-service vault-key export. Recovery depends on the retained protected service path being available; its exact manifest and account balances must be verified. See [Removing funds](/account-and-settings/removing-funds) for the other account regimes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.