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 entry vs exit hash card stores verifiable DeFi transaction records for cross-referencing on public blockchain ledgers. It is intended for use in cryptocurrency tax record keeping workflows to demonstrate the timing and value of asset movements between self-custody wallets, centralized platforms, and DeFi protocol contracts, per record retention requirements set by U.S. tax authorities for digital asset transactions. Field Ledger users may adapt this template for their personal record folders, and should always consult a licensed tax professional before submitting related documentation with any tax filing. This document does not constitute tax advice, and all reported transaction values should be verified against official chain explorer records and your own wallet transaction history prior to use in any official filing.
Entry Hash Column Alignment Specifications
The entry hash column is reserved for the unique transaction hash of the initial on-chain transaction that initiates a DeFi position, whether that is a liquidity pool deposit, token swap into a protocol-specific asset, staking deposit, collateral lock for a lending position, or mint transaction for a derivative asset. This column must be left-aligned on all printed and digital versions of the card, with space for the full 66-character hexadecimal string to be entered without truncation. Optional secondary columns may be added to the far left of the full entry hash column to display only the first 8 and last 8 characters of the hash for quick visual scanning, but the full string must always be included in the primary entry hash column to ensure verifiability against on-chain records. Mandatory adjacent columns that must be aligned horizontally with each entry hash row include: UTC timestamp of the entry transaction in ISO 8601 format, public wallet address initiating the entry transaction, recipient protocol or counterparty wallet address, asset type and exact quantity transferred to initiate the position, and gas fee paid in the native chain token for the transaction. Each entry hash may only be listed once per row, and grouping multiple entry hashes in a single row is prohibited to eliminate the risk of cross-reference errors when matching entry and exit records.
Exit Hash Box Labeling Requirements
Each exit hash corresponds to the on-chain transaction that closes or partially closes the DeFi position associated with the corresponding entry hash, including full or partial liquidity pool withdrawals, staking unstake and claim transactions, swap finalization out of a protocol-specific asset, collateral release from a lending position, or claimed reward distributions from staking or liquidity provision. The primary exit hash box must be located immediately to the right of the associated entry hash column on the card, with a 1/8 inch printed solid border to distinguish it from adjacent data fields and eliminate confusion between entry and exit records. Required labeling elements inside each pre-printed exit hash box, printed in 10pt sans-serif font for readability, include the header “Exit Hash”, a full-length blank line for the full 66-character hex string, a smaller blank line directly below for the truncated 8/8 character short hash for quick indexing, and a small check box to mark if the exit is a partial position closure. If multiple exit hashes apply to a single entry hash (for example, partial withdrawals executed over multiple months or years), add additional stacked exit hash boxes below the primary box, each labeled sequentially “Exit Hash 1”, “Exit Hash 2”, and so on, with corresponding fields for timestamp and asset quantity aligned to each box. No handwritten modifications to pre-printed box labels are allowed; if more exit boxes are needed than are pre-printed on the standard card, attach a supplementary continuation sheet and reference it in the discrepancy note section for the associated entry hash.
Cross-Reference Form Filing Procedures
Each completed entry vs exit hash card must be attached to the corresponding supporting documentation for IRS Form 8949 and Schedule D for the tax year in which the exit transaction was executed, as these forms are used to report capital gains and losses from digital asset transactions. If the DeFi position spans multiple tax years, a copy of the card must be filed with the tax return for each year a partial exit, reward distribution, or other taxable event related to the position occurs, with a clear notation on the top right corner of the card indicating “Partial Exit, Year [YYYY], Full Card Retained in Permanent File” to avoid confusion about whether the position has been fully closed. Illustrative example: If you enter a liquidity pool position on January 15, 2024, and withdraw 50% of the position on March 22, 2024, and the remaining 50% on January 10, 2025, you will file a copy of the card with both your 2024 and 2025 tax returns, with partial exit indicators marked for each corresponding exit hash. All cross-referenced tax forms must include the 8/8 short entry hash in the “Description of Property” column on Form 8949 to directly link the reported gain or loss to the verifiable on-chain transaction record on the entry vs exit hash card. When submitting digital copies of the card as part of your tax filing package, name the file following the consistent convention: [Tax Year]_[First 8 of Entry Hash]_DeFi_Hash_Card.pdf to ensure uniform indexing across your digital record folder and enable fast retrieval if requested by tax authorities. Do not submit these entry vs exit hash cards directly to the IRS unless explicitly requested as part of an official audit inquiry; retain the original completed cards in your personal tax records for a minimum of 7 years from the date of the final exit transaction for the associated position, per federal record retention requirements for tax documents.
Transaction Matching Folder Sorting Rules
All completed entry vs exit hash cards must be sorted in your physical and digital filing systems first by the tax year of the final exit transaction for the associated position, then by the native chain token of the transaction (e.g. Ethereum, Solana, Polygon, Arbitrum), then by the date of the entry transaction in chronological order. Physical hard copies of the cards must be stored in waterproof, acid-free file folders labeled with the tax year and chain name, with tab dividers separating entry transactions by calendar quarter to speed up retrieval during audit or review. Digital copies of the cards must be stored in an end-to-end encrypted cloud folder or offline cold storage drive, with file names following the convention outlined in the cross-reference procedures section to enable keyword search and quick retrieval. All supporting records for each card (including chain explorer screenshots of the entry and exit transactions, wallet signature confirmations, cost basis calculation worksheets, and protocol fee receipts) must be stored in the same folder as the associated entry vs exit hash card, with the 8/8 short entry hash printed on the top right corner of each supporting document to link it to the correct card without opening the full file. The table below outlines the mandatory and optional fields for the standard entry vs exit hash card, with cross-reference links to corresponding folder locations for formal record retention:
| Field ID | Field Name | Data Format | Required (Y/N) | Folder Cross-Reference |
|---|---|---|---|---|
| 1 | Entry Hash | 66-character hexadecimal string | Y | Permanent DeFi Transaction Folder > Position Initiation Records |
| 2 | Exit Hash (Primary) | 66-character hexadecimal string | Y | Tax Year Filing Folder > Digital Asset Transaction Supporting Docs |
| 3 | Entry UTC Timestamp | ISO 8601 (YYYY-MM-DD HH:MM:SS) | Y | Chain Explorer Export Backup Folder |
| 4 | Exit UTC Timestamp | ISO 8601 (YYYY-MM-DD HH:MM:SS) | Y | Tax Year Filing Folder > Cost Basis Calculation Workpapers |
| 5 | Partial Exit Indicator | Checkbox + Numeric percentage of position closed | N (required only for partial exits) | Permanent DeFi Transaction Folder > Partial Position Records |
| 6 | Hash Discrepancy Note ID | 10-character alphanumeric reference ID | N (required only if a discrepancy is documented) | Discrepancy Resolution Folder > Audit Support Records |
Hash Discrepancy Note Submission Protocols
A hash discrepancy is defined as any instance where the entry hash cannot be matched to a confirmed, finalized on-chain transaction, the exit hash does not correspond to a transaction that interacts with the same protocol address listed for the entry transaction, the sum of assets exited across all listed exit hashes does not match the total assets entered minus any documented protocol fees or realized impermanent loss, or there is a mismatch between the timestamp listed on the card and the timestamp recorded on the public chain ledger. All identified discrepancies must be documented on a standard Hash Discrepancy Note form, which must be attached to the front of the associated entry vs exit hash card, both in physical and digital filing locations to ensure it is immediately visible to any reviewer. The discrepancy note must include the 8/8 short entry and exit hashes for reference, a clear, factual description of the discrepancy, supporting evidence including full chain explorer export records for both the entry and exit transactions, and a signed note from your licensed tax preparer documenting how the discrepancy was resolved for tax reporting purposes. If the discrepancy cannot be resolved before your tax filing deadline, include a copy of the unresolved discrepancy note with your tax filing documentation, and retain all related records in a separate Discrepancy Resolution folder for a minimum of 10 years from the date the discrepancy was first identified, as unresolved discrepancies may increase the risk of audit inquiry in future years. Do not alter, cross out, or write over pre-printed or previously entered hash values on the entry vs exit hash card; always note changes, corrections, or adjustments on the separate discrepancy note form to maintain a clear, unaltered audit trail of all modifications to the original transaction record.
Print a blank entry vs exit hash card using the field specifications outlined above and file it in your 2024 tax records folder the next time you initiate a new DeFi position to capture the entry hash immediately at transaction execution.