Keeping records for a farming year you will be taxed on
The problem with treating airdrops as free money
An airdrop claim is a transaction. It has a block timestamp, a transaction hash, a token contract address, and an amount that lands in a wallet you control. In most jurisdictions that already puts it on a tax authority’s radar as some kind of taxable event, whether that’s income at the time of receipt or a cost basis question when you eventually sell or swap. Which treatment applies to you depends on where you’re tax resident and how your local rules classify token receipts, and that’s a question for a qualified tax professional, not a blog post. What this article is about is the part you control regardless of jurisdiction: whether you can actually reconstruct, twelve months later, what happened in your wallets and when.
Anyone running a handful of wallets for a season or two can usually eyeball their history. Anyone running dozens of wallets across several protocols, each with claim events spread over months, cannot. If you’re treating this as an operation rather than a lottery ticket, record keeping is infrastructure, not paperwork you do in April.
What actually generates a taxable event
Every claim transaction is public. The block explorer for whatever chain you claimed on shows the exact block, the exact timestamp (in UTC, which matters when your local tax year runs on a different clock), the contract that emitted the tokens, and the wallet address that received them. That’s the raw material for any record. Nothing about it is private or reconstructable-only-by-you: if you lose your own notes, the chain still has the truth, but pulling it back out manually across fifty wallets and a dozen protocols is a miserable way to spend a weekend before a filing deadline.
The things that are not on-chain, and that you have to capture yourself at the time, are usually the things that matter most for a tax filing: what the token was worth in your local fiat currency at the moment you received it, and what it was worth when you later sold, swapped, or otherwise disposed of it. Valuation at time of receipt is the piece people lose. A wallet balance six months later tells you what the token is worth now. It tells you nothing about what it was worth on the day it landed, and by the time you go looking, the specific price feed you’d want may be harder to reconstruct with confidence.
Build the ledger at claim time, not at tax time
The operational fix is simple to describe and tedious to skip: log the event when it happens, not when you file. A row per claim, minimum fields being wallet address, chain, token contract, transaction hash, date and time, quantity received, and the fiat value you assigned at that moment using whatever price source you consider defensible for your filing. A spreadsheet does this fine. So does a lightweight database if you’re running enough wallets that a spreadsheet becomes its own management problem.
The transaction hash is the field people skip because it feels redundant, but it’s the one that lets you or an accountant verify any line later without trusting your own memory. If a tax authority ever asks “how do you know this happened,” the hash is the answer. Screenshots and manual notes degrade over time; a hash pointing at an immutable ledger doesn’t.
Separate farming wallets from wallets that do other things
If a wallet claims airdrops and also holds funds you use for unrelated trading or spending, your records for that wallet become a mixed pile that’s harder to untangle later. Keeping farming wallets operationally separate from personal or trading wallets isn’t about hiding anything. It’s the same reason a business keeps a separate bank account from a personal one: it makes the accounting tractable. When every transaction in a wallet’s history belongs to the farming operation, you can export that wallet’s full history and hand it to an accountant without first stripping out unrelated activity.
This also matters for how chain analysis firms and some airdrop programs cluster addresses. Wallets that share funding sources, transaction timing patterns, or downstream consolidation points get grouped by clustering heuristics regardless of your intent. That’s a separate operational concern from tax records, covered in more depth elsewhere on this site, but the same discipline that keeps your wallets legible to a clustering algorithm (clean, separated funding and behavior per wallet) also keeps them legible to you and to whoever does your books.
Costs are part of the record too
An airdrop isn’t free to farm. Gas fees on every claim and every interaction leading up to it are real costs. If you’re running an RPC subscription to avoid public endpoint rate limits, that’s a recurring cost. If you’re running proxies or cloud phones to keep wallet activity from a single IP or device fingerprint, that’s a cost too, and if you’re operating as a business rather than a hobbyist, these are exactly the kind of expenses that offset income depending on how your local rules treat them.
The mistake is capturing only the inbound side of the ledger, the tokens received, and ignoring the outbound side, the gas spent and services paid for to make the claims possible. A farming year’s real financial picture includes both. Keep invoices or statements for infrastructure spend (RPC plans, proxy or device rental, any tooling subscriptions) in the same place as your claim ledger, dated and matched to the period they cover, so the full cost of the operation is visible in one place rather than scattered across email receipts and exchange statements.
What to log for disposals, not just receipts
Receiving a token is one event. Selling it, swapping it, or bridging it to another chain is another, and each of those has its own timestamp and its own valuation question. If you claim a token in January and sell half of it in June, you need both the January receipt value and the June disposal value to know the actual gain or loss on that portion, and you need to track which units you sold if you’re not selling the whole position at once. This is where a lot of manual tracking falls apart, because it’s easy to log the exciting event (the claim) and forget the mundane one (the eventual sale) months later on a different wallet or a different exchange entirely.
The same rule applies here as at claim time: log the disposal transaction hash, the date, the quantity, and the value realized, at the time it happens. Don’t defer it. A farming operation running for a full year across many protocols will have disposal events spread unevenly across the calendar, and reconstructing them from memory in the following spring is a much worse task than logging each one as it happens.
Tools that help, used for what they actually do
Block explorers let you pull a wallet’s full transaction history and export it, which is useful for cross-checking your own ledger against the chain’s record rather than trusting your notes blindly. Some portfolio and airdrop trackers offer CSV or API export of claim history across multiple wallets, which can save time consolidating records if you’re running enough addresses that manual entry is a bottleneck. None of these tools produce a tax filing on their own, and none of them know your jurisdiction’s rules about how a claimed token should be valued or classified. They’re record aggregators, not accountants. Treat their output as a source you reconcile against your own ledger and your own transaction hashes, not as the final answer.
Get a professional who understands the asset class
Nothing here is tax advice, and it isn’t meant to substitute for a conversation with someone qualified to give it in your jurisdiction. What good record keeping does is make that conversation short instead of long. An accountant who understands crypto can turn a clean ledger of claim events, valuations, disposal events, and operating costs into a filing in an afternoon. The same accountant handed a pile of wallet addresses and a request to “figure out what happened this year” will either charge you for reconstruction work or tell you to go do it yourself first. Keeping the ledger live, one row per event, as the year happens, is the difference between those two outcomes.
If you’re building out a real airdrop operation and want the rest of the ops side, how wallets get clustered, what proxies and devices actually do for you, and honest reviews of the tools involved, there’s more of that on the home page.
Get new guides and videos first — join the Telegram channel.