How Hookdroid works
Droids are rule sets that paper-trade every new Pons launch on Robinhood Chain. Each launch is scanned first, each move is explained, and each price links to the trade it came from.
Getting started
Hookdroid watches the Pons launchpad on Robinhood Chain. When a new token launches, the engine reads its first trades and scores it for safety. Droids then decide, by their own rules, whether to buy it on paper, skip it, or sell a position they hold.
Paper trading only. Droids use virtual money at real prices: $100 per trade. They never send a transaction, never touch your wallet and never ask for a deposit.
- Pick or tune a droidOpen the Studio, start from a house droid and move the sliders until the rules match how you think about new launches.
- Replay recent launchesThe Studio runs your rules on recent launches with the same decision code as the live engine and shows trades, win rate and the curve next to the baseline.
- Sign in and launchConnect a wallet on the dashboard and sign one plain-text message. Your droid then paper-trades every new launch and writes down why.
How droids work
A droid is a list of rules. Nothing else: no hidden model, no manual overrides. The same rules always give the same answer for the same launch.
One decision per launch
At its entry time (for example 10 minutes after a launch is created) the droid looks at the launch once and decides:
- BUY when every rule passes. The entry price is the last Pons trade price at that moment, and the size is $100 of virtual money.
- SKIP when a rule fails. The reason names the rule and the value, for example "Skip: 13 wallets bought in the same 3 s at launch (bundle)."
Open positions
Every engine tick checks open positions. A droid SELLS when the take profit or stop loss is hit, or when the max hold time runs out. The sell reason says which one fired.
What every decision stores
Time (UTC), launch, action, price, a plain-language reason, and the evidence: the Pons trade transaction hash and block the price came from. That is what makes a decision checkable on Blockscout.
The rules
| Rule | What it means | Example |
|---|---|---|
entryAgeMin | Minutes after the launch is created when the droid makes its one buy-or-skip call. One of 1, 2, 3, 5, 10, 15, 20, 30, 45 or 60. | 10 |
minScore | Lowest safety score (0 to 100) the droid accepts. | 80 |
minBuyers | Minimum unique buyer wallets, known bots excluded. | 15 |
maxDevPct | Highest share of supply the creator wallet may hold, in %. | 5 |
maxSnipers | Most known sniper bot wallets allowed in the first blocks. | 1 |
noBundle | true skips any launch where a group of wallets bought in the same seconds at launch. | true |
minProgress | How far the bonding curve must be filled, in %. | 20 |
maxProgress | Skip launches whose curve is already filled beyond this, in %. | 60 |
takeProfitPct | Sell when the position is up this much, in %. | 40 |
stopLossPct | Sell when the position is down this much, in %. | 20 |
maxHoldMin | Sell after this many minutes, whatever the price. | 360 |
House droids
Four droids by Hookdroid run all the time. They are a starting point for your own rules and a public reference: their full logs are open like any other droid.
Safe Only
by HookdroidSafety first. Waits 10 minutes, then only takes clean launches with real demand.
Early Bird
by HookdroidSpeed. Decides at 3 minutes with a lower bar and a wider stop.
Momentum
by HookdroidTrend. Waits 30 minutes for proof of demand and holds longer.
Bot Dodger
by HookdroidAnti-sniper. Skips launches that bots got into first.
The baseline
Every droid is compared with the simplest plan there is: buy every launch at 5 minutes and hold it for 6 hours. The leaderboard shows each droid's return and its difference to the baseline in points. A droid that cannot beat the baseline is not adding anything.
Safety scan
Before any droid sees a launch, the engine scans it. The scan reads the launch's first trades and wallets and runs six checks:
- Bundle at launch: a group of wallets buying in the same seconds as the launch.
- Dev buy and dev sold: how much the creator wallet bought, and how much of it was sold.
- Whitelisted and insider wallets: the share bought by wallets with early access.
- Known sniper bots: wallets from a list of known sniper bots buying in the first blocks.
- Real buyers: unique buyer wallets once known bots are taken out.
- Holder concentration: how much the largest holders own, the curve excluded.
The score
The score runs from 0 to 100. Each finding lowers it; a bundle at launch costs 35 points on its own. A red finding, such as a bundle or a dev who sold, caps the score at 79, so a launch with a red flag can never read as clean.
Every finding carries its evidence: the transaction hashes behind it, linked to Blockscout. Open any launch on the launch feed to see them.
A high score is not a safety guarantee. It means the six checks found no red flags in the on-chain data so far. Things can change after the scan.
Verify
Any decision can be checked without an account. Open its evidence link on Blockscout, compare the block, time and price with the log line, then replay the same rules in the Studio. The full walk-through, with a live example, is on Verify a decision.
Sign in and tiers
Browsing, the launch feed, the leaderboard and backtests need no account. To run your own droid you sign in once with a wallet:
- ConnectThe wallet shares your address only. The dashboard asks it to switch to Robinhood Chain (chain id 4663).
- Sign a messageYou sign a plain-text sign-in message with a one-time nonce. It is not a transaction: no gas, no approval, nothing leaves your wallet. Hookdroid never asks for a seed phrase or private key.
- VerifiedThe engine recovers the signing address from the signature (secp256k1) and opens a session. Droids you create are owned by that address and show a "signature-verified" badge.
Tiers
After you sign in, the engine reads your $HOOKDROID balance on Robinhood Chain and sets your limits.
Holder tiers unlock at launch. Until the token exists, every wallet runs on Free.
The balance is read live from Robinhood Chain and refreshed about once a minute. Buying details are on the token page.
Public API
Everything on the site comes from the same JSON API. The read endpoints are open; send requests from your own scripts at a reasonable pace.
| Endpoint | Returns |
|---|---|
GET /api/stats | Launches scanned, droids running, decisions, paper trades, hours running, per-day counts. |
GET /api/launches?limit=50 | Newest launches with safety score, verdict, flags, buyers, dev share and progress. Page with cursor. |
GET /api/launches/:ca | One launch with its scan findings, evidence tx hashes and droid decisions. |
GET /api/droids?sort=return | All droids with rules, owner, status and stats against the baseline. |
GET /api/droids/:id | One droid: decisions (paged with cursor), positions and equity curve. |
GET /api/decisions?limit=50 | Latest decisions of all droids with reason, price and evidence. |
POST /api/backtest | Body {"rules":{…}}: replays the rules on recent launches. Rate-limited. |
Errors come back as {"error":{"code","message"}}. A rate-limited answer (HTTP 429) carries retryAfter in seconds. All times are UTC.
FAQ
Does a droid ever trade real money?
No. Every trade is on paper: $100 of virtual money at the real Pons price of that moment.
Why did my droid skip a launch that went up?
Because one of its rules failed, and the skip reason names which one. Rules trade some winners for fewer bad entries; the Studio shows that trade-off before you launch.
Can I change a droid's rules after launch?
Rules are fixed once a droid runs, so its track record stays honest. Pause or delete it on the dashboard and launch a new one with the new rules.
Where do prices come from?
From Pons trades on Robinhood Chain. Each decision stores the trade tx and block its price came from.
Which wallets work?
Any EVM wallet that can sign a message, such as MetaMask, Rabby, Coinbase Wallet, OKX Wallet or Trust Wallet.