TeleSwap bridges BTC by having you send it to a collateralized Locker with request data in the Bitcoin transaction, verifying the deposit on-chain, then minting teleBTC or swapping it into a token at your destination address.
- Locker: Receives the BTC and holds collateral against its obligation to pay it back.
- Bitcoin relay: Supplies block headers so a contract can verify the deposit.
- Bridge contracts: Mint teleBTC after verification and, if requested, route it through a DEX.
From Bitcoin Deposit to Destination Token
A TeleSwap wrap begins when you send BTC to a Locker address and include your request in that same Bitcoin transaction. The request tells the bridge where to deliver the result and whether you want teleBTC or a swapped token. Native BTC stays with the Locker; the destination receives a token representing the completed bridge request.
Decide which token you want at your destination address before making the deposit. Use TeleSwap for the TeleSwap bridge or swap that matches that choice.
Relayers then submit Bitcoin block headers to a relay contract. The relay stores those headers, while a Merkle inclusion proof shows that your deposit transaction belongs to a particular Bitcoin block. TeleportDAO’s Bitcoin-EVM bridge contracts check that proof against the relayed headers using simplified payment verification, or SPV. The contract can establish that the deposit occurred without accepting a trusted signer’s word for it.
Once the proof and required Bitcoin confirmations pass verification, the contracts mint teleBTC against the deposited BTC at a 1:1 unit ratio. If your request calls for another token, the minted teleBTC goes through a decentralized exchange, or DEX, before the output reaches your address. The 1:1 ratio describes the wrap itself; a swapped output also depends on the trade price and applicable costs.
What Sets the Wait and the Amount You Receive
The TeleSwap wait is governed first by the Bitcoin confirmation depth required by the relay. A confirmation comes as Bitcoin blocks build on the block containing your deposit. Relayers must supply the relevant headers, and the proof must pass before minting can proceed. Contract execution on the destination chain comes afterward and can add its own time.
Say your deposit enters a Bitcoin block while the destination chain is processing transactions quickly. Even if that chain is Ethereum or Polygon, its speed cannot replace the later Bitcoin blocks the relay requires. A higher required confirmation depth means more Bitcoin blocks must arrive before the deposit qualifies. That is why a transaction can be visible in your Bitcoin wallet yet still be waiting for bridge verification.
The costs pay for different parts of that path. A Bitcoin miner fee helps get the deposit included in a block; it does not waive the required confirmation depth. Any quoted Locker or protocol charge belongs to the bridge service, while destination gas pays for contract execution. If you request a swap, DEX pricing and slippage also affect the final token amount. Compare the net output with the token you actually need, rather than treating 1:1 minting as a promise about what a swap will deliver.
Unwrapping runs the economic obligation in reverse: teleBTC is burned, and the Locker must send native BTC to the specified Bitcoin address. Lockers post collateral that can be slashed if they fail to meet that obligation. Deposit verification establishes that BTC entered the bridge; collateral backs the Locker’s duty to release it on the way out.
Choose between teleBTC and a swapped token by the asset you need at the destination, then judge the route by its confirmation requirement and net output.