How to Track Cost Basis Across a Crypto Bridge

A cross-chain transfer moves crypto from one blockchain to another, so its record must connect the asset leaving one ledger with the asset arriving on the next. The source transaction shows what you sent; the destination transaction shows what you received. Together with the bridge route and fee details, they help you tell a transfer from a sale or exchange and carry forward the asset’s cost basis where the rules that apply to you allow it.

What happens to crypto during a cross-chain transfer?

A bridge coordinates transactions on separate blockchains, which do not share one transaction history. In a common lock-and-mint design, a contract locks the asset on the source chain. A bridge operator, validator set or other verification system checks that event. A contract on the destination chain then releases or creates a corresponding asset. Some bridges use different designs, including burning an asset on one chain or routing through a pool of liquidity.

Think of it as a tracked parcel: the dispatch scan and delivery scan are separate records, and you need both to show the journey. The analogy ends there; a bridge transaction is confirmed by blockchain protocols and contracts, not a shipping carrier. For a quick overview of route choices and their moving parts, see this guide to Mantle Bridge routes for ETH or MNT transfers. The accounting record still needs to match the transactions to your own wallets and the exact assets involved.

Does moving crypto between chains change its cost basis?

A wallet address changing does not by itself tell you that you sold an asset. If the same owner moves an asset between their own wallets, the transfer may preserve its existing basis under the rules that apply in their jurisdiction. But a bridge route can involve more than relocation: it may exchange one token for another, wrap an asset, or take a fee in crypto. Those details can change how the event is classified.

Cost basis is the tracked value assigned to an asset for calculating a gain or loss when it is later disposed of. A bridge receipt should not be treated as a fresh purchase automatically. First establish whether the destination asset is the same asset, a wrapped representation, or a different token received in an exchange. Then record the route and fee treatment consistently with the tax rules where you file.

What records should you keep for a bridge transfer?

Keep enough information to join the source and destination events. A transaction hash alone may prove that a transaction occurred, but it may not explain why the destination wallet received a different token or less than the amount sent. A useful record includes:

• The source and destination chains, wallet addresses and transaction hashes.
• The token, amount and timestamp on each side, including any difference between sent and received amounts.
• The bridge or route used, plus receipts, confirmations or other records linking the two transactions.
• Any fee, the token used to pay it, and the value or conversion information needed for your records.

Save exchange or wallet statements alongside the public transaction data. A bridge explorer can help locate events, but it may not know which wallets you control or how you acquired the tokens. Keep the original acquisition record too: moving an asset across chains does not erase when, where or at what cost you acquired it.

How should you reconcile a bridge in your ledger?

Enter the outgoing and incoming events as one linked transfer when the facts and applicable rules support that treatment. Reconcile the quantities after accounting for fees, and investigate unmatched deposits before assigning them a new basis. If the route swaps assets or the records do not line up, preserve the evidence and classify each step under the rules that apply to you. A ledger that records both sides and the reason for the movement is more useful than a list of deposits alone.