Deposit Lifecycle

This is the initial state of an operation, which is created when a deposit is discovered in a block. A deposit is identified as follows:

The transfer must meet the asset's minimum amount. The supported-asset table is the minimum-amount reference for this lifecycle.

• A Bitcoin deposit is a transaction output to a Unit deposit address.
• An Ethereum deposit is an ETH transfer from an EOA or contract to a Unit deposit address. Each deposit corresponds to a trace.
• A Solana deposit is a SOL or supported SPL-token transfer to a Unit deposit address.

Once a sourceTx is discovered, the deposit operation goes through validation, which includes checks for sanctioned addresses.

A transaction has one confirmation when it is included in a block on the source blockchain. Each additional block adds a confirmation. The guardians wait for the source network's required confirmations before building the Hyperliquid transfer.

Discovery and operation creation happen before this finalization stage. The Operations API reports the current state and confirmation progress.

The guardians are constructing the Hyperliquid transaction payload to fulfill the deposit.

Additional verification steps before Guardians sign the Hyperliquid transaction.

The guardians are performing the MPC signature event for the Hyperliquid transaction.

The guardian network is submitting the destination transaction to the Hyperliquid network.

The guardians wait for the Hyperliquid destination transfer to meet the required confirmations. Follow the operation state to determine when finalization is complete.

The sweep of the source transaction has been performed and is finalized on the source network. The operation's state is officially "done" - this state is terminal.