Legacy Otto wallet retirement
The Mission Control Otto wallet on Base, earlier Otto Safes and new Otto trading permissions are retired. Mission Control no longer creates these accounts, offers funding for them or grants new permissions. Do not send new funds to a Mission Control Otto wallet or an earlier Safe. An exit does need a small amount of ETH on Base in the same wallet for network fees; if the wallet has none, email support@useotto.xyz instead of funding it. The Muse agent wallet at /app/agent-wallet is separate and still in use: signing in there creates a Coinbase account on Base, which you fund by hand with USDC for Muse’s research payments. Its research budget does not grant trading permission. Existing balances can be checked, and supported balances moved out. Open Legacy wallet recovery to:- sign in with the email you used for the original wallet and read its Base USDC and ETH balances. The page does not create a new wallet, and an unavailable reading is not a zero balance;
- review or stop an existing permission. It can no longer start swaps, stock buys or vault deposits; qualified vault withdrawals still work under it;
- withdraw from a supported vault and move eligible Base USDC out, as described in Moving funds out;
- check an earlier Safe linked to your connected wallet.
Which account am I using?
A DCA schedule’s Safe balance is separate from the Coinbase account.
Read your balances correctly
Legacy wallet recovery shows available Base USDC and ETH for fees in your existing Otto wallet. Its holdings section separately shows the wallet’s assets across supported networks (display only), supported Base stock tokens and Morpho vault positions; vault values are not included in available USDC. Connected wallets and earlier Safe balances are outside that section’s coverage. An unavailable balance is not zero. Account activity is your account’s record; public platform activity is not your personal transaction history. Stocks holdings describes supported assets in the connected wallet. Earlier Portfolio Co-Pilot views cover their own legacy accounts, not all of your Otto balances. Their yield suggestions are display-only.What a permission allows
Existing Model B permissions cannot start new swaps, stock buys or vault deposits. New permissions and replacements are also retired. A qualifying withdrawal from a supported Morpho USDC vault on Base remains available only when the existing permission is active, includes recorded withdrawal consent and passes the current account, expiry, permission-record and withdrawal checks. Otto verifies the supported vault share token, approved spender, share quantity and USDC destination. The withdrawal returns USDC to the same Coinbase account. Review the vault, share amount, expected USDC and fees before confirming an available withdrawal. Completed operations can still be read back. Use saved activity and its receipt/reconciliation controls for an earlier pending or uncertain operation; do not start a replacement trade. A public MCP connection does not activate your permission or give another agent access to it.Who enforces each limit
These limits describe existing permission records and provider policies. They do not enable new delegated trading.
These limits are not cumulative spending budgets or maximum-loss limits. An approval limit does not describe the value of a whole sequence of transactions. Retirement does not revoke an existing permission; check its status and confirm revocation when stopping it.
If Otto cannot confirm the recorded permission, it refuses a new withdrawal under it. A permission created or changed directly through Coinbase cannot restore retired trading or bypass Otto’s withdrawal checks. Older permissions without recorded withdrawal consent cannot be upgraded through the retired setup.
Where funds can go
Coinbase’s engine restricts the permitted contract calls, but it does not bind the output recipient of LI.FI routes. Its sign-only USDC transfer rule also has no recipient or network condition. Otto’s retained withdrawal path checks that USDC returns to the same Coinbase account. For an external transfer, Otto and the browser verify the reviewed Base network, destination, exact amount, Coinbase account identity and signature before submission. These are Otto’s integration checks, not guarantees made by Coinbase’s engine. A compromised Otto server could redirect funds within the engine’s limits. See What has been audited? for the distinction between provider security material and an audit of Otto.Expiry and stopping
The status card shows the recorded expiry of an existing permission. New or replacement Model B trading permissions and new trading under existing permissions are retired. Research-only agent authorization is separate and does not grant this trading authority. You can stop permission before expiry. Treat it as active until revocation is confirmed. Revocation prevents future use; it does not undo a submitted transaction or cancel a signature already created. Signing out is not revocation.Funding and moving funds
New funding is retired: do not send funds to a Mission Control Otto wallet or an earlier Safe. An exit moves native USDC on Base and needs a small amount of ETH on Base in the same Otto wallet for network fees; a connected-wallet balance does not pay them. If the wallet has no ETH, email support@useotto.xyz instead of funding it. Wait for the balance to be read before reviewing an exit. These are three separate actions:- Stop permission prevents future authorized use once confirmed.
- Redeem or sell a position returns assets to the account holding it.
- Transfer assets moves the available balance to another address.
If an action has no confirmed result
A timeout or missing answer does not prove that nothing happened. The transaction may have been submitted. Return to the same signed-in account and use its saved activity or transfer record to check receipts and the current status before starting another action. A transaction hash alone is not final confirmation. If permission status cannot be read, refresh it; do not assume permission has ended. If revocation is unconfirmed, treat it as still active. For a prepared or submitted transfer, use the specific recovery action shown in Moving funds out, rather than creating a replacement transfer. Contact support with the public transaction hash or reference if recovery cannot resolve it.Earlier Safe ownership
An account named “Otto Safe” is not enough to establish ownership:- Earlier operator-owned trading Safes give Otto’s execution key owner authority. Your connected wallet identity does not make you an owner; exits rely on the service’s withdrawal path.
- User-owned Safes with delegated execution can still give Otto broad authority over deposited funds. Check the installed permission, expiry and revocation controls.