Emergency Fund Sweep Tool

WHAT IT DOES

This tool sweeps funds from a source wallet to a safe destination during emergencies, protecting assets from potential threats. It reads and displays the source wallet's native balance and added token balances, sweep eligibility (whether the caller is authorized), sweep status (pending, completed, or cancelled), account balance, chain ID, sweep history (number of past sweeps), and sweep threshold (minimum number of executions required). Beyond read-only access, the tool lets you execute the five key actions: sweep funds from source to safe destination, approve a sweep execution (if required), batch sweep multiple wallets or token types in one transaction, claim sweep confirmation, and cancel a pending sweep.

HOW TO USE

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

TECHNICAL MECHANISM

The tool interacts with an emergency sweep contract that allows authorized parties to move funds in emergencies. The sweepFunds() 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 sweep is justified. The sweepStatus() function returns the current state (0 = pending, 1 = completed, 2 = cancelled). The sweepThreshold() function returns the minimum number of executions required. Batch sweep uses sweepBatch() with arrays of sources, recipients, and token lists. The tool fetches sweep history via sweepHistory(). The confirmation prompt requires explicit user confirmation to prevent accidental triggers.

WHAT IT CANNOT SEE

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

PLEASE NOTE — EVM CHAINS ONLY

Supports Ethereum, Polygon, Optimism, Arbitrum, Base and similar EVM chains. The sweep contract must implement sweepFunds(), approveSweep(), sweepBatch(), claimSweep(), cancelSweep(), and sweepHistory(). The tool is read-write: it signs transactions for sweeping, approval, batch sweeping, claiming, and cancellation. Always verify the contract address, source, and destination addresses before submitting. Sweeping requires explicit confirmation.