I built a crypto airdrop tracker because I kept missing snapshots. Here's what I learned.
Source: Dev.to
Background
I’m not a senior developer and I’m not building the next Uniswap. I kept losing money because my airdrop tracking system was a spreadsheet that I never updated. After missing a confirmed drop for the third time, I decided to actually build something instead of just complaining.
The Core Problem
Finding airdrops isn’t hard—there are dozens of sites that list them. The real challenge is knowing what to do and when to do it for each project. Typical steps include:
- Bridging assets
- Swapping tokens
- Providing liquidity
- Returning later to lock tokens
Keeping track of all these actions across 15+ protocols while holding a full‑time job quickly became unmanageable.
Solution: Per‑Project Checklists
I created a checklist for each airdrop. Every checklist contains the exact on‑chain steps required, rather than vague advice like “interact with the protocol.”
- Check off tasks as you complete them.
- Progress is saved automatically.
The approach is intentionally simple, but it has prevented me from missing any snapshots since I started using it.
Heat Score System
The most interesting technical component is the heat score. It surfaces time‑sensitive drops automatically, so I don’t have to manually scan every project. The score is calculated from two factors:
- Deadline proximity – how soon the airdrop window closes.
- Community engagement velocity – spikes in activity and discussion.
When both metrics rise together, a drop is likely about to close. After a few iterations to fine‑tune the weighting, the system now provides reliable daily alerts.
Technical Stack
- Framework: Next.js (still working out some bundle‑size concerns).
- Chains supported: 35+ blockchain networks.
- Wallet scanner: Built last month; paste an address and it checks balances across 50+ protocols in one go. This turned out to be the feature users wanted most.
Deployment
The tracker is live at jeetdrops.xyz. It’s still a work in progress, but it has already proven genuinely useful for me.
Closing Thoughts
I’m happy to discuss any of the technical decisions—some turned out well, while others were just “whatever worked at 1 am.” Feel free to reach out if you’re curious about the implementation.