Create or import a donor wallet locally, export the backup, then continue through the full recovery flow in one browser workspace.
Important: use this public browser-based workspace only on a trusted machine you control. Never share the donor wallet private key, mnemonic, or exported backup JSON with anyone. Anyone who gets these secrets can take all funds, so store them offline in a safe place. Do not refresh the page until the recovery flow is finished and every intended withdrawal from the donor wallet is complete. Secret keys remain in this tab's session storage until the tab is closed or session data is cleared. This site is currently in beta, is fully vibe coded, and is provided for informational preview purposes only. The site administrators are not responsible for any actions you take here or for how you choose to use this site.
This field stays locked until you choose Edit. Enable editing before you paste or revise the donor private key locally in this tab.
This field stays locked until you choose Edit. Enable editing before you paste or revise the donor mnemonic locally in this tab.
Generate locally, export the JSON backup, then continue into the next action.
A fresh donor wallet exists in the current browser tab.
The JSON wallet file has been downloaded and can be stored safely.
The Actions screen becomes available after the backup requirement is met.
Pick a network, refresh balances, and withdraw leftover native or ERC-20 assets from the donor wallet.
Select a network and refresh the donor native balance.
Enter a token contract, choose a network, and refresh the donor token balance.
Open the page and start creating or importing the donor wallet without extra navigation.
Actions stay locked until the donor wallet backup has been downloaded.
Donor wallet setup, Actions, TX Builder, funding review, and sending stay connected in one tab.
Generate the address, private key, and mnemonic locally inside the browser session.
Download the JSON wallet file before continuing so the wallet can be restored if needed.
Choose the recovery route, then continue into TX Builder for network and authority setup.
The gate prevents the operator from moving forward without a recoverable wallet export.
Yes. The Donor Wallet screen also accepts your own donor private key or mnemonic. Generating a new wallet is optional.
The current flow is Donor Wallet, Actions, TX Builder, Fund Donor, and finally TX Sender. All routes pass through TX Builder, and each step unlocks when the previous step has valid data.
ERC-20: 20 percent per transfer transaction.
Transfer All Native: 20 percent of the swept native balance, with the remaining 80 percent routed to the donor wallet.
NFTs: 5 USD in the network native token for each NFT fee unit.
Pure custom TXs: 5 USD per TX only when the bundle has no token or NFT transfers.
Every ERC-20 transfer transaction is split into two calls: 20 percent of the token amount is routed as the protocol fee share, and the remaining 80 percent goes to the recipient you entered. This is applied per ERC-20 transfer transaction, not once per bundle.
When you enable Transfer All Native for a compromised wallet, the dispatcher appends one execution-time native sweep for that wallet. It runs after that wallet's other calls, applies a 20 percent protocol fee share to the remaining native balance, and routes the remaining 80 percent to the donor wallet.
ERC-721 transfers are counted per NFT. ERC-1155 batch transfers are counted per token ID in the batch. Pure custom TXs are charged per TX only when the bundle has no token or NFT transfer at all. This 5 USD native fee logic is separate from the 20 percent execution-time native sweep fee used by Transfer All Native.
The site first checks whether the donor wallet already covers the required native fee. If not, it can allocate the fee from the unique compromised wallets in the current TX Builder set when their combined native balances are sufficient. Transfer All Native does not add to donor top-up for this fee, because its own 20 percent native fee is taken directly from the swept compromised-wallet balance during execution.
If the current chain is custom or unsupported for price lookup, the site skips the USD-to-native fee quote because it cannot safely price the native token.
The current tab restores the active wallet, selected route, network context, and transaction metadata from session storage after a normal refresh. Close the tab or clear session data to remove them.
Address, private key, and mnemonic are generated locally in the browser. In the current implementation, the active wallet is also kept in this tab's session storage until the tab is closed or session data is cleared. You can also export the backup JSON explicitly.
The donor wallet is prepared. Choose whether the next recovery route is delegation removal or a custom TX Builder flow. Both continue through TX Builder setup.
Choose a recovery route on Actions to load the required inputs.
Choose the target EIP-7702 network first. Public RPC send remains available, but a custom MEV-protected or private-orderflow RPC is recommended for the final send path.
Enter one compromised private key per line. Both 0x... and raw 64-hex formats are accepted.
Resolve token decimals from chain state or enter them manually.
Need to build TX data from scratch? Open ABI Encoder and paste the generated calldata back here.
Set one shared recipient for every selected ERC-20 transfer-all call in this route.
Search by token symbol or token name inside the balances loaded for the active wallet.
Choose the network and add a valid compromised wallet private key to load ERC-20 balances.
Debank returned a rate-limited or invalid response. Waiting 5 seconds before retrying.
Set one shared recipient for every selected pool withdrawal call in this route.
Search by project, pool name, or adapter ID inside the positions loaded for the active wallet.
Choose the network and add a valid compromised wallet private key to load pool positions.
Debank returned a rate-limited or invalid response. Waiting 5 seconds before retrying.
Review how much native balance the donor wallet still needs before the send step, including service fee, dispatcher deploy reserve, and the final rescue execution reserve.
This screen turns the current TX Builder state into a donor funding snapshot before TX Sender opens.
Current donor native balance appears here after the funding estimate resolves.
The native-denominated service fee quote appears here.
The current staged gas reserve estimate appears here.
This is the current staged native target reserved for TX Sender.
Use the prepared TX Builder payloads only after the network context and transaction set are fully validated. Public RPC send remains available, but a custom MEV-protected or private-orderflow RPC is recommended for better orderflow privacy.
This screen is unlocked once TX Builder has at least one valid prepared transaction and a working network context.
Awaiting sender execution.
Build calldata locally from a raw type list, a function signature, or a JSON ABI.
Example: transfer(address _to, uint256 _value)
Only callable functions are listed here. Constructors, events, fallback, receive, and errors are ignored automatically.
Paste a valid source above to generate the argument fields.
Convert one EVM value across common units locally in the current browser tab.
Gas estimation failed. Enter a gas limit to continue.
Default: 5,000,000