Where Is My Bitcoin After I Send It to TeleSwap?
What happens to my Bitcoin when I use TeleSwap? It stays in a collateralized Locker while you receive teleBTC, which you can burn to request a BTC payout.
The Chain Today Desk4 min read

When you use TeleSwap, your BTC goes to a collateralized Locker, and you receive teleBTC after the deposit is verified on-chain. The TeleSwap background adds the protocol context: TeleportDAO’s relayers and a Merkle proof connect a Bitcoin deposit to the EVM contract that mints teleBTC. TeleSwap’s bridge leaves you holding a redeemable token, not BTC under your own keys.
How does TeleSwap verify a Bitcoin deposit?
The process starts when you send BTC to a Locker’s Bitcoin address with an OP_RETURN request attached to the transaction. That request carries details such as the destination chain and recipient, so the bridge can associate the deposit with where the resulting asset should go.
After the Bitcoin transaction receives confirmations, relayers submit Bitcoin block headers to the EVM chain. A contract checks a Merkle proof against those relayed headers to verify that the deposit is included in a Bitcoin block. The proof is like a compact receipt: the contract uses it to check the transaction’s place in the block without needing the full block data.
Once verification succeeds, teleBTC is minted to the named recipient, less the fees specified in the request. A request can also be structured for a mint-and-swap outcome. The key point is that minting follows proof verification; sending BTC alone does not create the token.
What do the moving parts do?
Each part has a separate job in moving value from Bitcoin to the destination chain:
- Locker: Holds the deposited BTC at its Bitcoin address and provides collateral for the bridge’s obligations.
- OP_RETURN request: Carries request data, including the destination chain and recipient.
- Relayers: Submit Bitcoin block headers to the EVM chain so the contract can check the deposit.
- Merkle proof: Shows that the deposit transaction is included in a block represented by the relayed headers.
- teleBTC: The token minted to the recipient after verification; it represents a claim redeemable for BTC.
The BTC does not move into your wallet when teleBTC arrives. It remains at the Locker address, backed by collateral, while teleBTC is what you can hold and later use to request redemption.
Does redeeming teleBTC return the same BTC?
No. Burning teleBTC triggers a Locker to pay BTC to the Bitcoin address specified for the payout, but the payout need not come from the Locker that received your deposit.
That is because teleBTC is fungible across Lockers: units of the token are interchangeable rather than tagged to particular deposited coins. If you deposited to one Locker, then later burn teleBTC for a payout, another Locker may supply the BTC. Your original coins are not traced through the bridge and sent back to you.
For you, the practical distinction is between a specific set of BTC and a redeemable token. You give up control of the deposited BTC to the Locker arrangement and hold teleBTC under your own wallet keys. The redemption mechanism connects the token to a BTC payout; it does not preserve the identity of your deposit’s individual coins.
What changes if the recipient is on another chain?
The request’s destination chain and recipient determine where the verified deposit’s result is directed; they do not change the basic verification step. Relayers still submit Bitcoin headers, the contract still checks the inclusion proof, and the Locker still holds the deposited BTC.
For instance, if the request names a different recipient, teleBTC is minted to that recipient rather than to the wallet that initiated the deposit. The part that remains the same is the backing and redemption model: BTC stays with a Locker, and teleBTC can be burned to trigger a BTC payout.
Before sending, read the destination chain and recipient encoded in the request carefully. That quick check helps avoid expecting teleBTC in the initiating wallet when the request names a different recipient.