A bridge transfer moves value from one blockchain to another. The asset itself does not travel. The bridge locks or burns your tokens on the chain you are leaving and issues equivalent tokens on the chain you are arriving on, and the version you end up holding may or may not be the same asset in tax terms.
Blockchains cannot read each other, so every bridge is a workaround built on one of three patterns.
Lock and mint holds your tokens in a contract on the source chain and mints a representation on the destination chain. Burn and mint destroys the tokens on one side and issues native tokens on the other, which is how canonical bridges for a chain's own token usually work. Liquidity network bridges hold pools on both sides, taking your deposit into one and paying you out of the other, which puts them closer to a swap with two counterparties than to a transfer.
What you receive depends on the pattern. USDC bridged one way may be native USDC issued by Circle. Bridged another way it may be a wrapper issued by the bridge, with its own contract address and its own risk. Bridged assets are often supplied straight into a lending protocol or a pool on arrival, which stacks a second transaction on top of the first.
It depends on what the bridge did, and the IRS has not published guidance on bridging.
Where you move an asset to another chain and hold the same asset at the end, the case for treating it as a non-taxable transfer between wallets you control is reasonable. Nothing was sold and no counterparty received your property.
Where the bridge hands you a different token, the analysis changes. Receiving a bridge-issued wrapped token in place of the native asset is closer to an exchange of one property for another under section 1001. A liquidity network bridge that pays you out of a pool has more in common with a trade than a transfer.
Bridge fees, gas on both chains and any slippage are part of the transaction and belong in the cost basis calculation rather than being left out of it.
Bridges break cost basis more often than any other DeFi transaction. The send and the receive sit on different chains, minutes or hours apart, in different tokens, with different contract addresses. Tax software sees a disposal on one chain and an acquisition with no history on the other. The result is a gain that was never made on the outbound leg and a zero basis on the inbound one, so the same value gets taxed twice. Matching the two legs by hand is often the only fix.
Read our 2026 Guide to DeFi Taxes
CountDeFi specializes in complex DeFi tax accounting, including bridges, wrapped assets and multi-chain activity. See pricing.
