Rescue Actions
The site has several action types. Choose the one that matches your case.
If you are new, do not choose only by the name. First answer a simple question: what exactly do you want to do with the wallet or assets?
This is what the choice looks like on step two of the workspace:

Remove Delegation
This action clears EIP-7702 delegation from added wallets.
Use it when:
- The wallet has active EIP-7702 delegation
- You want to remove delegated code
- You want to stop future actions through that delegation
Important: Remove Delegation does not change the private key. If the private key is already compromised, it stays compromised.
In simple words: this action removes delegated code connected to the account. It is like disconnecting a risky add-on, but the wallet key itself stays the same.
Prepare:
- The private key of the wallet where delegation must be removed
- The correct network
- A donor wallet to pay gas
When to Stop:
- The site says there is no delegation
- Nonce loading fails — the nonce is the address's transaction counter
- RPC cannot check delegation
- You are not sure you added the correct wallet
Custom TX Builder
The Custom TX Builder action lets you assemble several transfers into one flow and send them together. It has four transaction types, and the type you pick decides which fields you have to fill in.
The order of work is the same for every type:
- Add the private key of the wallet you are rescuing assets from. You can add several wallets.
- Press Add Transaction and choose a type.
- Fill in that type's fields.
- Repeat for the remaining assets and wallets.
- Build the transaction and move on to simulation.
The donor key does not go here
This list takes the keys of the wallets you are rescuing from. The site will not accept the donor's private key here: the donor only pays gas and signs the send.
Transfer Tokens (ERC-20)
The most common case: USDT, USDC and most other tokens. Suitable for a beginner as long as you know the token's contract address.
Fields:
- Token Contract — the contract address of the token you are moving.
- Decimals — a unit dropdown, where
Wei (10^-18)corresponds to 18 places. Ordinary tokens use 18, but there are exceptions: USDT and USDC use 6. The site tries to read this number out of the token contract and fill it in for you. If you are unsure, check it in an explorer. - Amount — how much to move. There is a "max" toggle next to it: with it on, the field reads "Transferring all tokens" and the amount comes from the full balance at execution time.
- Recipient Address — your new safe wallet.

If the decimals could not be read, set them yourself
Sometimes the site cannot get this number out of the contract. It then says Decimals could not be read from this contract — enter them yourself.
The field does not go empty. It keeps whatever was already in it, and a fresh ERC-20 transfer starts at 18 — so if the token really uses 6, a wrong number sits there looking exactly like a correct one.
Look the token up in an explorer, find its decimals, and set the dropdown to that number by hand. Every place you are out multiplies the amount by ten, and 18 where the real answer is 6 puts you twelve places out. Set the number too high and the transfer asks for a million million times what you meant: there is not that much in the wallet, so it fails — simulation will at least show you that. Set it too low and it succeeds, moving a speck of what you were trying to save, with nothing anywhere reporting a problem.
Transfer NFT (ERC-721)
For NFTs that exist as a single copy. One item moves per transaction.
Fields:
- NFT Contract — the collection address.
- Token ID(s) — the item's number inside the collection, for example
42. - Recipient Address.
The fee here is not a percentage but fee units: one per NFT transfer.

Transfer NFT (ERC-1155)
The same NFT family, except an item can exist in several copies and one transaction can move several different IDs at once.
Fields:
- NFT Contract.
- Token ID(s) — one number or several separated by commas:
42or1,2,3. - Transfer Amount(s) — correspondingly
10or1,5,2. The order must match the order of the IDs. - Recipient Address.

Custom Transaction
Full control over what goes to the network. Needed when an asset cannot be moved by an ordinary transfer — when you have to call a contract method, for example.
Fields:
- Target Contract — the address the call is addressed to.
- Calldata (hex) — the call data in hex form.
- Value (Native) — how much native coin to attach to the call, as a decimal or as hex wei. Usually
0. A Unit dropdown next to it picks the scale of that number:Etherorwei.
There is no recipient field here: where the funds go is decided by the calldata itself.
Do not use this type on a guess
The site sends exactly the data you entered and does not check what it does. A mistake in the calldata can send assets to the wrong place or burn gas for nothing.
If you do not know where to get calldata, use one of the three types above, or the DeBank Withdraw action.

A call written out by hand is charged like any other. If the calldata you paste turns out to be an ordinary ERC-20 transfer, the token service fee applies to it exactly as it would to a transfer built with the form above. The Fund Donor step shows it as a row saying the fee may not apply, because the site cannot tell from the data alone whether the call really moves a token balance — When a Fee Row Says It May Not Apply explains what that row promises and what it does not.
The "donor" Toggle Beside Recipient Address
On the three transfer forms above — ERC-20, ERC-721 and ERC-1155 — the Recipient Address label has a toggle next to it marked donor. Turning it on fills the field with the donor wallet's address, so you do not have to go back to step one and copy it. It is a shortcut for typing and nothing more: the transaction that gets built is the same one you would have built by pasting that address yourself.
Three things to know before you use it:
- The field stays yours to type in. The toggle does not lock it. Type anything that is not the donor address and the toggle clears itself.
- Turning the toggle off empties the field. It does not bring back an address that was there before, so you enter the recipient again from scratch.
- It does nothing until a donor exists. Before you have generated or imported one, the toggle cannot be turned on, and it says why: Generate or import a donor wallet first. Put the mouse on it, tap it, or reach it with the Tab key to read that.
The Custom Transaction form has no recipient field, so it has no toggle either.
The Donor Is a Stop, Not a Destination
Assets sent to the donor land on the wallet whose private key this browser is holding — and that is the wallet the site later offers to erase and to replace. Both of those destroy that key, and whatever is still sitting at that address when they do stays there for good.
So a rescue that sends to the donor is not finished when the transaction confirms. Move the assets on to your own new safe wallet through Donor Asset Withdrawal, and keep the donor's Export Backup file until you have. That is one transaction more, and gas for it, than sending straight to your own address.
If you already have the new safe wallet that Before You Start asks you to prepare, put its address in the field and leave the toggle alone.
Permit Rescue
Permit Rescue uses token permit signatures when the token supports the required standard.
Supported ideas:
- EIP-2612
- EIP-3009
- DAI-like permit
This action is useful when token transfer can be approved by signature instead of a separate approval transaction.
In simple words: some tokens let you sign permission for a transfer without sending a separate approve transaction. When you add a token, the site asks the network which kind of Permit the token supports and fills in the amount with the wallet's balance. Once the check finishes, you generate permitData.
Only tokens that passed the site's Permit check can be selected here. Tokens this panel cannot sign a permit for can be rescued with Custom TX Builder.
Prepare:
- Private key of the wallet holding the token
- Token contract address
- A donor wallet: the rescued tokens go to it, so there is no recipient address to enter
- Amount or balance-at-execution mode
You do not choose a deadline. Until you sign, the Permit deadline field shows "Set automatically when you sign": signing sets how long the signature stays valid, and the field then shows the time it expires. The window is short on purpose, so sign when you are ready to go through the remaining steps straight away.
The site watches that time for you and stops before an expiring signature can be sent. The cure is always the same — sign again in this panel and build again — because nothing later in the process can extend a signature. Where you see it depends on how far you got:
- Before you build. Shortly before the deadline, the Build Transaction button disables itself, even if the panel is just sitting open, and its explanation says "This permit expires too soon to fund the donor and send the rescue before it does. Sign again to get a fresh one." Once the deadline has passed it says "The permit deadline has passed. Sign again to get a fresh one — an expired permit only spends gas." Press Generate & sign permitData again, then build.
- After you build. A plan built from permits never outlives them: it expires, at the latest, shortly before the earliest of its signatures does. When the signatures no longer leave enough time, TX Simulator shows a notice saying they expire too soon and disables Run Simulation, Proceed to Fund Donor and Continue Anyway. Once the plan has expired for that reason, Fund Donor says "The Permit signatures this plan relies on expire too soon to fund the donor and send it. Planning again will not help: go back to TX Builder, sign the permits again and approve the new plan." and its Return to TX Builder and sign again button takes you there. TX Sender says the plan can no longer be sent and does not send it.
- While sending. A rescue can take two transactions: first deploying the rescue contract, then the rescue itself. The site checks the time again before each one and does not send a step the signatures could no longer get through; the log shows which steps already went through. Press Retry — Back to TX Builder, sign again and build a new plan. If the contract was already deployed, the new plan first checks whether it can be reused, and if it can, you do not pay for it again. In the rare case a signature expires while a step is on its way, the rescue contract refuses that step: it moves no tokens, and only its network fee is spent.
Min received (base units) is the smallest delivery you are willing to accept: if less than that arrives, the rescue is rejected rather than going through. The service fee is 20% of the rescued amount and comes out of the tokens themselves, so the calculation leaves 80% — but that 80% is a calculation, and it leaves out what the token itself charges for a transfer. Choose the minimum below what you expect to receive rather than copying the calculated figure into it, or a token that charges for its own transfers has your rescue rejected for arriving short.
When to Stop:
- The token shows No Permit
- The token shows Not checked and Retry check does not help — switch the RPC endpoint and try again
- The row warns that the wallet had a delegation installed: some tokens refuse signatures from a delegated wallet. Run Remove Delegation first
- Signing fails
- The site asks you to regenerate permitData after changing amount, mode, donor wallet, network, or token context
- You do not understand what amount will move or what minimum should arrive
What can go wrong:
- The note on the EIP-2612 badge says the standard format is assumed: the token does not say which Permit format it uses. If it uses another one, one of two things happens. Either the rescue fails as a whole: nothing moves and no service fee is taken, but the network fee already paid for the transactions sent stays spent — the failed one, and the contract deployment if it went first. Or it goes through without moving that token: the network fee is paid, and so is the service fee in the network's own coin if one is due. The check before sending does not show the second case, so after sending, check that the token arrived; if it did not, rescue it with Custom TX Builder
DeBank Withdraw
DeBank Withdraw loads portfolio data from DeBank and helps prepare supported withdrawals.
The current flow focuses on supported Bundler token transfers and pool exits.
If DeBank does not show assets or returns an error, check:
- Network
- Wallet address
- RPC
- DeBank availability
- Whether the asset is supported by the current flow
In simple words: the site tries to find assets through DeBank and prepare withdrawals only for assets it knows how to handle. Not every DeFi position can be withdrawn automatically.
Prepare:
- Private key of the wallet with assets
- Correct network
- Recipient address
- Time for DeBank data to load
- Confirmation that selected token or pool positions are actually supported
Check Permit Compatibility
If a Permit token is selected inside DeBank Withdraw, sending may be unavailable for that variant. Use supported Bundler token transfers and pool exits when the site clearly allows you to continue.
Scenario Comparison
| Action | When to Use | What to Prepare |
|---|---|---|
| Remove Delegation | Need to clear EIP-7702 delegation | Private key of wallet, donor, correct network |
| Custom TX Builder | Need to move tokens or NFTs manually | Private key, contract addresses, recipient, network |
| Permit Rescue | Token supports permit signatures | Private key, contract address, donor wallet, network |
| DeBank Withdraw | Assets are visible in DeBank and supported | Private key, recipient, time for data load, network |
How to Choose
If you need to clear EIP-7702 delegation, choose Remove Delegation.
If you need to transfer normal tokens or NFTs through a prepared batch, choose Custom TX Builder.
If the token supports permit and you need a permit-based transfer, choose Permit Rescue.
If assets are visible in DeBank and the site supports the withdrawal, choose DeBank Withdraw.
If You Still Do Not Know
Do Not Guess
Do not guess. Use this safer order:
- Check the network and recipient.
- Create a donor.
- Choose the simplest action for one asset.
- Build the transaction.
- Run simulation.
- If the result is unclear, do not send.
Next
- Simulation, Funding, and Sending — what happens after building.
- Service Fees — what each action is charged.
- Affiliate Link — how the fee is split.
