Bot Usage
This page explains key commands, the standard operating path, and how to read outputs.
Commands
| Command | Purpose |
|---|---|
/start |
Open main menu |
/detect |
Start address detection |
/recovery |
Start asset recovery |
Standard Flow
- Run
/startto initialize session - Run
/detectto inspect asset structure - Run
/recoveryand provide required inputs - Confirm plan and fee breakdown
- Wait for the guided recovery process to finish and keep the transaction hashes for later checking if needed
Interaction Notes
- Detection is read-only and does not require private key.
- Recovery accepts private key or mnemonic.
- No destination address input is required; funds return to the same source address on Arbitrum.
- For lock/wait states, bot provides rerun timing guidance.
Output Reading
Focus on these fields after execution:
Recovered AmountActual FeesService FeeWithdrawal Fees- Transaction hashes if you want to verify the transfers yourself
Arrival to Arbitrum is asynchronous after withdrawal submission and may take several to more than ten minutes depending on Hyperliquid processing.
Common Mistakes
- Skipping detection before recovery, which can make you miss locked or waiting assets
- Treating estimated values as final actuals, even though prices may change slightly during execution
- Not checking whether the source address can receive normally on Arbitrum, which may cause confusion when waiting for arrival