How a rescue works

A drained wallet usually has no gas left, and anyone holding its key is watching for incoming funds. Sending gas to it just hands that gas to the attacker. RescueFi gets around this with EIP-7702, which lets the compromised wallet act through a contract for one transaction, paid for by a different wallet.

Two signatures, made in your browser

1. An authorization (EIP-7702). It lets the compromised wallet behave like the Rescuefi contract for the rescue. Skipped if the wallet already has it from an earlier rescue.
2. A transfer approval (EIP-712). It names the tokens to move, the safe wallet, the referrer if any, and a deadline one hour out.

Both are produced by the compromised key on the page. No wallet app is involved and nothing is sent anywhere yet.

One transaction, paid by your sponsor wallet

The app creates a small sponsor wallet in your browser. You fund it with just enough gas, and it sends the rescue transaction. The Rescuefi contract then moves each token in the same transaction: 80% to your safe wallet, 20% to RescueFi's fee wallet.

Because the compromised wallet never holds spendable gas, there is nothing for the attacker to take.

What you see

Step 3 shows each part as it happens: the rescue sent, the block it was confirmed in, and which tokens moved. A token the contract could not move is reported on its own and costs nothing.