TeleSwap BTC to teleBTC transfer: follow 0.1 BTC to Polygon
A TeleSwap BTC to teleBTC transfer sends 0.1 BTC to a Locker; Bitcoin confirmations and a Merkle proof trigger the Polygon mint, minus fees.
Crypto Daybook Newsroom4 min read
Send 0.1 BTC to the assigned Locker address with the Polygon request in OP_RETURN; TeleSwap’s mint depends on Bitcoin proving that deposit first. In this illustrative case, the app builds the request, Bitcoin headers are relayed until the deposit reaches the required confirmation depth, and a Merkle proof lets a Polygon contract verify it and mint teleBTC to the named recipient. The result is ready when that mint appears on Polygon; the amount is 0.1 BTC minus protocol and Locker fees, with the Bitcoin miner fee paid on top by the sender.
Bitcoin’s deposit and request set the route
The app’s transaction ties the BTC deposit to its Polygon destination. Say you want to use the wrapped BTC in a Polygon DeFi position: the request sends 0.1 BTC to a Locker address and puts the Polygon recipient and request data in OP_RETURN. TeleSwap’s flow depends on that on-chain data so the later proof can connect this deposit to the intended mint.
The bridge verifies that Bitcoin deposit before minting on Polygon. TeleSwap routes the wrap from a Bitcoin deposit into teleBTC on the destination chain. TeleportDAO documentation describes the relay, Locker and minting flow; the Bitcoin whitepaper’s section on simplified payment verification explains why a block header and Merkle proof can show that a transaction belongs to a block.
Bitcoin confirmations, not Polygon speed, set the wait
The mint can proceed after relayed Bitcoin headers cover the deposit to the required confirmation depth. Once that point is reached, anyone can submit the Merkle proof. The Polygon contract checks the proof against the relayed header and verifies the request before minting teleBTC to the recipient.
That makes the key wait the time for Bitcoin confirmations to reach the relay, which follows Bitcoin block intervals. Polygon’s speed matters for the contract transaction, but it cannot make the Bitcoin deposit confirm sooner. The reader can treat the mint as ready when the proof is accepted and the teleBTC appears at the recipient address.
The model removes an off-chain signer’s approval from the mint: a contract checks Bitcoin evidence on-chain against a Bitcoin light client. But the BTC sits with a Locker. Lockers post collateral on the destination chain and can be slashed for misbehaviour; that collateral addresses a Locker default, while the user’s BTC is still in Locker custody during the bridge flow.
Fees and custody decide whether this transfer is worth it
The teleBTC received equals 0.1 BTC less the protocol and Locker fees shown in the app when the request is made. The sender also pays the Bitcoin miner fee on top. For a small or one-off transfer, compare those costs with the planned Polygon use, including the cost of bridging back.
At the protocol level, the mint tracks the deposited BTC unit for unit before fees, but that does not mean the BTC remains in your wallet: it is held by the Locker, with collateral providing a separate backstop. Unwrapping reverses the route by burning teleBTC and paying out BTC.
Related: how long does teleBTC take to arrive on Polygon?
It arrives after the Bitcoin transaction has enough confirmations in the relayed headers, a proof is submitted and accepted, and the Polygon mint completes. The Bitcoin confirmation stage follows Bitcoin block intervals, so Polygon transaction speed alone does not determine the wait.
Related: is teleBTC backed 1:1 by BTC?
The mint is based on the verified BTC deposit, minus protocol and Locker fees. Lockers hold the BTC and post collateral that can be slashed for misbehaviour; weigh that custody and backstop model against the planned DeFi use. Bridge when the Polygon use justifies the fees and custody exposure.