ALPHA SNIPERText, however long
A thousand-word call with the CA buried at the bottom reads the same as a bare address.
Robinhood Chain · chain id 4663
Your alpha groups post a contract.
Your alpha groups post a contract.
The bot already bought it.
It listens to the Telegram groups and channels your own account is already in, pulls the contract address out of whatever shape it arrives in, prices it against the chain, and buys — before you have finished reading the message.
50ms
scan
385ms
post → on-chain
100ms
block time
Measured on a private Robinhood Chain node, on the trade shown here.
SNIPER-01
booting…
live
Detection
A contract address hides in more places than people think
Every one of these is read on arrival. The address is rarely sitting in plain text.
Links behind words
“ape here” pointing at a chart URL gives up the address inside it.
Link previews
When the message body says nothing, the preview title and description usually do.
Posts, in full
The linked post is fetched and read past Telegram's truncation — no X API needed.
Pair and pool links
A dexscreener pair or a v4 pool id is resolved on-chain back to the token behind it.
Buy-bot keyboards
Inline button URLs carry the CA as often as the message does.
Where it wins
The edge is not speed alone. It is being there at all
The calls that move are posted in rooms you cannot watch all day, at hours you are not awake for. The bot is in those rooms the whole time, and it does not get bored.
The small groups where the runners actually start
Ten-person chats, paid groups, friends-of-the-dev rooms: the ones where a token is posted before it is anywhere else. Because the bot listens through your own account, anything you can read, it can read — invite-only rooms included. Nothing needs to be added to the group, and nobody in it can tell.
One caller in a loud room
A good caller in a group of four hundred people is a needle in a haystack of noise. Restrict a group to the two or three members whose calls you actually take, and everyone else is ignored — no alerts, no buys. Per-group, so a channel can be set to buy while a busy chat only ever pings you.
The 3am call, taken at 3am
Meme markets do not keep your hours. The bot buys the moment the call lands, approves in the background, then watches the position and takes profit at the multiple you set — or cuts it at your stop. You wake up to a closed trade and a receipt, not a chart of what you missed.
Rules that do not get excited
Market cap range, liquidity range, maximum age, per-group buy size, take-profit and stop — checked against the chain in milliseconds, the same way every time. A token that fails one still reaches you as an alert with the reason, so you can see exactly what the filter kept out.
Next
X is where the call often breaks first
plannedThe bot already reads an X post when a link to one is shared in your chats — that part works today. What is not built yet is watching X directly: following a chosen list of memecoin accounts and acting on their posts the second they appear, with the same filters and the same wallets.
- Follow a handful of accounts, not a firehose — the influencers whose calls you would have taken anyway.
- Same rules, same wallets: an X post is just another source, with its own buy size and filters.
- Ticker and contract both read, so a post with only a $TICKER can still be matched on-chain.
Nothing here is promised by a date, and nothing is charged for it. When it lands, it lands for everyone already in.
Pipeline
What happens between the post and the transaction
Timings from the $WORM trade in the trace above — nothing here is theoretical.
0msMessage arrives in a chat you added. Chat filter, then per-group member filter.filter
<1msAddress extracted from text, entities, preview, buttons — X posts and chart links resolve in parallel.extract
50msToken scanned: market cap in dollars, liquidity, age, venue, pons fee and creator tax.scan
62msRoute priced — every candidate simulated against the live chain, the exact fill decides.route
385msSigned and broadcast from every selected wallet at once, to every RPC at once.send
+2sApproved in the background, so the sell never waits on an allowance.approve
livePosition watched every 2s — market cap, PnL, peak — and sold at your take-profit or stop-loss.manage
Access
Everything except buying is free
Connect your account, track your groups, build wallets, watch every call land with full detail. Buying is the one thing behind the gate — and there are two ways through it.
0.02 ETH
Pay once
- The bot gives you your own deposit address.
- Send the ETH; buying unlocks by itself, usually within a minute.
- No subscription, no renewal.
HOLD
Hold the token
- Hold the minimum amount and buying is free, for as long as you hold it.
- Prove the wallet is yours by sending 1 token to a throwaway address the bot generates.
- Sell below the minimum and the bot tells you access has lapsed.
Revenue
Every ETH payment is split in two
Nothing accumulates in an operator wallet. Half is burned into the token, half is paid back to the people holding it.
50%
Buy & burn
- Buys the token on-chain through the router.
- Delivers straight to 0x…dEaD in the same transaction.
- Supply falls with every payment, permanently.
50%
Holder revenue
- Goes to the revenue vault, claimable by holders.
- Eligibility: at least the minimum balance, held for the minimum number of days.
- Claim from the bot, or straight from the contract.
The vault is a contract of its own, with an owner-only emergency withdrawal — so ETH is never stranded if something goes wrong. Claiming opens when it is deployed and its address is published below.
Manual claim
vault not deployed
Claim straight from the contract
No wallet connection, no signature request, no approval to anything. You call the vault yourself from your own wallet — the bot only ever computes who is eligible.
Vault balance—ETH waiting to be claimed
Your shareyour tokens ÷ tokens held by everyone eligible
Minimum—below this, no revenue and no free access
Held for—must clear the minimum days before a claim counts
You can claim—fill in the fields above
1
Check what you are owed
The bot works out your share from your balance and how long you have held it.
Check in the bot
2
Send the claim
One transaction to the vault, from the wallet above. No value, just the call.
To
— published on deployment —Value
0 ETHData
0x4e71d92dclaim()Eligibility is a balance test and a time test: hold at least the minimum, and have held it for the minimum number of days. Selling below the minimum ends both the revenue share and free access — the bot tells you when that happens.
On-chain
Contracts and venues
The addresses a holder ever needs: where revenue is claimed, and where bought-back tokens go.
| Contract | Address | Role | Status |
|---|---|---|---|
| Revenue vault | not deployed yet | Holds the holder share; claims open on deployment | soon |
| Token | not launched yet | Holding it unlocks buying and earns a share of the revenue | soon |
| Burn | 0x000000000000000000000000000000000000dEaD | Where the bought-back tokens go | live |
pons v2 curves
Quoted in ETH, USDG, or a tokenised equity — GME, NVDA, SPCX, GOOGL, GLD. Graduated tokens follow their pool.
Uniswap v4, v3, v2
Including hooked and hook-managed v4 pools, where the liquidity lives inside the hook.
Simulated, not modelled
Each candidate route is run against the live chain first; the one that actually pays most is sent.