Skip to content

To keep going please Log in.

or

By submitting my information, I agree to the Privacy Policy and Terms of Service.

To keep going please Log in.

or

By submitting my information, I agree to the Privacy Policy and Terms of Service.

To keep going please Log in.

or

By submitting my information, I agree to the Privacy Policy and Terms of Service.

To keep going please Log in.

or

By submitting my information, I agree to the Privacy Policy and Terms of Service.

Wrapped Tokens vs Native Swaps: Where Cross-Chain Risk Comes From

Diana Paluteder

Why holding a bridged asset differs from exchanging native cryptocurrencies—and what THORChain’s design does and does not solve

Wrapped tokens and native cross-chain swaps can both help users move economic value between blockchains, but they solve different problems. A wrapped token represents an asset held or locked elsewhere. A native swap exchanges an asset on its original blockchain for another asset on its own blockchain, without leaving the user holding a wrapped representation. The distinction changes the risks that continue after a transaction is complete.

THORChain provides an example of the native-swap approach: users can exchange supported assets such as bitcoin (BTC) and ether (ETH) from self-custody wallets through its liquidity pools. That avoids the need to acquire wrapped BTC to receive native ETH, but it does not eliminate protocol security, liquidity or execution risks during the exchange.

What is a wrapped token?

A wrapped token is an asset issued on one blockchain to represent an asset from another. Wrapped bitcoin on Ethereum, for instance, is not BTC on the Bitcoin network. It is an Ethereum-based token designed to track bitcoin’s value, with its redemption and backing depending on an issuer, custodian, bridge or other specified mechanism.

In a common lock-and-mint process, original assets are deposited with a custodian or locked through a bridge mechanism while corresponding representations are issued on a destination chain. Redeeming the underlying typically requires the wrapped units to be surrendered or burned under the applicable redemption rules. The precise arrangements differ by issuer: not every wrapped token uses the same custody structure, reserve model or guarantee.

This design is useful when a user wants to deploy the economic value of BTC inside applications on Ethereum or another ecosystem. But the holder’s exposure then includes the continuing reliability of the backing arrangement, redemption process and issuing system, in addition to the market and blockchain risks of the token itself.

What is a native cross-chain swap?

A native cross-chain swap exchanges one supported blockchain asset for another without producing a wrapped token for the user to hold. For example, a user sends BTC on Bitcoin and receives ETH on Ethereum. The user ends the transaction holding native ETH rather than a tokenized claim on BTC.

Such a swap still requires an execution mechanism. Some systems use liquidity pools and validator-controlled vaults; others use atomic-swap protocols coordinating transactions between counterparties. ‘Native’ describes the assets delivered, not a promise that every system has the same security guarantees or eliminates intermediating mechanisms during settlement.

Wrapped BTC versus a native BTC-to-ETH swap

What asset does the user hold afterward?

With wrapped BTC on Ethereum, the user holds a token representing bitcoin under the relevant issuer’s backing and redemption model. After a completed native BTC-to-ETH swap, the user instead holds ETH on Ethereum. The two outcomes are not economically identical: one maintains bitcoin exposure through a representation, while the other converts that exposure into ether.

How long does the additional dependency last?

Holding wrapped BTC generally means relying on the wrapper’s continuing reserve security, redemption arrangements and operational continuity for as long as the position is held. In a completed native swap, the user no longer relies on a wrapper for the asset received. The exchange itself, however, temporarily depends on the protocol’s execution and custody mechanisms, and the received native asset remains subject to its own chain and wallet risks.

Does only wrapped BTC have depegging risk?

A wrapped token can diverge from its intended reference price if market confidence in backing or redemption deteriorates. A native ETH balance has no BTC redemption peg to break, but its market value can still move relative to BTC. Avoiding wrapper-specific depeg risk does not mean avoiding price volatility.

Where does cross-chain risk originate?

Cross-chain systems introduce trust and technical dependencies at points where one blockchain must rely on information, funds or execution coordinated elsewhere. Custodial wrappers concentrate backing assets under particular operational controls. Smart-contract bridges may rely on code, message verification, validator sets or external keys. Liquidity protocols have separate vault-management, node-security and pool-pricing risks.

The consequences of bridge failure have been significant. In an August 2022 analysis, Chainalysis estimated that attacks on cross-chain bridges accounted for 69% of the value stolen in crypto hacks during the year to that point. That was a time-specific snapshot of 2022, not an estimate of all cryptocurrency theft across all years. The Ronin and Wormhole incidents likewise illustrate how exploited bridge infrastructure can put substantial locked value at risk.

Four categories are particularly useful when comparing designs: custody and reserve risk, which concerns assets securing representations; contract or protocol risk, including bugs and flawed assumptions; validator and key-management risk, arising from compromised or colluding operators; and execution risk, including delayed settlement, pauses and poor quotes. Depeg risk is an additional concern for assets meant to maintain a redemption relationship with an underlying token.

How does THORChain facilitate native swaps?

THORChain is a decentralized cross-chain exchange with on-chain pools linking supported assets to its network asset, RUNE. In the standard BTC-to-ETH route, the trader sends native BTC to the exchange’s vault on Bitcoin, and the network uses its BTC–RUNE and RUNE–ETH pools to calculate and execute the conversion before paying out native ETH to the destination address. The participant need not hold RUNE personally for this routing.

Its validators, commonly called THORNodes, observe inbound transactions through chain-specific infrastructure. Vault funds are jointly controlled through threshold-signature systems rather than a private key held by one ordinary operator. Nodes bond RUNE as economic collateral and may face penalties for certain misbehavior. These defenses are designed to reduce particular attack incentives, but they are not guarantees against all technical or economic failures.

The exchange’s official materials list support for Bitcoin, Ethereum, XRP Ledger, BNB Smart Chain, Solana, TRON, Zcash, Dogecoin, Bitcoin Cash, Litecoin, Avalanche, Cosmos and Base, along with its own native chain. A listed integration does not mean every possible token or route always has active liquidity; supported assets and network status should be checked when making a swap.

A practical BTC-to-ETH example

First, the user requests a quote through a wallet or interface integrating THORChain and enters an Ethereum destination address. Next, the user sends native BTC to the assigned Bitcoin vault using the instructions provided. The network observes the deposit, executes the necessary pool conversions and initiates a native ETH payout to the destination wallet. Fees, confirmation requirements, network status and settlement time affect the result. A quote should be examined before funds are sent.

What risks remain in THORChain native swaps?

The most important trade-off is that wrapper redemption risk is replaced by exposure to the exchange while funds are in flight. A transaction depends on correct cross-chain observation, node cooperation, vault signing and normal operation of the connected blockchains. A pause, chain issue or protocol fault can delay a payout or cause a refund under the applicable rules.

Price impact is also relevant. The exchange uses liquidity pools, so a trade’s effective rate depends in part on its size relative to available depth. Its documentation describes slip-based fees and streaming-swap options intended to improve execution for eligible routes. Network fees on both chains also matter, and splitting an order is not automatically better when additional network costs and execution uncertainty are considered.

Because THORChain does not deliver wrapped assets to the user, a completed native swap avoids the ongoing claim on bridge-held backing. It does not confer immunity from market volatility, wallet loss, malicious interfaces, incorrect addresses or subsequent risks involving the received asset.

When is a wrapped token the better tool?

Wrapped tokens can be useful when the goal is to use one asset’s value within another ecosystem without converting it economically into a different coin. A user who wants BTC-denominated exposure in an Ethereum lending market may prefer a suitably assessed wrapped representation. That use case requires careful attention to issuer transparency, reserves, redemption rules and platform risks.

A native swap suits a different objective: converting an asset into another native asset and ending the process with that coin on its home chain. For instance, a trader rebalancing BTC into ETH may prefer a route that delivers native ETH directly. The comparison should include quoted output, slippage, chain fees, availability and security assumptions rather than treating either mechanism as universally superior.

The bottom line

Wrapped tokens and native swaps are different answers to different cross-chain needs. A wrapped token extends an asset’s usefulness into another ecosystem, while adding ongoing dependence on a backing and redemption mechanism. A native swap exchanges the user’s economic exposure for another native asset, removing that wrapper dependency after settlement but introducing protocol and execution risk during the transaction.

THORChain demonstrates how native swaps can operate through cross-chain liquidity and validator-controlled vaults. Its value proposition is not that cross-chain transactions become risk-free, but that users can receive real assets on their destination blockchains without keeping a bridged representation. Understanding the distinction helps traders compare routes more intelligently.

FAQs

Is wrapped bitcoin the same asset as native bitcoin?

No. Wrapped bitcoin is a token on another blockchain that represents BTC under a specified backing and redemption arrangement. Native BTC exists on the Bitcoin network.

Can a wrapped token lose its peg?

Yes. If confidence in redemption, collateral or custody declines, a wrapped token can trade above or below its intended reference value. The exact risk depends on its design.

Can users swap BTC for ETH without receiving wrapped tokens?

Yes. THORChain supports exchanges from native Bitcoin to native Ethereum assets through its decentralized cross-chain exchange, subject to live chain status, available pools and transaction conditions.

Do native swaps eliminate cross-chain risk?

No. They eliminate the need to keep holding a wrapped representation after the swap, but temporarily expose funds to the protocol’s vault, validator, execution and liquidity risks.

Do users need to hold RUNE to swap on THORChain?

No. The exchange internally routes supported cross-chain pool swaps through RUNE; users can send one supported asset and receive another without separately acquiring RUNE for the transaction.

Finance Digest

By subscribing you agree with Finbold T&C’s & Privacy Policy

Related guides

Home

IMPORTANT NOTICE

Finbold is a news and information website. This Site may contain sponsored content, advertisements, and third-party materials, for which Finbold expressly disclaims any liability.

RISK WARNING: Cryptocurrencies are high-risk investments and you should not expect to be protected if something goes wrong. Don’t invest unless you’re prepared to lose all the money you invest. (Click here to learn more about cryptocurrency risks.)

By accessing this Site, you acknowledge that you understand these risks and that Finbold bears no responsibility for any losses, damages, or consequences resulting from your use of the Site or reliance on its content. Click here to learn more.