AMM / DEX
TeleSwap turns a bridge into a swap by routing TeleBTC through Automated Market Maker (AMM) DEXs on the destination chain — all inside a single transaction, so there's no intermediate "bridge then manually swap" step for the user.
Two-step, one transaction
BTC → target token (ERC-20, Jetton, or SPL token)
1. Mint TeleBTC (after the bridge verifies the Bitcoin tx)
2. Swap TeleBTC → target token via the AMM DEX
Target token → BTC
1. Swap target token → TeleBTC via the AMM DEX
2. Burn (unwrap) TeleBTC → native BTC
Routing
TeleSwap routes swaps through the established AMM on each destination chain — for example:
| Chain | AMM used |
|---|---|
| Polygon | Uniswap |
| BNB | PancakeSwap |
| TON | DeDust |
| Solana | Jupiter |
Routing minimizes slippage and fees. The SDK's estimate methods
return the chosen internalExchange path and, where a cross-chain hop is involved, the
internalBridge path.
Reaching cross-chain networks
TeleBTC and the AMMs live on the chains directly connected to Bitcoin (Polygon, BNB, TON).
To deliver tokens on a cross-chain network (e.g. Ethereum, Optimism, Arbitrum, Base,
Unichain), TeleSwap performs the swap on the connected chain and then bridges the result to
the destination chain via Across — and the same path in reverse
on the way back to Bitcoin. This hop is what the SDK reports as the internalBridge path.
Slippage protection
Swaps carry a minimum-output amount; if the AMM can't meet it, the swap doesn't go through — see Swap Failures & Refunds.