Panic Button Fund Mover

WHAT IT DOES

This tool moves funds from a source wallet to a safe destination using a panic button mechanism during emergencies. It reads and displays the source wallet's native balance, added token balances, safe destination address, panic trigger eligibility (whether the caller is authorized), account balance, chain ID, panic history (number of past panic moves), and gas estimates. Beyond read-only access, the tool lets you execute the five key actions: trigger a panic move to transfer funds to safety, approve a panic move (if required), batch move multiple token types in one transaction, claim panic confirmation, and cancel a pending panic move.

HOW TO USE

Connect your wallet and select the network. Enter the panic button contract address, source address, safe destination address, and optional token addresses to move. Type "PANIC" in the confirmation field. Click "Load State" to fetch the source balance, your balance, panic history, and chain details. Review the source balance and panic eligibility. If you have sufficient balance and have confirmed, click "Trigger Panic" to move all funds from the source to the destination. If the contract requires explicit approval, click "Approve" first. To move multiple tokens at once, click "Batch Move." Click "Claim" to confirm a completed panic move, or "Cancel" to cancel a pending panic move. Each transaction shows confirmation and gas cost reporting.

TECHNICAL MECHANISM

The tool interacts with a panic button contract that allows authorized parties to move funds in emergencies. The panicMove() function transfers all native funds and specified tokens from the source to the destination. The contract validates that the caller is authorized and that the panic is justified. The batch panic uses panicBatch() with arrays of sources, recipients, and token lists. The tool fetches panic history via panicHistory(). The confirmation prompt requires explicit user confirmation to prevent accidental triggers.

WHAT IT CANNOT SEE

Cannot verify that the panic is genuine or that the destination is secure. Relies entirely on the panic button contract's verification and the destination chain's final state. Cannot detect if the panic is being used maliciously, if the destination is compromised, or if the panic is being performed by an unauthorized party.

PLEASE NOTE — EVM CHAINS ONLY

Supports Ethereum, Polygon, Optimism, Arbitrum, Base and similar EVM chains. The panic button must implement panicMove(), approvePanicMove(), panicBatch(), claimPanic(), cancelPanic(), and panicHistory(). The tool is read-write: it signs transactions for panic moves, approval, batch moves, claiming, and cancellation. Always verify the contract address, source, and destination addresses before submitting. Panic triggers require explicit confirmation.