Document note only. Field Ledger is not a tax firm, cloud reseller, dental office, or insurer. Read your own form and confirm it with the preparer, billing desk, carrier, or another licensed professional.
This standardized cross-reference table maps wrapped-token unwrap and disposal rows for accurate crypto tax and asset record maintenance. It eliminates common classification errors that can lead to misreported cost basis, incorrect capital gain or loss calculations, and audit inquiries for both individual and business crypto asset holders. All entries align with record-keeping requirements set forth by federal tax authorities for virtual asset transactions, and are designed to work with existing Field Ledger crypto tax folder structures if you use that platform for record storage. You should always cross-reference all entries with original on-chain transaction receipts and exchange trade confirmations before submitting any tax documentation to a preparer or regulatory body.
Unwrap Event Column Requirements for Cross-Referenced Table Entries
An unwrap event describes the conversion of a pegged wrapped token (such as WETH, wrapped SOL, or wrapped AVAX) to its native underlying asset, with no change in beneficial ownership of the asset. While unwrap events are not classified as taxable events in most jurisdictions, you must track all associated data points to maintain consistent cost basis records and prove non-taxable status if requested. Required columns for all unwrap entries in your cross-reference table include: unique on-chain transaction ID (hash), wrapped token contract address, native underlying token contract address, transaction timestamp recorded in UTC to the nearest second, pre-unwrap wrapped token amount recorded to full decimal precision, post-unwrap native token amount recorded to full decimal precision, total protocol and gas fees denominated in both the transacted token and USD at the time of the transaction, wallet address initiating the unwrap, and wallet address receiving the native token. For an entry to qualify as an unwrap, the sending and receiving wallet addresses must be identical, unless you can provide formal documentation that both addresses are owned by the same taxable entity. Illustrative example: A user unwrapping 2.7 WBTC to native BTC would record the 0.0002 WBTC protocol fee as a separate line item, rather than deducting it from the post-unwrap BTC amount without supporting documentation.
Disposal Action Box Distinctions Between Unwrap and Disposition Entries
The action box is a mandatory free-text field in your cross-reference table that explicitly labels the transaction type for quick sorting by you or your tax preparer, no abbreviations or shorthand are permitted to avoid misclassification. For all qualifying unwrap events, the action box must be marked in all caps: “UNWRAP – NON-TAXABLE”. For all disposal events, the action box must be marked with the specific disposal category in all caps: “DISPOSAL – SALE”, “DISPOSAL – TRADE”, “DISPOSAL – GIFT”, or “DISPOSAL – THIRD-PARTY TRANSFER”. Any conversion of a wrapped token to an asset that is not its native underlying token automatically qualifies as a disposal, even if the received asset is another wrapped token. For example, converting WETH to WBTC is a disposal, not an unwrap, as the received asset is not the native underlying of WETH. Any conversion sent to a wallet address not registered to the same taxable entity as the sending wallet also automatically qualifies as a disposal, even if the received asset is the native underlying of the wrapped token. Clear action box labeling cuts down on tax prep time by eliminating the need for manual review of every on-chain hash to classify transactions.
Cost Basis Note Fields for Both Wrapped-Token Transaction Types
The cost basis note field is a mandatory field that links each transaction to its original cost basis record to avoid inconsistent or incorrect gain/loss calculations. For unwrap events, the cost basis of the received native token is exactly equal to the cost basis of the unwrapped wrapped token, plus any applicable protocol and gas fees paid to complete the unwrap. The holding period of the wrapped token also carries over to the native token, so the note field must include the original purchase date and transaction ID of the wrapped token, plus a direct link to the supporting purchase receipt in your file system. For disposal events, the note field must include the original purchase date and transaction ID of the disposed wrapped token, the fair market value of the disposed token at the time of the transaction, total fees associated with the disposal, and the total proceeds received from the disposal denominated in USD. You should never combine cost basis records for multiple unrelated transactions in a single note field entry, as this can lead to calculation errors during tax prep. Illustrative example: If you purchased 3 WETH on June 14, 2022, for $3,900 total including fees, then unwrapped 1.5 WETH on January 7, 2024, the cost basis of the 1.5 ETH received is $1,950 plus the $2.10 USD equivalent protocol and gas fee for the unwrap, for a total cost basis of $1,952.10, which you would note alongside a link to the June 14, 2022 purchase transaction ID.
Token Amount Schedule Alignment for Accurate Record Matching
All entries in your cross-reference table must align with your quarterly and annual token holding schedules to avoid gaps, overstatements, or understatements of your crypto asset holdings. For unwrap events, your wrapped token holding schedule must show a decrease equal to the total pre-unwrap amount of the wrapped token, and your native token holding schedule must show an increase equal to the post-unwrap amount of the native token, with fees recorded as a separate line item expense. For disposal events, your wrapped token holding schedule must show a decrease equal to the total amount of the disposed token, and your capital gains or income schedule must show the total proceeds from the disposal. Any discrepancy between the on-chain transaction amount and the amount recorded on your exchange or wallet statement must be noted in the transaction’s note field, with copies of both the on-chain block explorer receipt and the exchange statement stored in the transaction’s supporting folder. All amounts must be recorded to the full decimal precision supported by the token’s smart contract to avoid cumulative rounding errors across multiple transactions. The table below summarizes core differences between unwrap and disposal rows for quick reference during reconciliation:
| Transaction Type | Action Box Label | Required Core Columns | Cost Basis Treatment | Classification Reference (consult licensed tax preparer for official guidance) |
|---|---|---|---|---|
| Standard Unwrap (same sending/receiving wallet, native underlying asset received) | UNWRAP – NON-TAXABLE | On-chain TX ID, wrapped token address, native token address, UTC timestamp, pre-unwrap amount, post-unwrap amount, total fees, sending/receiving wallet addresses | Cost basis of wrapped token carries over to received native token, plus applicable unwrap fees | Non-taxable (most jurisdictions, confirm holding period and ownership rules with your preparer) |
| Cross-Wallet Unwrap (sending wallet != receiving wallet, native underlying asset received, no proof of shared ownership) | DISPOSAL – THIRD-PARTY TRANSFER | All standard unwrap columns, plus recipient wallet ownership documentation if available | Cost basis of wrapped token compared to fair market value of received asset at transaction time to calculate gain/loss | Taxable disposal (most jurisdictions, confirm gift or transfer rules with your preparer) |
| Wrapped Token Trade for Non-Native Asset | DISPOSAL – TRADE | On-chain TX ID, sent and received token addresses, UTC timestamp, sent amount, received amount, total fees, sending/receiving wallet addresses | Cost basis of wrapped token compared to fair market value of received non-native asset at transaction time to calculate gain/loss | Taxable disposal (most jurisdictions, confirm like-kind exchange rules with your preparer) |
| Wrapped Token Sale for Fiat Currency | DISPOSAL – SALE | Exchange TX ID, UTC timestamp, wrapped token amount sold, total fiat proceeds, total exchange and gas fees | Cost basis of wrapped token compared to net fiat proceeds (proceeds minus fees) to calculate gain/loss | Taxable disposal (most jurisdictions, confirm income reporting rules with your preparer) |
| Wrapped Token Gift to Unrelated Third Party | DISPOSAL – GIFT | On-chain TX ID, UTC timestamp, wrapped token amount sent, recipient wallet address, total fees | Cost basis of wrapped token carries over to the recipient, no gain/loss recognized by sender below annual gift thresholds | Non-taxable for sender below annual gift limits (confirm gifting rules with your preparer) |
Supporting Form Folder Organization for Table Verification Tasks
Proper folder organization ensures you can quickly locate supporting documentation for any entry in your cross-reference table during tax prep or an audit. Start with a top-level crypto tax folder for the applicable tax year, with two dedicated subfolders: “Wrapped Token Unwrap Transactions” and “Wrapped Token Disposal Transactions”. Each subfolder contains individual transaction folders named for the full on-chain or exchange transaction ID of the entry. Each individual transaction folder must include four items: a full screenshot of the transaction from a public block explorer showing all addresses, amounts, and timestamps, a copy of the exchange or wallet confirmation receipt for the transaction, a direct link to the original purchase receipt for the wrapped token associated with the transaction, and a copy of your manual cost basis calculation if you did not use automated software to generate it. If you use Field Ledger, you can upload these documents directly to the corresponding transaction entry in the platform for centralized access and sharing with your tax preparer. Retain all supporting documentation for a minimum of 7 years per standard federal tax record retention requirements. You should also maintain a separate master cross-reference index that lists every transaction ID, its type, and the location of its supporting folder to speed up retrieval requests.
Before your next quarterly crypto asset reconciliation, pull all wrapped token conversion transactions from the prior 90 days, label each with the correct action box entry per the table above, and file supporting receipts in the appropriate folder.