Start typing to search this publication.
Gnosis Bridge
Open menu

Subscribe to Gnosis Bridge

Get new posts delivered straight to your inbox.

How to Use TeleSwap to Bridge BTC to an EVM Chain and Back

Gnosis Bridge
3 min read

TeleSwap lets you bridge BTC by requesting a route in its app, sending the exact Bitcoin amount to the assigned Locker with the request data in an OP_RETURN output, and waiting for confirmations before receiving teleBTC or your chosen token. The TeleSwap app provides the route request and transaction data that connect your Bitcoin deposit to your EVM recipient. The bridge verifies the Bitcoin transaction on-chain before minting.

Prepare and Send BTC to an EVM Chain

A BTC transfer through the bridge starts with a Bitcoin wallet, an address on your destination EVM chain, and enough BTC for the deposit plus the Bitcoin network fee. Open the official app from your bookmark. Choose the destination network and target token, then enter the amount and receiving address. Polygon and BNB Smart Chain are distinct networks even if your wallet displays the same EVM address on both; use the network selected for your route.

  • Route: the destination network, token and receiving address you choose.

  • Locker: the collateralized participant assigned to receive the BTC.

  • OP_RETURN: a Bitcoin output carrying the request data.

  • Result: teleBTC, or the token selected for the route, on the destination chain.

These parts must match one request. The Locker receives the deposit, while OP_RETURN identifies how the bridge should process it. Review the quoted output amount, fees and minimum deposit before sending. The amount you send must meet that minimum and match the amount generated for the request.

  1. Select the route and target token, then enter your receiving EVM address.

  2. Enter the BTC amount and review the quote, including the expected output and minimum.

  3. Sign or send the generated Bitcoin transaction with the assigned Locker output and OP_RETURN data intact.

  4. Wait for the required Bitcoin confirmations, then look for the mint transaction on the destination chain explorer.

  5. If the transaction is visible but teleBTC is hidden in your wallet, import the verified teleBTC contract for that chain.

Preserve the generated transaction details when using an external Bitcoin wallet. Copying only the Locker address is insufficient: the OP_RETURN output carries the route data. A wallet that drops or rewrites that output can leave a valid Bitcoin payment that the bridge cannot match to your request. Editing the Locker output or deposit amount can break the match too. Inspect the outputs before signing; if your wallet cannot keep them as generated, resolve that before broadcasting.

The confirmed Bitcoin deposit is the dependency for minting. The bridge needs the specified amount, Locker output and request data in a transaction with the required confirmations. You can recognize readiness by finding that transaction on a Bitcoin explorer and checking its confirmations against the route requirement. Completion is the mint transaction on the destination chain explorer, even if your wallet has yet to display the token.

Verify the Result, Fix Failures, and Return to Bitcoin

A TeleSwap transfer is complete when the destination-chain transaction shows the minted asset at your receiving address. If Bitcoin has too few confirmations, wait and check whether the network fee you chose is delaying confirmation. A deposit below the quoted minimum or one with changed outputs may fail to satisfy the request; more confirmations will not repair incorrect transaction data.

For a return transfer, use the bridge’s Bitcoin-bound route to burn teleBTC and provide the BTC receiving address. The burn removes the bridged tokens from circulation; a Locker then pays BTC to that address. Verify the burn on the EVM chain and the payout on a Bitcoin explorer. Keep the transaction identifiers for both directions so you can distinguish a pending confirmation from a missing transfer.

Subscribe to Gnosis Bridge