> For the complete documentation index, see [llms.txt](https://cvnnt.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cvnnt.gitbook.io/documentation/how-it-works/bridgeless-stateful-transfers/self-custody-channeled-btc-cross-chain-transfer/2-hop-btc-cross-chain-transfer.md).
# 2-hop BTC cross-chain transfer
2-hop flow represents a scenario in which the user wants to perform some DeFi actions with their BTC on Covenant before transferring their BTC to another network.
In this scenario Alice moves bitcoins from Bitcoin to Covenant and then from Covenant to Hyperliquid (EVM blockchain):
### Bitcoin → Covenant system → Hyperliquid
#### User flow:
|
1. Alice provides required parameters (BTC amount, her Covenant system wallet, etc.) and receives unique channeling transaction based on the data she provided.
2. Alice deposits BTC to her channel via her special transaction.
3. When the transaction is finalized on Bitcoin, Covenant system mints to Alice a Channel NFT with Alice’s Bitcoin deposit parameters.
4. Alice initiates her Channel NFT transfer to Hyperliquid via Covenant web app interface, providing her address on Hyperliquid and sending her Channel NFT to Covenant<>Hyperliquid connector module.
5. Connector module locks Channeled\_BTC and sends a transaction to the Asset transfer management module on Hyperliquid to mint Channel NFT with corresponding parameters to Alice on Hyperliquid.
6. When a transaction is finalized on Hyperliquid, Asset transfer management module mints Channel NFT to Alice on Hyperliquid.
