Getting a token

A client token identifies you to the coordinator and ties heartbeats and accepted results to your cabinet and leaderboard entry.

Paste the token into the cabinet to see your personal stats.

Running a client

The client leases disjoint key ranges; point it at this coordinator and pass your token.

rotor -m addresses --chain bitcoin --range 400000000000000000:7fffffffffffffffff \
  --coordinator https://your-coordinator.example --token <client-token> \
  --client-id my-machine --targets targets.txt

Use --client-id to name the machine. When the coordinator authenticates per-client tokens, the server owns the identity: the token decides which account receives the work and stats.

Admin-only commands create jobs and manage accounts; a client token cannot create jobs.

# create a job (admin token)
rotor-coord --token <admin-token> --state coordinator.json --bind 127.0.0.1:7878

CPU

Without -g the client scans on the CPU. CPU is the supported path for coordinator mode with every search mode.

GPU

Add -g and select devices with --gpui; address and xpoint searches also accept --gpux for the grid. Each selected device runs its own lease loop.

rotor -g --gpui 0 -m address --chain bitcoin --range 400000000000000000:7fffffffffffffffff \
  --coordinator https://your-coordinator.example --token <client-token> --client-id rig-a \
  GXtpBqxw3xwZ61zZ3f3uWk2dNq6M6j4K6w6yY1R1cGxY...

BSGS

BSGS jobs store a resumable giant-step checkpoint on the coordinator. CPU BSGS is the supported coordinator path; -m bsgs -g is rejected with --coordinator because the giant walk lives on the coordinator.

Browser client

Open /run, paste a client token from the cabinet and press Start. The tab runs the WASM scan core on the CPU, leases the same chunks and submits the same completion proofs as the native client. It only leases jobs the operator already created (authorized puzzle jobs only) and cannot create jobs.

Private-key explorer

/key is a read-only private-key explorer. Derivation runs in this browser in the same WASM artifact the worker uses; the coordinator only serves the page. It accepts hex, decimal or Bitcoin WIF keys for secp256k1 and ed25519, and shows BTC (legacy/P2SH/segwit/taproot), EVM, TRON, Solana, Litecoin, Dogecoin, Bitcoin Cash and XRP addresses with expandable calculations.

Public key pages

/private-keys is the directory of 18 chains. Every chain page shows 60 keys at a time with First/Previous/Random/Next/ Last controls, a page jump, HEX/WIF/brainwallet search and — for Bitcoin and Litecoin — address-type tabs (Legacy, SegWit, Nested SegWit, Taproot). Addresses are derived locally and balances are checked in your browser; only the derived public addresses reach a public provider. /keys is a permanent alias for the directory, and /keys/<chain>/<start>-<end> opens a key range. A URL such as /key/<64 hex> derives every address for one key. The first 64 keys and ranges are index,follow; later chain pages and arbitrary keys are noindex,follow.

Because the key is in the URL, the coordinator knows which key page was requested. The page shows a notice and checks only the derived addresses against the registry, so a registered owner can be warned that someone opened a page containing their address. Typing a key locally on /key is checked only if you tick the opt-in box.

Address monitor

/cabinet watches addresses you control: connect an EVM wallet, sign the one-time SIWE challenge, and the coordinator stores those accounts and reports balance/nonce changes in your feed. It never asks for a private key, WIF or seed phrase, never signs, and never moves funds.

Transaction decoders

/tx/bitcoin decodes a raw Bitcoin legacy or SegWit transaction in the browser: version, SegWit marker and flag, every input and witness item, every output with its value and script type (P2PKH, P2SH, P2WPKH, P2WSH, P2TR, P2PK, OP_RETURN or unknown), the decoded address where the script has one, locktime, serialized size, weight and virtual size. A fee is reported only when you supply one satoshi value per input; without prevouts the page says the fee is unavailable and does not guess.

/tx/ethereum decodes a raw EIP-2718 legacy, access-list (type 1) or EIP-1559 (type 2) transaction: chain id, nonce, gas price or max priority/max fee, gas limit, destination or contract creation, value in wei and ETH, data length/selector/first bytes, access list and the y-parity or v, r and s fields. RLP is validated for canonical encoding; signature recovery and verification are not performed.

Both pages are client-side only: no key, network request, storage or URL payload. /tx is the shared index.

Site map and donor parity

The parity audit maps every Crypto route to its privatekeyfinder.io and secretscan.org equivalent. It is internal documentation, kept in docs/site-map/index.html and docs/site-map/site-map-data.js, not a public route. The data also carries the feature matrix (parity, partial and missing capabilities with a priority), so a gap closes only when the data says so.

Security and disclaimer