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 airdrop unit and date card logs crypto airdrop allocations and their earliest permitted transfer dates. It is designed to populate your cryptocurrency tax records folder for easy reference during annual filing, audit response, or cost-basis calculation workflows. All entries should be cross-referenced with on-chain transaction receipts, project announcement correspondence, and wallet access records to avoid discrepancies. You may store a printed copy alongside digital files in your Field Ledger folder for offline backup, if desired.
Claimed airdrop unit count box
This standardized, scannable box sits on the top right of each airdrop unit and date card, reserved for the exact number of whole and fractional airdrop units you received and claimed on-chain. Do not include unclaimed units here, only those associated with your wallet address as of the official claim block height. The box is formatted to accept both numeric entries and scannable QR codes that link directly to the on-chain claim transaction, if you prefer to store digital references directly on the card. Fractional units should be listed to the same decimal precision specified in the airdrop project’s smart contract, to avoid rounding errors that could create discrepancies between your records and on-chain data. If you received allocations across multiple wallets, each wallet gets its own separate card, no combining counts across addresses here. If you received airdrop units that are subject to vesting, only list the number of units that have vested and been claimed as of the date you fill out the card, with a separate addendum for future vested units when they are released. Avoid rounding up or down fractional units when entering the count, as even small discrepancies can lead to mismatches with third-party tax reporting forms that may be issued by centralized exchanges if you later transfer or sell the airdrop units. If you claimed the airdrop via a custodial platform, the count listed here should match the number of units reflected in your custodial account statement for the claim date, to ensure alignment across all your records.

Eligible transfer date reference column
This column runs down the left third of the card, organized by block height and corresponding UTC date. The date listed is the first day the project’s smart contract allows self-custody or exchange transfer of the airdrop units, not the date you chose to transfer them. Each entry in this column should be paired with the exact block height at which the lockup period ends, so you can cross-reference with block explorer data if the UTC date is ambiguous due to time zone differences. For example, if a lockup ends at block 17,000,000 on Ethereum, you would list both that block number and the UTC date and time that block was mined, to eliminate any confusion about when transfer eligibility began. You should not use the date the airdrop was announced, the date you claimed the airdrop, or the date the tokens appeared in your wallet as the eligible transfer date, unless those dates align exactly with the end of the mandatory lockup period. If the project amended lockup terms after the airdrop announcement, you should log the original and revised dates here, with a cross-reference to the official amendment communication stored in your crypto tax records folder. If the project did not publish a formal lockup period, but imposed a temporary transfer restriction to prevent bot activity immediately after the airdrop, the end date of that temporary restriction is the eligible transfer date you should list here, not the date the airdrop was distributed. You can confirm the end of any temporary restrictions by attempting a small test transfer of less than 0.001 units to a secondary wallet you control, and logging the date and transaction ID of that successful test in the lockup period end verification note.
Lockup period end verification note
This is a 2-line free text field directly below the claimed unit count box, reserved for confirmation that the listed eligible transfer date matches the end of the mandatory lockup period specified in the airdrop’s terms of service. You should add the wallet address associated with the airdrop here, along with the transaction ID of the first successful transfer you initiated on or after the eligible date, if applicable. If you did not transfer the units immediately, you can note the date you first verified transfer eligibility via a test transaction of 0.0001 units if you performed that check. This note should be signed and dated by the wallet holder or the authorized tax preparer who verified the lockup end date, to create a clear audit trail of who confirmed the entry. If you use a third-party tax tool to pull airdrop data, you should include the name of the tool and the date you pulled the data in this note, as an additional cross-reference. If the airdrop has no mandatory lockup period, you can note “No lockup, eligible immediately upon claim” in this field, paired with the date you claimed the airdrop as the eligible transfer date. If you are filling out this card as part of a business or entity tax record, the note should be signed by the authorized signatory for the entity that holds the wallet, not an individual employee, to ensure the entry is legally valid for audit purposes. You may also attach a printed screenshot of the block explorer page showing the end of the lockup period to the back of the card, for quick reference without needing to access digital records.
Unclaimed airdrop unit ledger folder
This separate physical or digital folder is stored alongside your completed airdrop unit and date cards, to track airdrops you were eligible for but did not claim, either because the claim window expired, you chose not to participate, or you did not meet post-eligibility requirements. Entries here do not get added to your claimed unit count, but are retained for record keeping in the event of audit inquiries about unreported income or unclaimed assets. You should include a copy of the eligibility notice you received, the claim window end date, and a short note explaining why the airdrop was unclaimed, for each entry in this folder. You do not need to complete a full airdrop unit and date card for unclaimed airdrops, but you should retain enough documentation to prove that you never took possession of the units, in the event that a tax authority sends an inquiry about reported airdrop allocations associated with your wallet address. You may group unclaimed airdrop records by calendar year, to align with your annual tax filing schedule, and you can discard records after the applicable statute of limitations for tax audits in your jurisdiction has passed, per guidance from your licensed tax professional. If you receive an eligibility notice for an airdrop that you do not intend to claim, you should add a copy of that notice to this folder within 30 days of receipt, to avoid forgetting the details of the unclaimed airdrop later. You do not need to track unclaimed airdrops that you never received an eligibility notice for, as there will be no on-chain record of an allocation associated with your wallet address in those cases.

Transfer eligibility confirmation record form
This form is the core of the airdrop unit and date card, designed to be printed or filled digitally for each airdrop you receive. Each row of the form corresponds to one unique airdrop and wallet address combination, so you will add a new row each time you claim an airdrop to a new wallet. The cross-reference file ID corresponds to the naming convention you use for your crypto tax records folder, so you can quickly pull supporting documents if requested by a tax preparer or auditor. The verification checkbox should only be marked once you have completed all cross-references: confirmed the unit count matches on-chain data, confirmed the eligible transfer date matches the project’s terms and block explorer data, and stored all supporting documents in your crypto tax records folder. You may attach additional rows to the form if you have more airdrops than fit on the standard template, as long as each row includes all required fields. This page is for educational purposes only, it cannot file a tax return on your behalf, and you should consult a licensed tax professional for guidance specific to your jurisdiction and tax situation.
| Airdrop Project Identifier | Associated Wallet Address | Claimed Unit Count | Eligible Transfer Date (UTC) | Lockup Period End Verification Checkbox | Cross-Reference File ID |
|---|---|---|---|---|---|
| Illustrative example: ChainXYZ Governance Token | 0x1a2b3c4d5e6f7g8h9i0j | 127.42 | 2023-04-17 | [X] | CTXZ-2023-0417-001 |
| Illustrative example: DeFi Protocol Yield Token | 0xk9j8h7g6f5e4d3c2b1a0 | 3.891 | 2022-11-02 | [X] | DPYT-2022-1102-007 |
| Illustrative example: Layer 2 Utility Token | 0x0z1y2x3w4v5u6t7s8r9q | 412.0 | 2024-01-29 | [ ] | L2UT-2024-0129-003 |
| Illustrative example: Public Goods DAO Token | 0xq9p8o7n6m5l4k3j2i1h0 | 56.114 | 2023-09-22 | [X] | PGDT-2023-0922-012 |
Pull your most recently claimed airdrop’s on-chain claim receipt and official project lockup terms, and fill out the first row of your transfer eligibility confirmation record form today.