A bridge transfer leaves records on two chains

A cross-chain bridge transfer can create records on two blockchains, so a useful tax export must connect the transaction that sends the asset with the one that delivers it. The source chain records the first action, such as a deposit or token burn. A bridge contract or service carries a message, and a destination chain records a release or a newly minted token. The two records may have different transaction IDs, timestamps and token names.

That is why a wallet’s single activity line may not be enough. For a plain-language account of the user-facing steps, see this Manta bridge first-transfer guide; it explains the path a transfer takes while the records here focus on reconciling it. Treat the two on-chain entries like receipts for opposite ends of one parcel: keep both, then connect them with the bridge’s transfer reference where available.

What records does a bridge transfer create?

The source-chain transaction shows what left your wallet and what the network charged to process it. The destination-chain transaction shows what arrived, or whether the transfer is still pending. Some bridges release an existing token from a pool; others mint a representation on the destination chain. The mechanics differ, so do not assume that matching names mean matching assets or that the destination amount must equal the source amount.

Start with the bridge’s own transfer history if it provides one. Then check each transaction hash on the relevant chain explorer. The bridge interface can help match the source event to the destination event, but the chain record is the evidence of what was recorded. Save these details for each leg:

• Source and destination chain names, wallet addresses and transaction hashes.
• Token names or symbols, contract addresses where shown, and amounts sent and received.
• Dates and times, including the time zone or UTC setting used by the export.
• Network and bridge fees, plus any status or transfer reference linking the two legs.

Keep the original CSV or downloaded report alongside your working spreadsheet. An export can omit failed attempts, pending transfers, token contract addresses or fees paid in a different asset. If the bridge shows a transfer as complete but the destination explorer does not show the expected transaction, keep the status and lookup details rather than recording an arrival you cannot verify.

How do I export and reconcile cross-chain activity?

Export activity separately for every wallet and chain you used. A wallet app may show a combined view, but its export may cover only one network or one address. In each explorer, search the address and download transaction history if that option is available. Use the bridge’s transfer page to find the destination hash or message reference when the two explorer records do not identify each other.

Build one row per leg, not one row per bridge transfer. Add a shared transfer reference to the source and destination rows when you can establish the match. Record the asset and amount on each side, the fees, and the status. Keep a note for unmatched entries: a delayed destination transaction, a refund, or a fee paid in another token can otherwise look like a missing or duplicated movement.

Preserve the raw exports before changing formats or correcting labels. If you convert timestamps, retain the original value as well. A spreadsheet can make amounts line up while hiding a difference in token contract, chain or date. Those distinctions matter when later working out what was held, received, exchanged or disposed of.

Does moving tokens through a bridge trigger tax?

The export documents activity; it does not decide its tax treatment. Rules vary by jurisdiction, and a bridge can involve more than a simple transfer between wallets. A fee paid in tokens, a swap into a different asset, a wrapped-token issue or a change in who controls the asset may need separate analysis. Do not label every bridge movement either taxable or tax-free based only on the word “transfer.”

For example, US IRS guidance generally treats a transfer between wallets you own as non-taxable, but says digital assets used to pay transfer services can be an exception. HMRC guidance asks UK taxpayers to keep transaction-level records and identifies exchanging one cryptoasset for another as a disposal for capital gains purposes. These rules are jurisdiction-specific; the bridge’s records let you and a tax professional determine which events matter under the rules that apply to you.

The practical goal is a traceable pair of records, not a single total. Export early, preserve both chain histories, and reconcile each source action with its destination result before calculating gains, income or fees.