A deposit channel is a blockchain address tied to a specific transfer instruction, including where the swapped asset should go. It works only if the channel is opened for the right source asset and the destination chain and address are correct.
A deposit channel binds a transfer to its destination
When a channel is created, the swap request records the input asset, output asset, destination chain and destination address. The channel then gives you an address to fund on the source chain. The address is the link between the funds you send and the instruction the network will carry out.
On Chainflip, the request is registered on its State Chain, while the deposit itself happens on the source blockchain. The protocol derives a deposit address associated with that request; validators watch for funds arriving there and record a confirmed deposit. A regular transfer to a vault address without a registered swap instruction may not be recognised as a swap.
A channel address is not a general-purpose wallet or a reusable account for any destination. Its purpose is to identify a particular swap request. Even if an address looks familiar, use the fresh address provided for the transfer you are making.
The network connects the deposit to the payout
After the source-chain transaction is confirmed, validators witness the deposit and the protocol processes the swap against available liquidity. The resulting asset is then sent to the destination address recorded in the request. You do not need to make a second transfer to connect the source funds to the destination; that relationship is part of the registered instruction.
For example, suppose you want to exchange ETH on Ethereum for SOL on Solana and receive the SOL in your own Solana wallet. The request must specify ETH as the source asset, SOL as the output asset, Solana as the destination chain, and your Solana address as the destination. You send ETH to the channel address on Ethereum; after confirmation and processing, the output is sent to the recorded Solana address.
Chainflip’s official site is a service for carrying out this kind of native cross-chain swap. Before sending, check that the source asset and network match the wallet you are paying from, and that the destination address belongs to the output network.
Timing and costs depend on both chains
The deposit must first satisfy the source chain’s confirmation rules, so timing varies: Bitcoin transactions, for example, generally take longer to confirm than Ethereum transactions. The destination transfer also needs to be broadcast and confirmed on its own network. A quote or estimate can change with liquidity, network conditions and the time between requesting the channel and funding it.
Budget for the source-chain transaction fee, swap charges and the cost of sending the output on the destination chain. As a planning example, published Chainflip protocol components include a 0.10% liquidity fee and a 0.10% network fee; the actual total can also depend on network costs and any broker charge. Check the terms shown for the service you use before committing funds.
Use a fresh channel and verify both ends
Deposit channels are temporary. Chainflip’s documentation says they close after 24 hours, and a late deposit may no longer be recognised, so open a new channel for each swap and send promptly. If a transfer is not detected, keep its transaction ID and check that it was sent on the correct source network before taking further action.
The destination address is the detail that decides where the output goes, so copy it from the wallet or app where you intend to receive funds and verify the network as well as the address. For the protocol’s role in this process, see the Chainflip protocol. My practical tip: compare the destination address’s first and last characters after pasting it, then confirm the selected network before you send.