Bridging Transactions

How to handle bridging/cross-chain transactions on the platform

Patrick McGimpsey avatar
Written by Patrick McGimpsey
Updated over a week ago

Note: Bridging is not yet implemented for UK users using the HMRC method or Canada users using the ACB method.

Just as the name suggests, a blockchain bridge connects two different chains and allows assets to move from one to the other. Bridging is a relatively new transaction type that has been born out of necessity as more blockchains are created and DeFi users wish to move their assets from chain to chain to take advantage of different opportunities.

Bridging often consists of many different transactions and can even result in the change of the underlying asset to a pegged or wrapped derivative (depending on the bridge and source/destination chain). CryptoTaxCalculator can handle these complex transactions, allowing you to reconcile any cross-chain transactions and report your tax obligations correctly.

Handling Bridging in the Platform

To handle bridging in the platform, follow these simple steps:

1. Find the transactions related to the bridging event under ‘Review Transactions’. Usually they will be split into an ‘outgoing’ component (sending to the bridge) and an ‘incoming’ component (receiving the asset on the other chain). The example below shows 0.5 WETH being bridged from Ethereum to Avalanche.

2. Re-categorize the ‘outgoing’ component as ‘Bridge Out’. Do this by clicking on the category box, selecting ‘Advanced’ and then choose the category ‘Bridge Out’ on the right side of the page.

3. Re-categorize the ‘incoming’ component as ‘Bridge In’ using the same process as step 2.

4. The two components will then group to form a single line categorized as a ‘Bridge’. The cost basis from the original asset will be moved across to the asset on the destination chain, even if it is a pegged or wrapped version of the original asset.

Important Notes

  • Both the ‘Bridge Out’ and ‘Bridge In’ components must occur within a 24-hour timeframe for them to be grouped together.

  • 'Bridge Out’ should be earlier than ‘Bridge In’.

  • A ‘Bridge Out’ will match with the next ‘Bridge In’ in chronological order if the following criteria are fulfilled:

    • The two components are within 24 hours

    • The amount that is received is similar to the amount that was sent (5% tolerance accepted)

  • If multiple bridges of the same amount are done in the same 24 hours, ensure that the corresponding ‘Bridge Out’ and ‘Bridge In’ are chronologically one after the other.

  • Bridging transactions will not be auto-categorized, they require manual selection due to the complex nature of the transaction.

  • The cost basis of the original asset on the source chain will be transferred to the asset that is received on the destination chain whether it is the same asset or a pegged/wrapped version.

Did this answer your question?