What is a native swap? Cross-chain trading without the bridges

A native swap is a crypto trade that moves value directly between two blockchains — you send the asset one chain actually uses and receive the asset the other chain actually uses. No bridge, no wrapped stand-in token, no IOU. The trade settles as the real asset, on its real chain.

If that sounds like the way cross-chain trading should always have worked — agreed. The detour crypto took to get here cost users rather a lot of money, and it's worth understanding why before you move anything between chains.

The problem native swaps solve (bridges, and what kept going wrong)#

Blockchains don't speak to each other. Bitcoin lives on Bitcoin, SOL lives on Solana, and neither network has any idea the other exists. For years, the standard workaround was a bridge: lock your asset in a vault on chain A, and receive a "wrapped" copy of it on chain B. Wrapped Bitcoin on Ethereum, for example, is not Bitcoin — it's a token that represents a claim on Bitcoin held somewhere else.

That word "somewhere" is where the trouble started. A wrapped token is only as good as the vault backing it, and the vaults turned out to be the single most attacked infrastructure in crypto. Chainalysis attributed more than $2 billion of stolen funds to cross-chain bridge exploits in 2022 alone — including the Ronin bridge (~$625 million) and Wormhole (~$325 million). A wrapped token is a claim on a vault, and some of those vaults were guarded with the cryptographic equivalent of a beaded curtain.

When a bridge fails, the wrapped tokens it issued don't gracefully unwind. They simply stop being redeemable — which is a polite way of saying they stop being worth anything.

How a native swap actually works#

A native swap removes the vault-and-IOU construction entirely. The venue executing the swap maintains liquidity on both chains:

1. You send the native asset on the source chain — say, real BTC on the Bitcoin network.
2. The venue prices the trade and sources the destination asset from its liquidity on the destination chain.
3. You receive the native asset on the destination chain — real SOL on Solana, not a wrapped representation of something else.

Nothing gets locked, minted, wrapped, or unwrapped. Settlement speed is governed by the two chains' own confirmation times — typically minutes, not the multi-step ordeal bridges require. And because the asset you end up holding is the chain's own, there is no third-party vault whose solvency you're silently depending on next year.

Native swap vs. bridge vs. wrapped token — the 60-second version#

Where native swaps happen: DeFi protocols and regulated platforms#

Native swaps grew up in DeFi. Protocols like THORChain pioneered swapping native BTC for native ETH without wrapped tokens — decentralised, non-custodial, and entirely self-service. That model puts you in full control, and full control means full responsibility: wallet operations, address formats on every chain, and no support desk. (Our guide on wallets versus exchanges covers that trade-off honestly.)

The same mechanics now exist on regulated venues. Penning's Native Swap executes cross-chain swaps on 30+ networks and settles in the destination asset — with the platform handling the multi-chain plumbing, and with the protections that come with a MiCA-licensed counterparty: direct delivery to your own wallet and supervision by the Danish FSA. Which model fits you depends on whether you want to run your own cross-chain operations or have a regulated platform run them for you.

What native swaps don't fix#

A native swap removes wrapped-token and bridge-custody risk. It does not repeal the rest of reality:

• Market risk stays. The assets on both sides remain volatile; a clean settlement of a falling asset is still a falling asset.
• Liquidity matters. Thin pairs mean wider pricing, on any venue, decentralised or regulated.
• Chains can be slow. Settlement inherits both networks' confirmation times and congestion.
• Compliance applies. On a regulated platform, transfers and swaps are subject to AML screening — that's a feature of the licence, not a bug.

The MiCA angle: why "native" matters more in the EU#

Under MiCA, a licensed platform that holds client assets must keep them segregated — and ownership is cleanest when the asset is the chain's own. A wrapped token introduces a second issuer whose solvency and authorisation status sit outside your platform's control. Native settlement keeps the chain of ownership short: your asset, on its chain, in your own wallet — verifiable against a supervised licence rather than a protocol's multisig.

That is the quiet, unglamorous reason native swaps fit the regulated era: fewer intermediaries to trust is good engineering and good compliance.

One practical note for Danish readers: a crypto-to-crypto swap is a disposal, and disposals can be taxable. Penning documents every swap with a SKAT-ready export — the paperwork side of cross-chain trading is handled, whichever chains you cross.