Settlement engine
Start, poll the round, read the crash point, claim at cp − offset. The server accepts a claim at or below the crash point after the round has crashed. That is the play.
A panel bolted to the crash page that reads the round, claims inside the settlement window and runs the whole desk: bet engine, guards, analytics, market buyer and sniper. One lane, one ledger, no theatre.
The panel calls the same endpoints the site calls, with your existing session. It does not touch site files and never calls finish_crashed.
Start, poll the round, read the crash point, claim at cp − offset. The server accepts a claim at or below the crash point after the round has crashed. That is the play.
TURBO respects your delay. OVERDRIVE removes local overhead: 40 ms poll, zero wait. RUSH only unlocks when a probe proves the crash point leaks mid-flight.
FLAT, MARTI and % BAL, with a hard martingale cap. Guards: reserve floor, max consecutive losses, time limit and instant-crash limit.
A refused claim retries one cent lower, then two, then five, before the round is dropped. A cent of payout still beats a full loss.
Cumulative P/L, crash histogram, RTP, EV per round and per minute, round time, claim latency p50/p95, streak and drawdown. Every round is recorded locally.
SCAN the marketplace, BUY ALL with 1–12 workers, filters, budget, owned-title dedupe, retry pass and a listing SNIPE watcher.
Two 25-coin rounds test the leak and the mid-flight claim. RUSH stays locked until both halves pass. If claims get refused, the engine demotes itself instead of wasting the run.
Round length belongs to the server. RUSH is the only mode that changes the equation, and only after a passing probe.
| mode | round time | coins / min at 1,000 | note |
|---|---|---|---|
| TURBO | 9.0 s | ~7,000 | 80 ms poll, delay respected |
| OVERDRIVE | 7.6 s | ~8,200 | default ceiling of the crash timer |
| RUSH | ~1 s | ~62,000 | requires leak + accepted mid-flight claim |
The whole build is a host-scoped content script. No background worker, no extra permission, no page verification module. Settings and market checkpoints stay in local storage.
The panel appears bottom-right on every 0x21 page. It is draggable, minimizable and remembers where you left it.
Extract the delivered zip to a permanent folder. The manifest sits at the root; do not load the extension from inside the archive.
Open chrome://extensions, switch on Developer mode, press Load unpacked and select the folder. Pin the action.
Go to 0x21cracks.com and sign in with Discord. The panel mounts bottom-right once the page is idle. Refresh once after installing.
Press PROBE. It spends two 25-coin rounds and prints leak, mid-flight claim and exact-crashPoint results in the panel. Only then does RUSH unlock.
Not fine print — the mechanics that decide whether a session ends green or ends the account.
Current build is 2.0.0. Panel header and manifest carry the version.
No. It calls the same API routes the page calls, with your session, and draws its own panel over the page. The site's files are untouched, which keeps the footprint to one content script.
Two rounds at 25 coins. It tests whether the crash point is readable mid-flight and whether a claim at cp − 0.01 is accepted. Probe rounds are included in analytics, so the mean is diluted until real rounds accumulate.
No. The server keeps one active round per account and a second start orphans the first. A single lane is the design; worker count applies to market purchases, not crash rounds.
The panel writes the active-round key and tries to claim it on load. It is recovery, not a guarantee — avoid closing the tab mid-round.
After three refused mid-flight claims it demotes itself to OVERDRIVE for the rest of the run instead of wasting half a second per round. RUSH relocks until the next passing probe.
Owned ids and bought titles are stored under x21cf_market_v1 in the site's localStorage. A re-scan only queues what is missing. The run ends with a downloadable JSON report.
Ghost runs Stockfish 19 locally with arrows, eval and verified autoplay.