🟨Basic flow
Toggle eth_sign requests
To allow dApps to request your signature using 'eth_sign' requests, you need to turn on this setting. Please note that 'eth_sign' is an open-ended signing method that allows you to sign an arbitrary hash, which can be a dangerous phishing risk. Only sign 'eth_sign' requests if you are able to read and understand what you are signing and trust the request's origin.
⚠️ If this setting is turned off, your MetaMask will not be able to connect to the Wallet Rescue app. You will need to manually turn on this function. ⚠️
The user flow depends on the required actions. For example, if you want to withdraw tokens from a staking contract but your account is hacked, any tokens transferred to your account will go to the hacker's wallet.
Or, your account's (0x1d0fBBc026243b79d27c2FB891002Ccf9bC60EE6) private key was compromised (Ex. 0x7eea14f731c1691b56238e777a67674d40de1bdd544f883e733549f6915d7961), and all funds in your wallet were transferred to the hacker's wallet. Also, the hacked account initiates some stakes, and you want to claim your stake without losing funds.
To begin, you must transfer native currency to your account by selecting the 'Native Token Transfer' transaction type
After completing the native token transfer, a new transaction block will appear in the bundle section. Clicking on the block will open a form where you can specify the sender and receiver account addresses, as well as the transfer amount.
After filling required parameters, you should sign a transaction with the sender's wallet.
After clicking the “Sign” button, the app will open Metamask wallet with a signature request. You should approve the signing.
If the signing is successful, the transaction block should display the transaction information, including the sender, receiver, value, gas, gas price, and nonce. Additionally, a green icon should appear to indicate that the transaction was signed successfully.
After completing this transaction, your hacked account will have sufficient native currency to process other transactions.
You should choose the “HEX Data Tx” transaction type to add custom transactions.
To generate hex data for specific transactions, you can use specialized services or copy the hex data from your Metamask wallet during the transaction confirmation.
For example, if you have $CAKE tokens in a pool on a hacked account, you should navigate to the pool website and initiate a withdrawal transaction.
After the transaction request appears in your Metamask wallet, you should navigate to the 'HEX' section and copy the generated hex data.
⚠️ Be cautious when processing transactions to a smart contract, as some contracts may contain malicious code. Always ensure that you are interacting with a trusted service.⚠️
After generating the HEX data, you should specify the parameters in the recently added transaction. The Sender Address should be your compromised wallet, the Smart Contract Address should be the address of the staking smart contract, and the HEX Data should be the data you copied previously from Metamask. This transaction withdraws staked tokens or reward tokens from the staking smart contract to your compromised wallet.
After successfully signing the withdrawal transaction, you should specify the token transfer transaction to protect your claimed stake from hackers. To add this type of transaction, select the 'Token transfer' transaction type.
Next, you should specify the transaction details for the token transfer. The Sender should be your compromised wallet, the Receiver should be your safe wallet, the Token Address should be the address of the token being transferred, and the Amount should be the quantity of tokens to be transferred.
⚠️ If you see a message indicating that the currently connected wallet address and the 'Sender address' are different, simply open Metamask and switch to the correct wallet address.⚠️
Once you have added all transactions to the bundle and signed them, you must simulate the bundle execution to ensure that each transaction will be processed without errors. To do this, click on the 'Simulate' button located in the upper section.
Following the bundle simulation, each transaction should display a simulation result of either 'Simulation success' or ‘Simulation failed’. If a transaction fails to simulate, the simulation error message will be displayed in the transaction's 'Simulation' section.
Since the generated bundle was simulated successfully, we can now execute the transaction bundle to perform the staked token rescue actions.
To begin processing the transaction bundle, click on the Run button. The system will then display an informative pop-up message during bundle mining.
⚠️ Please note that transactions may not be mined immediately, as private miners may not cover the entire HASH rate. Typically, it takes 1-2 minutes (or even less) to mine transactions, but this can vary depending on other factors such as network overload and provider response times. That is why Wallet Rescue waits for 100 blocks before aborting transactions.⚠️
If transactions are not mined within 100 blocks, the bundle can be sent for mining again.
If transactions have not been mined yet, you can manually cancel the process of sending them to private miners by clicking on the 'Cancel' button. Please note that this process can be very quick, so double-check your transaction data before running the bundle.
After the bundle transactions are included in a block, the system will display links to the transaction explorer for each transaction.
This flow is a basic example of how our system can be used. You can perform more complex sequences to protect your funds or send private transactions
Last updated
