TimeFarm Crypto Bot
An idle farming bot built around time, not clicks. Log in once a day, collect what's accumulated, set the next farming cycle — calm UX, minimal server load, tokenomics that scale.
The problem we were hired to solve.
Tap-to-earn alternatives demanded constant interaction, pushed addictive notifications, and exploded the database with one row per tap per user. Owners spent more on infra than they earned on tokenomics.
One daily check-in. Cron does the math. Redis answers the questions. Postgres barely notices. Players come back because the loop respects their time, not because the notification yelled at them.
Context
Tap-to-earn won the Telegram bot meta in early 2025 and immediately started burning out users — endless tap loops, addictive notifications, and database costs that scaled linearly with engagement. The owner wanted the opposite: a farming game where the reward is time, not finger fatigue, and where the server doesn't need to handle a real-time event for every user every second.
Approach
Node.js bot core on grammY plus a thin Telegram Mini App for the daily check-in. Reward calculation is a node-cron job — every cycle the worker writes one row per active wallet, no real-time interaction needed. Redis holds hot per-wallet state (current cycle, next claim time, accumulated yield) so the bot answers status checks without touching Postgres. Postgres only sees one write per cycle per user. TON Connect handles the wallet so claims hit-chain when the player asks for them, not before. The UI deliberately skips animation overload — one screen, one button, one timer.
How this project was actually made.
Every project leaves a paper trail. Figma comments, Notion specs, GitHub history, Vercel deploy logs, Telegram threads, first-week analytics. Numbers below are real and available on request under NDA.
◆ Screenshots of any artifact available on request. Confidential details redacted.
Key features
- ◆
- ◆
- ◆
- ◆
- ◆
Results
Stable under 120,000+ active farming wallets with one DB write per cycle per user. Average session is around 30 seconds — players log in, claim, set the next cycle, and leave. Server load stays flat as user count grows.
Tech stack
What the client said.
Asked for a Telegram farming game that didn't burn out users or our infra. Got an idle loop with cron-driven rewards, Redis hot state, and one DB write per user per cycle. Stable past a hundred thousand wallets without scaling pain. Sessions are thirty seconds — players come back because they want to, not because we nagged them.