ApeChain
Live registry 0x4848…8A95
Reading the live registry…Drill registry of the live run 0xd73E…B0C0
Reading the run's drill…Plate XIX
An ownerless registry posts bounties on five public keys whose private keys nobody knows. A claim proves a curve has fallen; every Qanary account reads the registry and shuts its classical keys down in response.
Each network has its live registry, read below as it stands, and the drill registry the recorded run tripped on purpose: the first ladder rung where a ladder verifier runs, then secp256k1. The run’s treasuries follow the drill, so their hot keys are shut.
Live registry 0x4848…8A95
Reading the live registry…Drill registry of the live run 0xd73E…B0C0
Reading the run's drill…Live registry 0x4848…8A95
Reading the live registry…Drill registry of the live run 0xd73E…B0C0
Reading the run's drill…Each target is a point found by hashing a public tag onto the curve: x = SHA-256(tag ‖ counter) mod p, taking the first counter that lands on the curve and the even y. Nobody chose the point, so nobody knows its private key; a valid signature by one of them proves the discrete logarithm was computed. scripts/nums.py in the repository writes them, and this page re-derived each one when it was built.
Ladder rung 1
Ladder rung 2
Ladder rung 3
Ethereum keys
Passkeys
The ladder curves are too short for Ethereum’s precompiles, so a Stylus program checks them. It is live on ApeChain. Sign a message here with a published drill key (python-ecdsa’s RFC 6979 signing, reproduced in the browser) and the verifier answers.
A drill is a fresh registry over the drill keys, whose private keys are published. Claim its targets one by one and watch the level rise and the families break, exactly as the live registry would, without touching it. Claims are signed in this page and sent from your wallet.