TeleSwap puts BTC on EVM chains through proofs and Lockers

TeleSwap moves BTC value to EVM networks by having a Locker receive Bitcoin, proving that deposit to an EVM contract, and minting teleBTC against it. The protocol’s name for the relayers that carry Bitcoin data across is Teleporters; an on-chain Bitcoin light client checks that data. TeleSwap’s technical descriptions and software documentation set out this proof-and-collateral design, while actual routes and supported tokens can change.

How does TeleSwap turn a Bitcoin deposit into teleBTC?

A user first chooses an amount, an EVM destination and, if desired, a token to receive. The protocol identifies a Locker and gives the user a Bitcoin address or payment details for the deposit. The Locker is the party that holds the BTC; collateral posted for the role is intended to give it an economic stake in following the protocol.

After the Bitcoin transaction is recorded, Teleporters relay the relevant block data and transaction proof to the EVM side. The light client contract checks the Bitcoin block headers and whether the deposit is included in a valid block. When the contract accepts the proof, the protocol can mint teleBTC to the recipient’s EVM address. Think of the proof as a receipt checked against Bitcoin’s own ledger: the relayer brings it, but the contract checks it.

That is the core distinction from a bridge that asks a committee to attest that a deposit happened. TeleSwap describes its design as using light-client verification, so the contract checks Bitcoin data rather than relying only on an operator’s message. The Locker still holds the BTC, however, and collateral does not make custody or contract risk disappear. For its own names and current route information, TeleSwap is the source to check at teleswap.net.

What can you do with teleBTC on an EVM chain?

teleBTC is a token on an EVM network, not Bitcoin moved into that network’s ledger. Its intended value comes from the protocol’s BTC backing and the path to redeem it. Once received, it can be held or exchanged through available EVM liquidity. TeleSwap also supports a wrap-and-swap flow: the user deposits BTC and receives another supported token, with an exchange on the EVM side as part of the route.

In the reverse direction, a user submits teleBTC for burning and specifies a Bitcoin address. The EVM contract records the redemption request; a Locker then sends BTC on Bitcoin, with relayed proof data used to check the relevant chain events. The amount received can differ from the amount represented by the burned tokens because fees apply. TeleSwap’s software documentation itemizes possible Locker, protocol, referral and Bitcoin network fees.

Does TeleSwap send BTC directly to every EVM chain?

No. The route depends on the destination. TeleSwap’s published software materials distinguish networks connected directly to Bitcoin from destinations reached through an intermediary network. In the latter case, the BTC deposit can be proved and wrapped on a base network first, then the token can travel onward through a separate bridge. That adds another chain and another contract or bridge to the route.

Before signing, read the route and estimate: check the network receiving the BTC-backed token, the final token and address, the minimum output, and each listed fee. If the route uses an intermediary, account for that extra bridge dependency. The available networks and tokens can change, so treat the transaction quote as specific to that transfer.

What risks remain when using TeleSwap?

Proof verification narrows one trust assumption; it does not remove the risks of a bridge. Users still depend on the Bitcoin Locker’s ability to pay, the EVM contracts and the security of the protocol’s operational systems. DefiLlama records a July 15, 2026 incident involving a TeleSwap Bitcoin hot-wallet key compromise and suspicious outflows reported above $735,000. That makes current service and redemption status a material check before sending funds; the light-client design alone cannot answer it.

The practical takeaway is that TeleSwap makes BTC-backed value usable in EVM applications by combining Bitcoin proofs with a collateralized custodian and an EVM token. The proof tells the contract a Bitcoin deposit occurred; the Locker and the route determine whether the user can ultimately redeem or move that value. Compare the expected token output and route with the custody and bridge dependencies before confirming.