Is Bridging Crypto Taxable in the UK? HMRC Facts Test

You bridged ETH from mainnet to Arbitrum. Or moved USDC across to Optimism. The tokens left your wallet on one chain and appeared on another. Your crypto tax tool saw tokens leave and called it a disposal. Now you're looking at a phantom capital gain on a transaction where nothing was sold.

A bridge should not be classified from the contract label alone. HMRC CRYPTO22110 says cross-ledger treatment depends on the facts. A same-owner, same-asset route can carry basis; a route that exchanges tokens or changes the rights held can create a disposal.

This guide covers the HMRC position on cross-chain bridges, which bridges ChainTax supports, where automated classification can go wrong, and how gas fees on bridges should be treated.

When a bridge can carry basis rather than create a disposal

A disposal for Capital Gains Tax occurs when you sell, exchange, or gift a cryptoasset (HMRC CRYPTO22100). The critical question is: did beneficial ownership of the asset change?

For a supported bridge route, check that the same beneficial owner controls both sides, the economic asset and rights are preserved, and the source and destination legs reconcile. Those facts support basis-carry treatment. Different-token output, altered rights, or an unmatched destination leg changes the analysis.

ChainTax therefore uses a disclosed basis-carry treatment only for supported bridge patterns whose decoded evidence preserves the asset and owner. It does not treat the word "bridge" as a tax rule.

How cost basis works under basis-carry treatment

If the facts support basis carry, bridging 5 ETH from Ethereum to Optimism does not reset its cost. If those 5 ETH originally cost £8,000, ChainTax carries that £8,000 to the supported destination holding.

This matters because if your tax tool treats bridging as a disposal, it will:

1. Record a disposal at market value on the bridge date, generating a phantom gain or loss
2. Reacquire the tokens on the destination chain at the bridge-date market value, resetting the cost basis
3. Corrupt your Section 104 pool, so every subsequent disposal on the destination chain will use the wrong cost basis

How ChainTax treats direct ETH and WETH wrapping

A closely related operation is wrapping ETH to WETH (Wrapped Ether) or unwrapping WETH back to ETH. Many DeFi protocols require WETH rather than native ETH, so users wrap and unwrap frequently.

WETH is redeemable 1:1 for ETH. For a direct decoded wrap where beneficial ownership and economic exposure remain with the same person, ChainTax applies the CRYPTO22100 beneficial-ownership principle and carries basis.

ChainTax classifies both ETH→WETH wraps and WETH→ETH unwraps as Transfer with cost basis preserved when both sides are verified. That product treatment should not be applied automatically to receipt or yield-bearing wrappers with different rights.

Which bridges does ChainTax support?

ChainTax's classification engine recognises the following bridge protocols. For a verified same-owner, same-asset route it appliesTransfer basis-carry treatment. Different-token or incomplete flows require separate review:

* The ETH2 Beacon Chain deposit is a consensus-layer staking deposit, not a cross-chain bridge. HMRC CRYPTO22110 gives a one-way Beacon transfer as a section 43 example where the original cost is attributed to the destination asset. ChainTax represents that as basis carry; validator returns are analysed separately.

Bridge detection runs early in ChainTax's classification pipeline, before protocol-specific handlers. It recognises supported bridge intent early while rejecting different-token output; incomplete cross-chain evidence should still be reviewed.

Want to see how a specific bridge transaction is classified? Paste any transaction hash into the free transaction explainer and see the full breakdown: chain, protocol, classification, and reasoning.

Why bridge classification can go wrong

The root problem is architectural. A transaction-level classifier works from transaction-level data: tokens left wallet A, tokens arrived in wallet B. They don't understand the intent behind the transaction.

Here's what they typically see when you bridge ETH from Ethereum to Arbitrum:

1. Source chain: ETH leaves your wallet and goes to the Arbitrum bridge contract. The tool records a disposal: "user sent ETH to an external address."
2. Destination chain: ETH appears in your wallet on Arbitrum from what looks like a new source. The tool records an acquisition: "user received ETH from an external address."

Two separate events, on two separate chains, with no obvious link between them. The tool has no way to know these are two sides of the same operation. Result: a phantom disposal on mainnet and a fresh acquisition on Arbitrum with a reset cost basis.

Do not automatically deduct bridge gas

A bridge fee is not automatically an allowable Capital Gains Tax cost merely because it was paid on-chain.

HMRC CRYPTO22150 allows transaction fees connected with an acquisition or disposal. A same-owner bridge treated as basis carry is not, by that fact alone, an acquisition or disposal. The purpose and tax treatment of the transaction must be established before claiming the fee.

In practice:

• Do not add ordinary same-owner bridge gas to the Section 104 pool automatically.
• If the route includes a disposal or acquisition, attribute only the qualifying directly connected cost on a just and reasonable basis.
• Keep the receipt and purpose visible so an adviser can confirm any material claim.

Edge cases: when a bridge might be taxable

There are a few situations where a cross-chain operation is a taxable event, even if it looks like a bridge:

• Token swaps via bridge aggregators. Some aggregators (e.g. certain Hop routes) swap through an intermediate token during the bridge. If you send USDC on Ethereum and receive DAI on Arbitrum, that's an exchange of different assets, which is a disposal. ChainTax checks the input and output tokens; if they differ, it classifies as Disposal rather than Transfer.
• Wrapped representations with different economics. Bridging ETH to a chain that uses a wrapped representation (like WETH on Polygon) may support basis carry where the rights and beneficial owner are preserved. Receiving a yield-bearing derivative or otherwise different set of rights needs separate analysis.
• Third-party bridges with fees taken as tokens. If a bridge delivers fewer tokens than were sent, record the unit difference and fee evidence. Its allowable-cost treatment depends on whether it is connected with a qualifying acquisition or disposal.

Where the proposed NGNL regime fits in

You may have seen HMRC's proposed No Gain / No Loss (NGNL) regime mentioned alongside DeFi tax. It's worth being clear about one thing: the draft NGNL measure targets qualifying DeFi lending and automated market-making arrangements, not bridge classification. Current bridge treatment still follows CRYPTO22100 and CRYPTO22110: asset identity, rights, and beneficial ownership matter.

The proposed NGNL regime is a separate measure aimed at lending, borrowing, and moving tokens into and out of liquidity pools, the cases where today's rules can trigger an awkward disposal. It does not replace the facts-and-circumstances analysis for a cross-ledger movement.

ChainTax applies disclosed basis-carry treatment to verified supported same-owner, same-asset bridge routes and leaves mismatched evidence for review.

How to check your bridge transactions

1. Review your tax report for bridge-related disposals. Search for transactions involving known bridge contracts. If your tool shows a Disposal on a bridge transaction, compare the source and destination assets, rights, and owner before deciding whether it is wrong.
2. Check for cost basis resets after bridges. If your cost basis on the destination chain starts from the bridge date rather than carrying over from your original acquisition, the pool may be wrong where the facts support basis carry. A UK crypto tax calculator that recognises bridge contracts will leave your pool intact across chains.
3. Verify WETH wrap/unwrap handling. If your tool treats a direct ETH→WETH or WETH→ETH wrap as a swap, check whether beneficial ownership and economic exposure were preserved.
4. Use a tool that reads contract-level data. Surface-level token flow analysis cannot distinguish a bridge from a sale. You need a classifier that understands which contracts are bridges and what the transaction method signatures mean. Try the free transaction explainer →

Summary: bridge transactions and UK tax