Withdrawal Lifecycle
The lifecycle of a withdrawal operation
SourceTxDiscovered
This is the initial state of an operation, which is created when a deposit is discovered in a Hyperliquid block. A withdrawal is identified as a Hyperliquid transfer - greater than the minimum for the source-chain - to a Unit withdrawal address.
Once a sourceTx is discovered, the deposit operation goes through validation, which includes checks for sanctioned addresses.
ReadyForWithdrawQueue
In accordance with throughput limitations of supported networks, destination transactions are staged on a withdraw queue to be triggered in batches. Like sweeps, withdraw queue transactions are triggered every ~3 Bitcoin blocks for bitcoin withdrawals, and ~21 Ethereum slots for ethereum withdrawals.
The operation's positionInWithdrawQueue may be used to inform the expected completion of this state.
QueuedForWithdraw
The operation has been included in a withdraw queue batch, the tx-hash of which corresponds to the tx-hash returned by the withdraw queue endpoint and can be inspected on any explorer for the destination network.
ERC20 Withdrawals
SourceTxDiscovered
This is the initial state of an operation, which is created when a deposit is discovered in a Hyperliquid block. A withdrawal is identified as a Hyperliquid transfer - greater than the minimum for the source-chain - to a Unit withdrawal address.
Once a sourceTx is discovered, the deposit operation goes through validation, which includes checks for sanctioned addresses.
ENA: Please note, for ENA withdrawals there is a max withdrawal size of $20,000,000. Any deposits larger than this will not be processed.
ReadyForWithdrawQueue
The guardians are preparing to submit the Layerzero transaction releasing your tokens on Ethereum.
Done
The Layerzero withdrawal has been initiated. You may track the status of this deposit via the Layerzero Scan explorer with your operation's DestinationTxHash.
Last updated