GDrop Bot is a full automation bot for the GDrop Telegram Miniapp.
It handles the complete daily cycle: completing all available tasks, watching earn ads on Adsgram and Monetag until each network hits its daily cap, claiming the daily bonus via an ad-verified flow, resolving any pending game reward, and playing all four mini-games (Catch, Merge, Flappy, Whack) with automatic ad verification per round to claim GD rewards, all running automatically across multiple accounts with proxy support and a live countdown between cycles.
Built and distributed by Yuurisandesu.
- Python
3.10+ - Git
Clone the repository:
git clone https://github.com/Yuurisan-N1/GDrop-Miniapp.git
cd GDrop-MiniappInstall dependencies:
pip install aiohttp coloramaFill data.txt with Telegram WebApp initData for each account, one per line:
user=%7B%22id%22...&hash=abc123
user=%7B%22id%22...&hash=def456
initDatacan be obtained from the browser DevTools when opening GDrop on Telegram Web.
Fill proxy.txt with proxies, one per line (optional, leave empty to run without proxy):
host:port
host:port:user:pass
http://user:pass@host:port
Proxies are assigned to accounts by index in round-robin order.
sleep_seconds controls how many seconds the bot waits between cycles. If config.json is missing, the bot falls back to a default of 3600 seconds.
python bot.pyPress Ctrl+C at any time to stop the bot cleanly.
The bot filters all tasks with status idle and processes each one. It sends a start request, waits the server-specified verify duration plus 1 second, sends a verify request to confirm, then claims the reward. Each claimed task logs its title, GD reward, and new balance.
The bot checks the Adsgram and Monetag ad counters and calculates how many slots remain under each network's daily cap. It then watches each remaining ad slot in sequence: starting the ad, waiting the server-specified minimum watch time plus cooldown, then completing it. Progress is logged per slot per network.
The bot checks whether the daily bonus has been claimed. If not, it runs a full ad cycle for the bonus purpose, then claims the bonus reward with the resulting nonce. The GD reward and new balance are logged.
Before starting any games, the bot checks if there is a pending unclaimed game reward from a previous session. If so, it resolves it first by running a 30-second ad countdown, getting a game ad nonce, and claiming the pending reward. This prevents reward loss from interrupted sessions.
The bot plays all four mini-games in order: Catch, Merge, Flappy, and Whack. For each game, it processes all remaining plays for that game. Each play sends a start request, waits 5 seconds, sends a finish request with a fixed score per game type, then claims the reward via a full ad cycle. The ad cycle runs a 30-second countdown followed by a game ad start and complete. Each round logs the game name, round number, GD reward, and new balance.
Each account session uses a freshly generated 25-character random alphanumeric device ID sent as a request header, making each session appear as a unique device.
All accounts in data.txt are processed sequentially within every cycle. Balance, daily bonus status, ad counters, and remaining plays per game are fetched and logged at the start of each account.
Proxies are loaded from proxy.txt and assigned to accounts by position in round-robin order. Proxy credentials are masked in log output. Running without proxies is fully supported.
After all accounts complete a cycle, the bot displays a live HH:MM:SS countdown until the next cycle starts.
GDrop-Miniapp/
├── bot.py # Main bot, full daily cycle automation
├── config.json # Sleep duration between cycles
├── data.txt # Account initData, one per line
├── proxy.txt # Proxy list, one per line (optional)
├── LICENSE # Apache 2.0
└── utils/
└── banner.py # Banner display on startup
This tool is built for educational and technical exploration purposes. Use it wisely and at your own responsibility.