Recovery and emergencies

YieldSeeker is designed so that the app is not the source of ownership of your assets. If something goes wrong, stay calm, avoid repeated transactions, and record the wallet address, agent, network, and transaction hashes.

If the app is unavailable

Your Agent Wallet and its on-chain state remain on the blockchain when the interface is unavailable. Contact support before attempting unfamiliar contract interactions.

Technical users can review the developer AgentWalletKit guide and the deployed contract sources for recovery options.

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

YieldSeeker may restrict a protocol or pause automated operations when a supported integration presents a material risk. A pause can stop new automated operations, but it cannot create liquidity that the underlying protocol does not have.

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

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 platform’s emergency controls and adapter restrictions are described in Security. They reduce the impact of compromise but do not eliminate every risk.

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.