- Points logged for the current target
- —
Every one re‑derived by the pool before it counted.
keyroo is a distributed Pollard’s Kangaroo search. Volunteers’ GPUs walk one shared herd of kangaroos across an enormous interval, looking for the place two of them land together. The coordinator recomputes every point it is sent and keeps only the ones that check out.
Mainnet only. This is the whole of your identity here — no account, no name, no cookie. Nothing runs until you press Run, and stopping is instant.
- Your rate
- —
- Backend
- WebGPU
What you have contributed
- This run
- 0
- This address, all time
- 0
- Share of this run
Points the coordinator verified since you pressed Run.
Across every run and every device that named this address.
Your points over the fleet’s, which is the only ratio that matters.
Two herds, walking until they collide.
Tame kangaroos set off from a known point. Wild ones set off from the key we are looking for. Both take jumps decided by where they land, so the moment one lands where another has already been, the two walk in lockstep for ever — and the distance between them is the key.
A kangaroo only reports when it lands somewhere distinguished, which is what keeps a million GPUs from drowning the coordinator in traffic. Those reports are the points you are credited for.
What this does, plainly
- Nothing runs until you say so
- Your GPU walks only while this tab is open and you have pressed Run. Close the tab or press Stop and it stops. Nothing is installed and nothing runs in the background.
- There is no account
- No sign‑up, no email, no name, no cookie, no analytics. An address is issued a worker token for the session and that is the extent of it. Come back tomorrow with the same address and your total is still yours.
- Points are checked, not taken on trust
- The coordinator re‑derives every point before crediting it — one scalar multiplication each. A satellite cannot inflate its share, and an honest one never sees a rejection. A submission containing a point that does not verify is refused whole.
- If the key is found, the split is proportional
- Every contributor is paid in proportion to verified points, minus a — operator fee, read from the coordinator rather than written here. There is no finder’s bonus and no other deduction. The pool itself never signs anything: it writes the key and what it owes to disk, and the payment is made offline. Nobody can tell you the odds, and this page will not pretend to.
- You keep a receipt for every submission
- Each accepted checkin is a leaf in an append‑only Merkle log, and you get a signed receipt naming its index. Keeping them is what lets you check the pool later without asking the pool.
Leaderboard
Points verified for the current target.
| # | Address | Points | Share |
|---|---|---|---|
| Reading the board… | |||
Questions worth asking first
What does the pool take?
— of anything recovered, read from the coordinator rather than written into this page. It pays for the machine that holds the point table, verifies every submission and stays up between finds — a search of this size is years of storage and bandwidth, not a weekend. Everything else is divided among contributors in proportion to verified points. No finder’s bonus, no other deduction.
What stops someone submitting made‑up points?
Every point is re‑derived before it is credited — the coordinator recomputes the curve point from the distance claimed for it and compares. A forged point cannot survive that, and a repeated one earns nothing because the table is keyed by position.
A submission containing one is refused whole — nothing in it is credited, including the honest points alongside it. It is not possible to gain by trying, only to waste a lease.
What happens the moment a key is found?
One transaction, straight away, moving the whole balance to cold storage. Not to contributors — signing hundreds of outputs live, from a machine that has been accepting connections from strangers, is a worse risk than the one it would avoid. Payouts follow from cold storage within 24 hours, in proportion to the points the log already records.
That window is the part you have to take on trust, and every pool has one. What this pool can do is make the inputs to the payout impossible to revise after the fact: your contributions are leaves in a signed, append‑only log, published as they happen, and the split is fixed at the instant of the find. You can prove what you were owed. You cannot force the operator to send it.
How is the split worked out?
Verified points, divided by all verified points for that run, applied to the balance after the operator’s share. The denominator is published continuously, so your share is checkable at any moment rather than announced at the end. Points from earlier runs do not carry over — each target is settled on its own.
Is the code available?
All of it, GPLv3, including the kernels and this page. github.com/keyroo/keyroo. The builds are reproducible: the repository publishes the hash of every artifact, and one command rebuilds them and compares.
Can I run it for myself, without a pool?
Yes. The solver runs standalone against any target you like, with no coordinator and nobody taking a share — the pool exists to make one search out of many machines, not to gate the software. Setup is documented in the repository.
Don’t trust this page. Audit it.
Everything the pool publishes can be checked offline, on public inputs alone, without the coordinator’s cooperation. Each command exits non‑zero on failure, so it composes into a watchdog.
keyroo verify roots- Every published root is signed, the log never rewinds, and each root is a prefix of the next.
keyroo verify receipts- Your receipts are signed over their whole submission, and the log really grew to contain them.
keyroo verify solve- The revealed key multiplies to the announced target. Nothing can fake that.