How to Track Cost Basis After a Stuck Wrapped Transfer
A delayed wrapped-token transfer does not automatically create a new tax lot. Trace the source debit, destination receipt, fees and any later swap before updating basis.
The Tareom Editors4 min read

When you send a wrapped asset across chains and the transfer stalls, keep the original lot’s cost basis tied to it until you can account for the destination or a recovery. The key is to reconcile what left the source chain with what arrived, returned or remains pending; a delayed receipt alone does not tell you that you bought or sold anything.
- Record the source token, amount and transaction hash.
- Check whether the source transfer locked or burned the token.
- Match any destination mint, release or refund to that source event.
- Record bridge fees and any later swap as separate entries.
Does a stuck transfer create a new cost basis?
A stuck transfer does not, by itself, establish a new purchase or a new cost basis. Cost basis is the recorded acquisition cost of an asset, adjusted as required by the rules that apply to you; moving an asset between wallets you control may leave that record unchanged.
Wrapped assets complicate the record because a bridge may lock an original token on one chain and issue a token representing a claim on another. Some systems burn the source token and mint a representation at the destination; others use different mechanisms. The token name alone does not prove that two balances represent the same asset or that a bridge action has a particular tax treatment.
Keep the source and destination events linked, then establish what happened to the claim. If the destination token arrives as the continuation of the same holding, preserve the lot details in your records rather than treating the mint as an unrelated purchase. Tax treatment can depend on the bridge, asset and jurisdiction, so don’t treat that bookkeeping approach as a universal tax ruling.
How do you reconcile a transfer that has not arrived?
Start with the source transaction and check its status on the source chain. A submitted transaction can fail before it moves tokens; a confirmed transaction may lock or burn them while a separate destination step is still pending.
Look for a matching destination event, bridge status or documented recovery path. Save transaction hashes and timestamps for both chains, the token contract addresses, amounts, and the bridge’s stated status. If the destination shows less than the source amount, account for any stated fee or deduction instead of silently changing the lot quantity.
If the transfer is eventually refunded, record the return against the original movement and confirm whether the returned asset is the same token and amount. If it is still pending, keep it marked as unresolved in your records; don’t count both the source and a hoped-for destination balance as available holdings. Reconcile balances from the chain records before you close the entry.
What if you swap the asset after it arrives?
A swap is a separate event from the transfer, so record it separately when it occurs. The swap may dispose of the asset you gave up and create a new lot for the token you received, depending on your jurisdiction’s rules.
Keep the amount exchanged, the output received, the transaction hash and any fees with the transfer record. If the bridge or swap route deducted part of the value, use the actual onchain amounts in your reconciliation rather than a quote shown before execution. A quote describes an expected result; it does not prove what settled.
If a swap itself stalls, check whether the transaction failed, remains pending or completed before trying again. A different route can change the expected output and execution cost; for details on comparing options, see how to choose a quickswap route. Keep that swap record distinct from the wrapped-token transfer so the same movement is not counted twice.
What should you keep for your records?
Keep enough evidence to rebuild the chain of events later: acquisition records for the original lot, source and destination transactions, bridge messages or receipts, and any refund or swap. Note the quantity and token identity at each step, along with fees and the date and time shown by the relevant records.
When amounts differ, preserve the original lot details and document the difference rather than forcing the numbers to match. If the bridge changes the asset, the destination never arrives, or the records conflict, get advice for your jurisdiction before deciding how to report the event. The practical rule is simple: carry the lot forward only when you can support how the asset moved, and record any exchange or loss as its own event.