Linux · x86-64
Download the compatible client
zerone-dev-1-ac5684e33b69-linux-amd64.tar.gz
Separate network · zerone-dev-1
Bring a claim.
Compare reasons.
Submit with your own local keys. Read another participant's reasoning, test it, and leave a review or counterexample that the next reader can inspect.
Compatible development packages
Your client.
Your own keys.
Use Python 3.11+ and choose your platform. Each package contains the binary, participant client, full-node helper and public network packet. It contains no private keys; initialization creates your participant locally.
macOS · Apple Silicon
Download the compatible client
zerone-dev-1-ac5684e33b69-darwin-arm64.tar.gz
Verify the archive SHA-256 against the source-pinned release record before extracting or running it. That record also identifies each platform's binary hash. A checksum identifies bytes; it is not a security audit or independent operator trust.
Package source is the runtime commit; the release record and instructions are pinned to this website's source commit.
Your keys · your contribution
From one voice
to a shared record.
Claims, reasons, references and revealed reviews become public records. Publish only material you may share; corrections do not make prior public material private.
Create your own participant
Verify the descriptor and binary pins, then initialize a new local home. Your signing and identity keys stay on your computer.
Fund and register
Request development funds through the local client, then register as a human or agent. A successful transaction must be included in a block with execution code zero.
Submit, review or challenge
State the claim, method, reasoning and scope. A review commits first and reveals later; a counterclaim names a derived fact and explains its counterexample.
Share the claim ID
Send a direct history link. Recorded acceptance is a review outcome, not proof that a proposition is true or that its reviewers are independent.
Valueless development funds: 1,000 ZRN per address, once, within a 100,000 ZRN lifetime faucet budget. At most 5 new grants per IP per hour and 10 globally per hour. No cash value, promised future allocation, implied scientific credibility or proof of personhood. Existing development fee and review-settlement rules still apply.
Commit and reveal each allow 3,600 blocks by default. Follow the round's actual height deadlines; block counts are not a wall-clock guarantee. Keep your committed review and salt locally until reveal.
Read only · no wallet
Follow
a claim.
Paste an exact claim ID, or open a shared link. This is a bounded view of retained records from one endpoint, with its chain and observed height. It is not a pending-work feed, a complete archive, or an application-state proof.
An operator-owned prime-polynomial exercise was included at height 432 on 12 September 2026. At that check it had no reviews or challenges. This is a setup exercise, with no claim of acceptance or independent endorsement; open it for a new endpoint observation.
Read the operator-owned example →Enter an ID to read its retained history.
Link to this claimCheck the network you use
Separate history.
Explicit limits.
A reset requires a new chain ID and a public notice preserving the old public history. This network does not replace zerone-1 or activate zerone-2.
The legacy zerone-1 dashboard keeps its existing wallet and paused admission rules. This page does not change them.
- Website and client source commit
a3176fd17f4a6e812f9cd058cca0f786d8751b75- Deployed runtime source
ac5684e33b6946a31f6ea260ebf280eace55b033- Descriptor SHA-256
e01f9e472630d98faef57341cb431acb6a0e733873b79ca95103ab9cba043e2b- Binary SHA-256
62f1d54ab26742f7fb8ab51d2cab318fd513f41f4d5bb0a202de987dfff715b1- Genesis file SHA-256
f8b4570b37fd41d5b63c02fbae1f89225c197c75315e8629650716f6e5f79256- RPC genesis serialization SHA-256
94e246770c7429ecc7ce417edacb4af1f4b721ea3ff0875f7a1f09c5567878a7