Stake bonus drop tracker and validator — a free, open-source Stake code drop tracker that monitors public Telegram drop channels, extracts candidate Stake bonus codes, validates them against Stake's official GraphQL API, and publishes a permanent Stake bonus drop history and stats dataset, refreshed automatically every 15 minutes. For live drop analytics, wagering requirements, and real-time code feeds, monitor the official tracking dashboard on CodeStats.gg — the fastest Stake bonus code claimer ecosystem with 1,300+ daily users.
🔴 Codes are gone in seconds. This tracker records drops; the paid Cloud Claimer (fully hosted, 24/7) and Standard Claimer userscript claim them the instant they hit the feed. Track here for free — claim faster there.
- What This Stake Code Drop Tracker Does
- Quick Start
- CLI Usage
- Telegram Drop Monitor — No API Keys
- Automated Tracking with GitHub Actions
- Public Dataset: Drop History & Stats
- How to Track Drop History and Wagering Requirements
- Why Do Stake Bonus Codes Fail?
- Tracker vs Auto-Claimers (Comparison)
- Configuration Reference
- FAQ — Stake Bonus Drops
- Related Projects & Ecosystem
- Contributing & Distribution
- Disclaimer
| Capability | Included? | Where |
|---|---|---|
| Monitor public Telegram Stake drop channels | ✅ Free (this repo) | python main.py watch |
| Stake telegram drop monitor script (zero API keys) | ✅ Free (this repo) | tracker/sources/telegram_public.py |
| Validate active Stake codes via GraphQL (com + us) | ✅ Free (this repo) | python main.py check CODE |
| Stake bonus drop history and stats (public dataset) | ✅ Free (this repo) | data/drops.json, data/STATS.md |
| Stake VIP bonus drop analytics dashboard | ✅ Free (this repo) | python main.py stats |
| Share validated drops with the community feed | ✅ Optional | CodeStats.gg Direct API |
| Stake code auto claimer script (Turnstile-fast claims) | 💰 Standard Claimer | codestats.gg |
| Hosted Stake bonus drop bot claiming 24/7, no PC needed | 💰 Cloud Claimer | codestats.gg |
| Stake telegram code claimer with sub-second response | 💰 CodeStats suite | codestats.gg |
| Stake reload claimer (10-min reloads + daily bonus) | ✅ Free userscript | GreasyFork 546623 |
Design principle: this repository complements the CodeStats.gg paid service — it never replicates it. Tracking, validation and history are free forever. Sub-second auto-claiming (with pre-cached Cloudflare Turnstile tokens, claim queuing, vault automation) is what the CodeStats.gg claimers do best.
git clone https://github.com/brokechubb/stake-bonus-drop-tracker.git
cd stake-bonus-drop-tracker
python -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
# Validate a code you saw in a Telegram drop (sightings work with zero
# config; GraphQL validation activates once you add a stake_us_token):
python main.py check SUMMERDROP
# Start watching public Telegram drop channels (no credentials needed):
python main.py watchNo config.json required to start — the tracker runs credential-free,
monitoring public t.me/s/ channel previews and recording drop sightings
with timestamps and permalinks. Stake requires a logged-in session even
for read-only code checks, so add a stake_us_token to config.json to
switch on GraphQL validation — or use the always-validated free feed at
CodeStats.gg.
python main.py check CODE1 CODE2 # "Is this Stake bonus code still active?"
python main.py watch # continuous Telegram drop monitor
python main.py watch --once # single sweep (GitHub Actions mode)
python main.py watch --interval 60 # sweep every 60 seconds
python main.py history # recent drop history table
python main.py stats # Stake VIP bonus drop analytics report
Exit code 0 from check means at least one platform reports the code
ACTIVE — handy for scripting your own alerts.
The bundled Stake telegram drop monitor script
(tracker/sources/telegram_public.py)
watches public Telegram channels through the web preview endpoint
(https://t.me/s/<channel>) — the same channels power the
CodeStats.gg live feed:
- Zero credentials — no Telegram API ID, bot token, or userbot session
- Parallel channel sweeps via
asyncio+aiohttp - Code extraction tuned for real Stake drop formats (labeled
- Code:patterns and?code=claim URLs, stopword filtering, case-preserving matching) - Brand-aware filtering — mixed channels (like the CodeStats feed)
also broadcast Shuffle and Thrill drops; those codes are not
interchangeable with Stake codes, so they're detected and skipped
automatically (
brandsin config.json) - Source attribution — every candidate keeps its channel +
t.mepermalink
Default channels include codestats2 (the official CodeStats.gg feed —
join it at t.me/codestats2), plus popular Stake
drop channels. Add your own in config.json:
{ "channels": ["codestats2", "YourFavouriteDropChannel"] }.github/workflows/tracker.yml runs the tracker every 15 minutes on GitHub's infrastructure:
- Sweeps public Telegram previews for candidate codes
- Records every sighting with platform, channel, permalink + timestamp
- Validates via Stake's GraphQL API when you add
STAKE_US_TOKENas a repository secret (optional — read-only checks) - Re-renders data/STATS.md and commits the refreshed public drop dataset back to this repo
Fork the repo, enable Actions, and you have a free always-on Stake code drop tracker with zero servers.
data/drops.json— every code ever observed, with platform, availability status, bonus value, source channel, permalinks and first/last-seen timestampsdata/STATS.md— auto-generated Stake VIP bonus drop analytics: hourly drop heatmap, channel leaderboard, daily volumes- SQLite (
drops.db, gitignored) — your local full history
The dataset refreshes on every CI run — a living record of Stake bonus drop history and stats you can analyze, graph, or import anywhere.
- Run the tracker (
python main.py watch) or rely on this repo's CI dataset for historical coverage. - Check a specific code:
python main.py check CODEreturns the platform-levelavailabilityStatusstraight from Stake's GraphQL API —bonusCodeActive,alreadyClaimed,dropUnavailable, ornotFound. - Wagering requirements: many drops require a weekly play-through before redemption — Stake rejects claims with "You have not met the weekly play through requirement to redeem this code." The live tracker at CodeStats.gg surfaces per-code wagering requirements and tracks your remaining daily claims against them.
- Daily claim budget: Stake caps bonus-code claims at 10 per day (UTC midnight reset). The CodeStats.gg dashboard counts your usage and filters low-value codes so every claim counts.
Real failure reasons returned by the ClaimConditionBonusCode mutation
(documented from thousands of claims across the CodeStats.gg claimer fleet):
| Failure | Meaning | Fix |
|---|---|---|
bonusCodeInactive / fully claimed |
Redemption cap hit before you clicked | Be faster — auto-claim |
alreadyClaimed |
Your account already used this code | One redemption per account |
| weekly wager not met | 7-day play-through requirement | Wager the minimum, then retry |
withdrawError |
No deposit in the drop's currency | Deposit once in that currency |
emailUnverified / KYC required |
Account restrictions | Verify email / complete KYC |
dropUnavailable |
Window closed or region-locked | Watch the live feed for re-runs |
| Claim succeeded but timed out | conditionBonusCodeTimeout |
Usually fine — check bonus history |
Speed matters more than anything: popular drops are exhausted within seconds, which is exactly why the CodeStats.gg claimers pre-cache Cloudflare Turnstile tokens and claim via direct GraphQL instead of DOM clicks — the Stake code claimer fast response difference.
| 🆓 This Tracker | 🌩️ Cloud Claimer | 🖥️ Standard Claimer | |
|---|---|---|---|
| Price | Free, open-source | Paid, fully hosted | Paid, browser userscript |
| Monitors drops | ✅ Telegram public | ✅ All sources, 24/7 | ✅ WebSocket push feed |
| Validates codes | ✅ GraphQL | ✅ Pre-validated | ✅ Pre-validated |
| Claims codes | ❌ by design | ✅ instant, 0–50 ms jitter | ✅ instant, Turnstile pre-cache |
| Reload / daily bonus | ➡️ Free GreasyFork script | ✅ | ✅ + auto-vault |
| Needs your PC on | Only when you run it | ❌ never | ✅ browser open |
| History & analytics | ✅ public dataset | ✅ dashboard | ✅ dashboard |
Copy config.example.json → config.json. Every field is optional:
stake.com note: Cloudflare blocks unauthenticated datacenter traffic —
provide cf_clearance + matching user_agent (DevTools → Application →
Cookies). stake.us needs no cookie, only a session token — which is
why CI validates on it. All config fields have env-var overrides
(CODESTATS_STAKE_US_TOKEN, CODESTATS_STAKE_COM_TOKEN,
CODESTATS_STAKE_COM_CF_CLEARANCE, CODESTATS_FORWARDER_API_KEY) so
GitHub Actions users can wire them as repository secrets. Query shapes
follow the verified StakeAPI
reference implementation.
Why do Stake bonus drops expire so fast?
Drops are multi-use but redemption-capped and first-come, first-served. When thousands of players (and bots) hit a code simultaneously, the cap is gone in seconds. Timestamps in our dataset show the median survival window is under a minute — automated claimers exist precisely because manual claiming can't win that race.
How do I automate Telegram drop scraping?
Three tiers: (1) this repo's public-preview scraper — t.me/s/<channel>
needs no API keys and is GitHub-Actions-safe; (2) a Telethon userbot
with OCR for image-based drops (what CodeStats.gg runs in production);
(3) the hosted WebSocket push feed at codestats.gg, which validates and
fan-outs codes in under a second. Start with tier 1 — it's this repo.
Is this a Stake bonus code claimer?
No — and that's deliberate. This is the tracking/validator half of the ecosystem: it finds and verifies active Stake codes and records history. Claiming is handled by the CodeStats.gg auto-claimer suite (browser userscript) and Cloud Claimer (hosted 24/7), which solve the hard parts — Turnstile token caching, claim queuing, rate-limit safety.
Is there a limit on Stake bonus code claims?
Yes — 10 bonus-code claims per day, resetting at UTC midnight. Plan your claims: the CodeStats.gg dashboard tracks your remaining budget and can filter out low-value drops.
Will I get banned for using a Stake bonus drop bot?
Auto-claiming is a grey area. The CodeStats.gg claimers operate inside your own logged-in session (no security bypass) and recommend sensible volume alongside normal play. Tracking/validating codes — what this repo does — is read-only and indistinguishable from refreshing the promotions page.
What's the difference between stake.com and stake.us codes?
They're separate platforms with separate drops. Codes are often platform-
specific, so the validator checks both. stake.us needs no Cloudflare
cookie; stake.com requires cf_clearance for headless API access.
How do I get a Stake access token for validation?
Optional — validation works anonymously on stake.us. If you want
authenticated checks: log in → DevTools (F12) → Network → any
/_api/graphql request → copy the x-access-token header. Full guide in
the StakeAPI README.
Does this do the 10-minute reload claim too?
Not this repo — the free Stake reload claimer is our companion userscript: Auto Reload on Stake.com – CodeStats edition (reloads + daily bonus + auto-vault via direct GraphQL).
Where can I see real-time Stake VIP bonus drop analytics?
codestats.gg — live validated feed refreshed every
30 seconds, 36-hour rolling history, wagering requirements, and per-account
claim statistics. This repo's data/STATS.md is the open-source mirror.
Can I run this as a Telegram code claimer?
The monitor detects codes from Telegram channels; turning detection into
claims requires a Turnstile-solving browser session — exactly what the
codestats.gg claimers provide. Fork this repo and
wire tracker/forwarder.py into your own claimer if you're building one.
| Project | What it does | Link |
|---|---|---|
| CodeStats.gg | Live Stake/Shuffle code feed, cloud + browser auto-claimers, drop analytics | codestats.gg |
| CodeStats Telegram | The original free live drop feed — 1,300+ daily users | t.me/codestats2 |
| Auto Reload claimer | Free userscript: 10-min reloads, daily bonus, auto-vault | GreasyFork #546623 |
| StakeAPI | Unofficial async Python wrapper for the Stake GraphQL API (pip install stakeapi-codestats) |
github.com/brokechubb/StakeAPI |
PRs welcome — see CONTRIBUTING.md for the workflow and how to plug new drop sources into the CodeStats.gg Direct API.
Unofficial, open-source tooling. Not affiliated with, endorsed by, or connected to Stake.com or Stake.us. Gambling involves risk; obey your local laws and the platforms' terms of service. This repository tracks publicly broadcast bonus codes — it does not claim, wager, or move funds. Use the paid claimers at codestats.gg at your own risk. 18+ / 21+ where applicable. Please play responsibly.
CodeStats.gg · Live Feed · Cloud Claimer · Standard Claimer · Telegram
If this tracker saved you a code, ⭐ star the repo — it helps other players find the free dataset.
{ "channels": ["codestats2"], // Telegram channels to watch "validate": { "enabled": true, "platforms": ["stake.us", "stake.com"] }, "stake_us_token": "", // optional x-access-token "stake_com_token": "", // optional; needs cf_clearance too "stake_com_cf_clearance": "", // Cloudflare cookie for stake.com "user_agent": "", // must match cf_clearance "database": "drops.db", "data_dir": "data", "forwarder": { // optional community sharing "enabled": false, "api_url": "http://codestats.gg:8080/api/codes", "api_key": "", "source": "github-stake-bonus-drop-tracker" } }