I'm not a senior dev. I'm not building the next Uniswap. I just kept losing money because my airdrop tracking system was a spreadsheet that I never updated.
Third time I missed a confirmed drop I sat down and actually built something instead of complaining about it.
The core problem wasn't finding airdrops. There's a hundred sites for that. The problem was knowing what to do and when to do it on each one. Bridge here, swap there, provide liquidity, come back next week, lock tokens — and somehow remember all of that across 15 protocols simultaneously while holding a job.
So I built per-project checklists. Each airdrop has a task list — actual on-chain steps, not vague "interact with the protocol" advice. You check them off, progress saves. That's it. Stupidly simple but I haven't missed a snapshot since.
The interesting technical bit was the heat score system. I wanted something that surfaced time-sensitive drops automatically instead of me having to check everything manually. It factors in deadline proximity and community engagement velocity — when both spike at the same time something is usually about to close. Took a few iterations to get the weighting right but it works well enough that I check it every morning.
Stack is Next.js, which I'm starting to regret slightly because of bundle size issues I'm still sorting out. Covers 35+ chains now. Built the wallet points scanner last month — paste an address and it checks your balances across 50+ protocols at once, which turns out to be the feature people actually wanted most.
It's at jeetdrops.xyz if you want to poke around. Still a lot to build but it's been genuinely useful for me which I figure is a decent place to start.
Happy to talk through any of the technical decisions if anyone's curious. Some of them were good. Most of them were just whatever worked at 1am.
Top comments (0)