What happens between the post and the claim.
Drop codes go to whoever gets there first, and the pool is often empty within seconds. StakeClaime removes the part that costs you those seconds — seeing the message, copying the code, finding the field, pasting it. Here is the whole chain, step by step.
The chain
Four steps. Only one of them runs on our server.
-
01
You install it, once
Tampermonkey runs the script on the Stake tab you are already logged into. What it installs.
your browser
-
02
Stake posts a code
Codes are announced publicly, where anyone can read them. The channels that carry them.
Telegram
-
03
The relay forwards it
Our server watches those channels and pushes each new code to every connected script at once.
our server
-
04
Your browser claims it
The claim goes from your tab. The panel logs the result: claimed, skipped, pool full, or not eligible.
your browser
Your account is only ever touched by the two steps on your own machine.
Why the claim comes from your browser
StakeClaime never asks for your Stake login. It claims from the tab you already have open, so your account details stay on your computer.
Our server only sees the code and which channel it came from. Not your username, not your balance, not your login.
The permissions, in full, and the source on Greasy Fork to read before you install it.
What it never touches
- Your Stake password — never asked for, at any point.
- Your session cookie value — never read.
- Your balance or wallet — never sent anywhere.
- Any tab that is not Stake — the script declares the domains it may run on, and nothing else is in reach.
The claim log lives in your browser and stays there. We never see the amounts in it.
What decides whether a claim lands
Speed is the part StakeClaime can help with. These are the parts it cannot.
- Eligibility. Stake decides which accounts a drop applies to. If yours does not qualify, the claim fails and the log says so.
- How fast the pool empties. Some drops are fully claimed in under a second. Those are misses for everyone, including us.
- Stake’s daily cap. Ten claimed codes per 24 hours, resetting at 00:00 UTC. No plan raises it — a plan decides whether you are in time for the codes you are entitled to, not how many.
- A challenge on the page. If a captcha blocks the page, claiming stops until you clear it. The script cannot answer one for you.
- Your tab being open. Claims are submitted by your browser, so a closed browser claims nothing.
What you need
- A desktop browser with Tampermonkey. Userscript managers do not exist on Chrome for Android or default iOS Safari, so there is no phone version.
- A logged-in Stake tab, left open, on the site you use.
- For Telegram codes, a trial or a plan. Reload claiming is free and always has been.