Your Trezor can now swap native Bitcoin with no KYC. That closes a real gap.

On June 3, 2026 we shipped native Trezor support to LeoDex. The interesting part isn't the integration — it's that Bitcoin, the asset most hardware-wallet owners actually hold, is the one Trezor's own swap can't move cross-chain without a KYC exchange. Here's the gap, what 'native' buys you, and the honest limits.

On June 3, 2026, we shipped native Trezor support to LeoDex. You can now connect a Trezor and swap native Bitcoin — real BTC, not a wrapped IOU — across more than sixty chains, with no account, no KYC, and no custodian, signing every transaction on the device itself.

That reads like a routine wallet integration. It isn't, and the reason is specific. The single most-held asset on hardware wallets is Bitcoin. And Bitcoin is precisely the asset that Trezor's own built-in swap cannot move cross-chain without routing you through a centralized exchange that can ask for your ID.⁰¹

§ 01 What a hardware wallet actually protects

Strip away the marketing and a hardware wallet does one narrow, important thing. It keeps your private keys on a device that never exposes them to your computer, and it makes you approve each transaction on a screen the malware on that computer cannot reach. The keys are generated offline. They sign offline. The only thing that leaves the device is a signature.

That is the whole trust model, and it is a good one. It is not a perfect one. In 2020, Kraken Security Labs showed that a Trezor One or Model T, in an attacker's physical possession, could have its seed extracted by glitching the chip's voltage — a fifteen-minute attack that a passphrase (a thirteenth word only you know) defeats.⁰² So: set a passphrase, and the threat model that remains is the one that matters for swapping — remote compromise of the machine you are sitting at. Against that, the device is exactly as strong as your habit of reading its screen before you press confirm.

A swap is just a transaction. If your keys can sign a send, they can sign a swap. The question was never whether a Trezor could do this. It was whether anyone gave you a way to do it without handing the rest of the process to someone who would.

§ 02 The gap in Trezor's own swap

Trezor Suite — the desktop app most Trezor owners use — has a Swap tab. It is convenient, and for the right asset it is fine. The catch is the asset. Suite's decentralized swap route works for EVM assets only — Ethereum, and the tokens (ERC-20s) and chains built to be Ethereum-compatible. Bitcoin runs on its own, non-EVM network, so it falls outside that route and gets handed to centralized-exchange partners instead.⁰¹

Those partners can require identity verification above a threshold, and in some cases will ask for ID even to process the refund on a swap that failed.⁰³ Trezor is upfront about this in its own documentation. The "just use Suite" advice that gets handed to new Trezor owners is reasonable on its face. It is also wrong for the asset most of them actually hold. There is a categorical difference between "swap your ERC-20s in one app" and "move your Bitcoin across chains while keeping custody and privacy." Suite does the first well. It cannot do the second at all.

This is not a knock on Trezor the device. The device is excellent. It is a gap in one feature, and gaps get filled.

§ 03 What "native" buys you

The word doing the work in the lede is native. There are two ways to "swap Bitcoin" that aren't really swapping Bitcoin: you can wrap it into a token on another chain and trade the token, or you can hand it to an exchange and trust them to send you something else. Both put a layer of someone-else's-promise between you and your coins.

Native cross-chain swaps remove that layer. Protocols like THORChain and MAYAChain hold real liquidity on both chains and settle in the real assets — you send real BTC and you receive real ETH. The instruction telling the protocol what to do rides along inside the very transaction your device signs: a short "memo" attached to the send.⁰⁴ Chainflip does the same with its own just-in-time liquidity, and bills its no-KYC, address-to-address design as a hardware-wallet-friendly flow precisely because it asks the user to do nothing exotic — just sign a standard transaction.⁰⁵ NEAR Intents adds a solver network whose routes can be the cheapest available — a protocol fee as low as 0.01% on some pairs.

LeoDex does not pick one of these and hope. It aggregates them, streams their quotes live, and shows you the best net output for the specific trade in front of you. Your Trezor signs whichever one wins.

§ 04 The honest limits

Now the part the marketing usually skips.

On LeoDex today, a Trezor connects for Bitcoin and seven EVM chains — Ethereum, Arbitrum, Base, BNB Chain, Optimism, Avalanche, and Polygon. That is the source side. From any of those you can swap into sixty-plus destination chains, but you connect from those eight.⁰⁶ If you want to spend assets that live on a Solana or an XRP account on your Trezor, that path is not wired yet; you can still receive Solana or XRP as the output of a swap from your Bitcoin or your ETH.

For Bitcoin, use a Native SegWit account — the addresses that start with bc1q. Nested SegWit works too. Taproot and legacy accounts are not enabled for Trezor signing on LeoDex yet, so a Taproot wallet won't sign, and the honest move is to tell you that here rather than let you find out at the confirm screen.

And we do not keep a hardware wallet connected between visits. You reconnect each session. That is deliberate — a hot persistent handle to a cold device is a contradiction — but it is a small recurring friction, and you should know about it going in.

None of this is hidden behind a happy path. The model only works if you read the device. That is the deal with self-custody, and it does not change because the transaction happens to be a swap.

§ 05 Why this matters now

The case for swapping from your own device with no account is not ideological. It is about optionality, and the last few years have made the cost of not having it concrete.

People keep funds on centralized exchanges for convenience, and periodically discover that convenience and control are different things — when withdrawals pause, when an account is frozen pending a review that has no deadline, when the asset you "own" turns out to be an entry in someone's database. I wrote about one such freeze in these notes already.⁰⁷ The lesson generalizes: an asset you cannot move without permission is an asset you only conditionally own.

Regulation is tightening around the fiat edges — the travel rule (which forces regulated services to attach your identity to transfers) and MiCA (the EU's crypto rulebook) push identity collection onto the on-ramps and off-ramps, the places you move between cash and crypto.⁰⁸ Crypto-to-crypto, on-chain, in self-custody, remains the part of this you can still do without asking. A hardware wallet plus a non-custodial cross-chain aggregator is simply the most durable version of that: the keys are yours, the settlement is on-chain, and no intermediary sits between your intent and the trade.

That is what shipped on June 3. Not a feature. A way to keep moving when the permissioned paths close.

Survive > maximise. Hold your own keys. Swap without asking permission.