Five Records to Save for Cross-Chain Crypto Taxes

For every cross-chain crypto move, save five records as soon as it completes: the source and destination transactions, wallet addresses, asset amounts, and value and fee evidence. A bridge can involve separate transactions on separate networks, so one explorer page may show only part of what happened.

• The source-chain transaction hash and its status.
• The destination-chain transaction hash and its status.
• The sending and receiving wallet addresses, plus proof those wallets are yours.
• The tokens and amounts sent and received, with the network named for each.

What should you save from each side of a cross-chain move?

Save the source and destination transactions separately, including their dates, times, hashes and final status. A transaction hash is the unique identifier for an on-chain transaction; it lets you reopen the record in a block explorer later.

Keep a copy of each transaction’s details, not only a bookmark to an explorer. Explorer sites can change, and a link may not make clear which wallet you controlled or why the two transactions belong together. Export the wallet’s transaction history when available, and store it with your tax records.

Record the sending and receiving addresses and label which wallet you control. If an exchange or another service handled one leg, save its receipt or activity export too. The public ledger shows addresses and activity, but it does not by itself establish who owns an address or what prompted a transfer.

How do you match a bridge transfer across chains?

Match the two sides using the token, amount, wallet and timing, then write down the bridge or swap service involved. A transfer may burn or lock tokens on one chain and release or mint tokens on another; the destination amount can differ because of fees, conversion rates or the service’s design.

Your note should explain the relationship in plain language: what left, what arrived, and which transactions show each step. Keep any route quote, confirmation screen, email receipt or protocol record that helps connect them. These off-chain records can fill gaps when a destination transaction is delayed or an explorer’s description is terse.

If a QuickSwap transaction is still pending, save its hash and status before retrying or submitting another transaction. For the steps that address a delay, see this guide to a pending QuickSwap swap. Keep the original and later records together so your notes show whether the first attempt completed, failed or was replaced.

Do not assume that every bridge is just a transfer between wallets. Some routes exchange one token for another, or use a wrapped token on the destination chain. Record what the service actually did; tax treatment depends on your jurisdiction and the transaction details.

How should you record value, fees and token amounts?

The fifth record is a value and fee worksheet for the move. Note each token’s amount and value at the transaction time in the currency used for your tax reporting, the source and destination fees, and the token used to pay each fee. Keep the pricing source or calculation with the worksheet, rather than relying on a number copied into a tax app without its context.

Keep units precise. Token tickers are reused, and the same token name can refer to different contracts or networks. Record the network and, where relevant, the token contract address so you can distinguish assets that look alike in a wallet.

Store the five records together with a short note of your reasoning. A clean record lets you reconstruct the move later, check whether the tokens and amounts line up, and explain missing or unmatched entries. Save exchange exports and wallet records regularly, since services may not retain them indefinitely.