Play-to-earn tax record-keeping, in plain language: what to log, when, and why
Educational content only — not tax or financial advice. Tax rules differ by country and change over time, and this guide is about the record-keeping habit, not about how any specific player should file. The examples below lean on the U.S. Internal Revenue Service's published digital-asset guidance because it spells out the record fields clearly; the logging habit itself is useful almost anywhere. For a filing decision, a qualified tax professional in your own jurisdiction is the right call.
Most play-to-earn tax stress is not really a tax problem. It is a record-keeping problem discovered too late — usually in filing season, when a player is trying to reconstruct a year of small rewards, swaps, and sales from a wallet history and a game that may no longer exist. The fix is unglamorous: log each event when it happens, with the handful of fields tax authorities actually ask for. This guide explains which events matter, what each record needs, and a short weekly routine that keeps the log complete without turning play into bookkeeping.
Why games make this harder than trading does
A trader on one exchange gets a tidy statement. A player earns across games, wallets, guilds, and marketplaces, often in tokens that are claimed in small amounts many times a week. Yet the underlying tax treatment is the same framework used for other digital assets. In the U.S., the IRS treats digital assets — cryptocurrencies and NFTs included — as property, not currency, and income from digital assets is taxable. Players with digital-asset transactions must report them whether or not the transactions produced a gain or a loss. That means the small stuff counts: a reward claim, a token swap, an NFT sale, and a cash-out are all events a return may need, and none of them reconstruct themselves after the fact.
There is a second complication. Broker reporting is filling in part of the picture for exchange users — U.S. brokers must report gross proceeds on Form 1099-DA for transactions from January 1, 2025, with basis reporting on certain transactions following from January 1, 2026 — but those rules do not cover decentralized or non-custodial brokers that never take possession of the assets. In plain terms: activity that happens inside a game, in a self-custody wallet, or on a decentralized platform may never arrive on a tidy form. The player's own log is the record.
The two moments every reward creates
The single idea that makes P2E taxes click is that one reward drop creates two separate moments, and each needs its own record.
Moment one is receipt. When tokens or an NFT arrive as earnings, record the date and time, what arrived, how much, and its fair market value in your local currency at that moment. Record-keeping guidance for crypto rewards is consistent on this point: the timestamp matters because it determines the fair market value used for income reporting, and it starts the holding-period clock. If an asset is locked or unusable at first, note when it became usable as well as when it arrived — the IRS's airdrop guidance, for example, ties receipt to the point where the holder has dominion and control over the asset. The value at receipt also becomes the asset's basis: what it was "worth" when it became yours, against which any later gain or loss is measured.
Moment two is disposal. Selling the tokens, swapping them for another asset, spending them on an in-game item, or cashing out to a bank account are all disposals. Record the date and time, what left, how much, the fair market value at that moment, and any fees. The difference between the disposal value and the basis from moment one is the gain or loss. This is also where holding period matters: under the IRS framework, a gain on an asset held one year or less is short-term, and more than one year is long-term — one more reason the receipt date cannot be guessed later.
The five events to log, compared
Almost everything a player does falls into five event types. Logging them separately — instead of letting a wallet export lump everything together as "transfer" — is what makes a year-end summary possible.
| Event | Examples in play | Fields to capture |
|---|---|---|
| Receipt (earnings) | Reward claims, tournament prizes, airdrops, a guild split paid to you | Date/time, asset, amount, fair market value at receipt, source wallet or game, note on what it was for |
| Purchase | Buying tokens or an NFT with money or another asset | Date/time, asset, amount, what you paid including fees, where |
| Swap or spend | Trading one token for another, buying an in-game item with earned tokens | Date/time, what left and what arrived, fair market value of both sides, fees |
| Sale or cash-out | Selling tokens or an NFT, withdrawing to a bank account | Date/time, asset, amount, proceeds, fees, basis of the units sold |
| Self-transfer | Moving your own assets between your own wallets or a game account | Date/time, from and to addresses, amount, transaction hash, a note that it was your own wallet |
A strong record, in general crypto tax guidance, carries the same core fields across all of these: date, asset, quantity, transaction type, purchase and disposal values, fees, wallet address, platform name, transaction hash, and the reason for the transaction. The reason field sounds like overkill until a reviewer — or future you — is staring at an unexplained transfer. A one-line note such as "season reward claim" or "moved to cold wallet" settles it. For unusual events — airdrops, protocol migrations, a hack, a game shutdown — keep a screenshot or statement as well; they are exactly the events that are hardest to document later.
The weekly record-keeping routine
Ten minutes a week beats ten hours in filing season. This procedure assumes a simple spreadsheet or a notes file; dedicated tax software can import the same information, but software is an aid, not a substitute — imported data can be wrong when basis is missing, transfers are unmatched, or a chain is unsupported.
- Export, don't screenshot-and-pray. Once a week, export transaction history from each exchange, wallet, and marketplace used that week, and save the files with the date in the filename. Exports come first because access is perishable: platforms shut down, change their report formats, block accounts, and lose older data.
- Log the week's game events. Add a row for each receipt, purchase, swap, sale, and self-transfer, using the fields in the table above. Note which wallet received each reward — source-wallet clarity is what makes later reconciliation possible.
- Stamp the values at the time. Record the fair market value in your local currency as of each event, and note where the value came from. For on-chain receipts, a blockchain explorer's value at the exact date and time is evidence the IRS says it accepts for fair market value.
- Flag the odd ones. Mark airdrops, locked rewards, guild splits, and anything connected to a game announcing a shutdown, and save a screenshot or statement alongside the row.
- Back the log up off the game. Keep the spreadsheet and exports in ordinary cloud or local backup — anywhere that survives the game, the marketplace, and the wallet app all disappearing.
- Do a monthly five-minute reconciliation. Pick a few rows at random and check them against the wallet history and the saved exports. Disposal rows should show both the proceeds and the basis of what was sold; if basis is missing, fix it now, while the receipt record is findable.
What success looks like
The routine is working when three things are true at any point in the year. First, every token and NFT you hold can be traced to a receipt or purchase row with a date and a value — nothing is "just there." Second, every sale or cash-out row names the basis it is measured against, so a gain or loss can be computed without detective work. Third, the whole log lives somewhere that does not depend on any game or platform still existing — because, as the shutdown guide on this site covers, games ending is a normal event in this ecosystem, and tax records have to outlive them.
FAQ
Do tiny rewards really need logging? The IRS position is that digital-asset transactions must be reported whether or not they result in a gain or loss, and rewards are receipts with a fair market value at the time. Logging them as they arrive is what makes that reporting possible at all; whether small amounts change a particular player's bill is a question for their own jurisdiction's rules and, if needed, a tax professional.
Is moving tokens between my own wallets a taxable event to log? Log it either way. A self-transfer is generally a bookkeeping event rather than a sale, but an unexplained gap between wallets is how records fall apart — and paying a transfer fee in crypto can itself be a transaction. The log row with both addresses and a one-line note is what proves the two ends are the same owner.
What if a game already shut down and took my history with it? Reconstruct what you can from wallet history and block explorers — on-chain receipts and disposals carry dates, amounts, and transaction hashes even when the game's own interface is gone — and keep the exports you do have. A partial, honest record built from chain data is far better than a blank one, and it is the reason the weekly export step exists.