A paper record of the transactions you actually made: when, from which wallet, on which chain, and what the gas cost. This free printable wallet activity log gives you 12 transaction rows per page, a monthly recap for the 5-line summary, and a labels box where your wallet aliases live. The hash column takes the last 4 characters only, so the sheet is safe to leave on a desk. It organizes your own history. It predicts nothing about any airdrop and holds no price claims. If you farm several campaigns at once, the airdrop tracking spreadsheet printable covers the campaign side of the same habit.
How to use this page: print both pages at 100% scale (the site chrome drops out on paper). One row per transaction, filled in the moment it confirms: date, the alias you call that wallet, the chain, the last 4 characters of the tx hash, and the gas paid. At month end, complete the recap table, then print a fresh page 1. Keep the filled sheets private; they are your activity history.
Page 1 is the working log: 12 rows, one transaction each. Page 2 closes the month: a 5-row recap, the labels box where aliases and their jobs are written down once, and the three security reminders worth rereading before any transaction. The wallet column never takes anything secret; it takes the nickname you gave the wallet, like burner-2.
Matchbook Labs · printable · page 1 of 2
Wallet activity log — transactions
Period:
Tx hash column: LAST 4 characters only. Wallet column: the alias you gave the wallet (like "burner-2"). NEVER a seed phrase or private key.
| # | Date | Wallet alias | Chain | Tx hash (last 4) | Gas paid | Notes |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 | ||||||
| 4 | ||||||
| 5 | ||||||
| 6 | ||||||
| 7 | ||||||
| 8 | ||||||
| 9 | ||||||
| 10 | ||||||
| 11 | ||||||
| 12 |
One row per transaction, written when it confirms. Chain is whatever you call it in your own notes. Full sheets go in the folder; print page 1 again when 12 rows run out.
Matchbook Labs · printable · page 2 of 2
Monthly recap & wallet labels
Month:
| Week | Transactions | Gas paid | Wallets used | Review note |
|---|---|---|---|---|
| 1 | ||||
| 2 | ||||
| 3 | ||||
| 4 | ||||
| 5 |
Counts from page 1, copied over by hand at month end. "Review note" takes one line: what this month's activity was actually for.
ALIASES ONLY. NEVER a seed phrase, private key, or recovery words. A label box that holds a secret is a leak waiting for a photo.
1. Never share a seed phrase or private key. Support staff, admins, "verification" flows: no legitimate role ever asks for them. A message that asks is a scam, whatever name or logo it carries.
2. Verify URLs yourself. Type the address or open your own bookmark. Links in DMs and comments stay unclicked until you have checked where they lead.
3. Test with a small transaction first. A new address, bridge, or wallet gets a small test send before anything larger moves. The test costs minutes; the alternative can cost the balance.
This log organizes your own records. It holds no price claims, predicts no airdrop, and guarantees nothing: projects set their own criteria and change them.
This is personal record-keeping, not financial advice. Nothing on it predicts any airdrop, token price, or project plan, and nothing here tells you what to buy, sell, or hold; the sheet exists so your own past actions are checkable when a project publishes its criteria. No reward is promised by writing rows: most activity across most seasons earns nothing, and a log that proves history is still worth more than a memory that argues with itself.
Paper covers one month at a time. Past that, the same discipline moves into a spreadsheet built for longer runs. Verbatim from the Airdrop Hunter Tracker README:
A working system for airdrop farming: a 230-row tracker spreadsheet (import-ready for Google Sheets and Excel) plus a short playbook that turns farming into a capped 15-minute daily routine.
This is not a list of airdrop predictions. It's the operating system around them: track what you did, when, on which chain, and what it cost you — so when a project announces eligibility criteria, you can check your own history in minutes instead of guessing.
What's inside
- tracker.csv — 9 columns (project, category, chain, status, date started, last check, est. effort, est. value, notes), 30 sample rows showing common task patterns (L2 testnet activity, points seasons, faucet rotation, quest campaigns), and 200 blank rows ready to fill. Samples are labeled SAMPLE - and generic on purpose: no claims about any project's unconfirmed airdrop.
- playbook.md — one-sheet-per-quarter setup, the daily 15-minute cadence, a weekly 10-minute review, and the checklist that applies to almost everything: wallet hygiene, burner email per campaign, date-stamped activity log.
Honest limits
- No guarantee of any airdrop, ever. Projects set their own criteria and change them.
- Sample rows are generic task patterns, not signals about real projects.
- The spreadsheet tracks effort. It can't create allocations.
Personal + commercial use allowed. No resale or redistribution of the file set as-is. Provided as-is, no warranty.
Quoted verbatim from the Airdrop Hunter Tracker product README.
Get the Airdrop Hunter Tracker - 230-row spreadsheet + playbook →one-time · CSV + playbook · instant download · personal + commercial use · or browse the catalog