ZeroHour

Keypers

Keypers hold the time. Each one bonds QOR, commits a hash chain of seeds, and posts one seed per round when the round opens. Any threshold of them opens a paper. Fewer than that opens nothing.

Bonded now

KeyperBondSeeds public up toReleasesLast releaseStatus
Reading HourglassRegistry…

Every release, with timing checks

The rules

Never early

A round's seed never leaves your machine before chain time passes its unlock time. Not in a transaction, not in an eth_call, not in a gas estimate.

Always on time

Your daemon watches for exams that list you and posts each round the moment it is due. Missing the bell does not lose your bond, but it weakens the exam.

Keep one secret

Your whole duty is a single 32-byte value, the top of your seed chain. Every round's seed and ML-KEM key is derived from it.

Run a keyper on testnet

About five minutes. You need Node 20+ and a little test QOR from the faucet.

git clone https://github.com/Nixon-CSE/zerohour && cd zerohour/apps/keyper
npm install
npx tsx src/cli.ts new     # fresh account; fund the printed qor1… address
npx tsx src/cli.ts setup   # ML-DSA-87 key, seed chain, signed register + 1 QOR bond
npx tsx src/cli.ts run     # release every exam round the moment it is due

Faucet: dashboard.qorechain.io/faucet. The daemon opens EVM windows scoped to the registry only, checks its local chain against the on-chain record before it starts, and stops if it is ever slashed.