Bridging and cross-chain fees: the real risk is your broken cost basis

Last updated: March 2026 · Reading time: 7 minutes

Many Belgian crypto investors think bridging is a simple technical detail: you send ETH, USDC or another token from Ethereum to Base or Arbitrum, and you are done. Surely there is nothing special about it for tax purposes?

Fundamentally, that is correct. Bridging is usually not a taxable sale. But that is exactly where the danger lies: as soon as your tooling or records fail to recognize that movement as continuity, you end up with a distorted file. It then looks as if you sold something on chain A and bought it again on chain B, resulting in an incorrect cost basis and sometimes even a fictitious capital gain.

That is why the right question is not only "Is bridging taxable?", but above all: how do you prevent cross-chain transfers from breaking your cost basis and FIFO calculation? In this article we explain where things go wrong, which bridge fees really count, and how CryptoTax automatically links source and destination legs to each other.

The short version

• Bridging the same asset is generally not a taxable event
• The real risk is that a bridge is wrongly reconstructed as a sale + new purchase
• Bridge fees, bonder fees and protocol costs belong in your cost file
• Slippage, subsidies and incentive tokens can have a separate tax impact
• Hop, Across, Orbiter, Stargate and Circle CCTP each use a different technical flow
• CryptoTax matches both legs, maintains continuity and links fees to the same bridge flow

1. Bridging is usually not a sale

When you move the same asset from chain A to chain B, in economic terms you usually change nothing about your position. You still have the same exposure, just on a different network.

Examples:

• you bridge ETH from Ethereum to Arbitrum
• you send native USDC via Circle CCTP from Ethereum to Base
• you move WETH or USDC via Across, Hop, Orbiter or Stargate

In all of those cases the main intuition is the same: this is generally a movement, not a realization of a capital gain. The tax challenge therefore does not lie in the existence of the bridge itself, but in reconstructing it correctly.

2. Where things usually go wrong: a broken cost basis

The real problem arises when your source and destination chain are not read together. A tool or spreadsheet then sees:

• an outgoing transfer or burn on chain A
• an incoming transfer or mint on chain B

Without bridge logic, that looks like two separate events. The result:

• your original lot disappears on chain A
• a "new" lot appears on chain B
• the original acquisition date and acquisition price are lost
• later sales use an incorrect FIFO basis

That is exactly how phantom gains arise: not because you made an economic profit when bridging, but because your historical cost basis was not carried over correctly to the destination chain.

3. Why bridges are so tricky technically

Not every bridge works the same way. That makes automatic reconstruction harder than many investors think.

Depending on the protocol, you may see, for example:

• lock-and-mint flows
• burn-and-mint flows such as with Circle CCTP
• intent-based settlement via relayers such as with Across
• bonder liquidity and temporary representation tokens such as with Hop
• maker-based transfers such as with Orbiter
• liquidity pool bridges such as with Stargate

To a human, those flows often look like "I sent something and got something back". To a tax engine, they are several on-chain steps with different timestamps, counterparties and fee structures. That is precisely why manual reconstruction so often goes wrong.

4. Which bridge fees really count?

Using a bridge feels cheap as long as you only look at the UI. But in your tax file several costs can be in play at the same time:

• gas on the source chain
• gas or a receiving step on the destination chain
• protocol fee
• bonder or relayer fee
• slippage between the amount sent and the amount received
• any attestation or settlement costs

These costs seem small per transaction, but they become important once you bridge frequently between Ethereum, Base, Arbitrum and other L2s. If they are not correctly linked to the same transfer flow, you lose not only auditability but also part of your real economic cost.

5. When does bridging actually have a tax impact?

The main flow is usually not taxable. But certain side effects can have tax consequences:

• slippage or value differences between departure and arrival
• bridge subsidies or refunds, for example in incentive campaigns
• governance or reward tokens that you receive for providing liquidity or using the protocol
• incorrectly matched representation tokens that cause something to be wrongly seen as a swap

That distinction matters. "Bridging is not taxable" does not mean that everything around bridges is automatically neutral. The underlying transfer can be neutral, while fees, incentives or technical intermediate steps must remain visible separately.

6. How CryptoTax handles bridging

CryptoTax does not treat bridging as two separate transactions, but as a coherent continuity flow across chains. This matches how we also explain our FIFO cost basis: lots must carry over when your economic position carries over.

In concrete terms, we do three things:

1. Match the source and destination leg based on timing, asset, value and protocol pattern
2. Preserve the cost basis so that the original lot continues to live on chain B with the same historical context
3. Link fees to the same flow so that your audit trail shows what the bridge really cost

This prevents the same bridge from later showing up in your report as an artificial sale, a "spontaneous" new purchase or a standalone incoming transfer with no origin.

7. How we handle the differences per bridge

Not every protocol requires exactly the same heuristic. That is why we combine generic transfer matching with protocol-specific detection.

Examples from our current coverage:

• Circle CCTP: burn on the source chain, mint on the destination chain, cost basis stays intact
• Stargate: source/destination linking plus bridge and LayerZero fees
• Across: intent, relayer fulfillment and settlement context as one bridge story
• Hop: hToken mint/burn, bonder fees and any subsidies or fallback settlement
• Orbiter: send/receive matching with a maker-based fee structure

For you as a user, that means one practical benefit: you do not have to explain yourself why a particular incoming transfer on Arbitrum in your Belgian report was really just the other half of your Ethereum bridge.

8. Why this matters so much for FIFO

Belgium expects your cost basis to be tracked correctly. As soon as you use multiple chains, you will otherwise run into a problem sooner or later with later disposals.

Suppose:

• you buy ETH on Ethereum in January
• you bridge that ETH in April to Base
• you sell part of that position on Base in September

If the bridge is not treated correctly as continuity, it looks as if the ETH on Base was only "acquired" in April. Your FIFO order is then no longer correct and your result is artificially distorted. You can read more about this in our guide on cost basis and FIFO.

9. A practical checklist for your own file

Do you use bridges often? Then you want to be able to demonstrate at least this:

1. which asset left the source chain
2. which amount arrived on the destination chain
3. which fees were paid along the way
4. whether there were subsidies, rewards or slippage
5. that the original cost basis was preserved on the destination chain

That is why we recommend keeping not only your wallet transactions but also a report in which the source and destination legs are visibly linked to each other. You can read more about documentation in our guide on supporting documents for your crypto tax return.

10. The real tax message of bridging

The mistake is usually not that someone thinks "bridging is taxable". The mistake is more subtle: people underestimate how quickly an incorrect reconstruction contaminates the rest of the file.

A poorly matched bridge does not only cause noise on that one day. It also distorts:

• later FIFO calculations
• unrealized portfolio overviews
• the classification of fees and slippage
• the audit trail toward your accountant or the tax authorities

So bridging is often not a taxable event, but it is one of the most important sources of tax errors once you are active across multiple chains.

Conclusion

Cross-chain bridges look technically simple, but they are dangerous for tax purposes as soon as the continuity between source and destination disappears. The main risk is not a direct tax on the bridge itself, but a broken cost basis that later causes fictitious gains or incorrect disposals.

CryptoTax tackles that problem where it really arises: by matching bridge legs across chains, linking fees to the same flow and keeping your lot history intact for later FIFO calculations.

Do you use Ethereum, Base, Arbitrum and other networks interchangeably? Start for free with CryptoTax and see how bridge transfers, fees and cross-chain continuity automatically end up in your Belgian report.

Disclaimer: this article is purely informative and not individual tax advice. For specific files or borderline cases, we recommend consulting a Belgian tax specialist.