Skip to content
YieldSeeker Docs

Recovery and emergencies

The connected wallet can sign an onchain withdrawal of available base assets from its Agent Wallet. Connected wallet · ownerAgent Wallet · base assetVault positions still need approved adapter exits

For a deployed Agent Wallet, ownership and wallet state are onchain; the app is not the source of ownership. If something goes wrong, avoid repeated transactions and record the wallet address, agent, network, and transaction hashes.

If the app is unavailable

Section titled “If the app is unavailable”

Your connected wallet remains the owner of a deployed Agent Wallet. The owner can submit authorized contract actions without the app, but the current Vault Agent’s direct withdrawal path is limited to available base-asset balances. Vault positions and other assets require permitted adapter operations and remain subject to the underlying protocol’s withdrawal conditions.

If you need to exit a position while the app is unavailable, contact support before attempting unfamiliar contract interactions. See the developer AgentWalletKit guide for contract-level details. An Agent Wallet address that has not yet been deployed still needs deployment before its contract can act.

If a transaction is pending or failed

Section titled “If a transaction is pending or failed”

Wait for the transaction state to settle before submitting another action. Check the network, transaction hash, wallet balance, and whether the underlying protocol accepted the operation.

If the same action continues to fail, save the error and contact support rather than repeatedly retrying.

If a protocol has an incident

Section titled “If a protocol has an incident”

At the contract layer, the Agent Wallet owner can block an adapter or target for that wallet; the platform’s emergency role can pause registry lookups or remove a target or adapter. Blocking or pausing stops affected adapter execution and may also prevent an adapter-based exit. These controls do not withdraw assets or create liquidity.

Do not assume that a high displayed APY, a registry pause, or an emergency response guarantees an immediate exit.

If you suspect compromise

Section titled “If you suspect compromise”

Do not approve unfamiliar transactions. Record what happened, disconnect the affected browser session, and contact YieldSeeker support through the official channel.

The Agent Wallet’s adapter restrictions and owner-controlled blocklist limit which contract interactions can run, but they do not eliminate software, market, protocol, or operational risk.

What to include in a support request

Section titled “What to include in a support request”

Include:

  • your agent and wallet addresses
  • network and asset
  • transaction hashes
  • the time and action that failed
  • the exact error message
  • screenshots that do not expose private keys or seed phrases

Never share a seed phrase, private key, signature you did not intend to authorize, or secret API credential.