Shape the standard.
Blockchain, DNS, ISP, ICANN, IETF, and institutional experts are needed to turn the proposal into durable, interoperable rules.
Future networks may be sovereign, private, disconnected, delay-tolerant, or interplanetary. They will require local delegation authority while retaining the ability to interoperate.
Open design questions
- Precise staking and token allocation model that creates scarcity without creating a monetary asset.
- Smart-contract semantics for token minting, wrapping, expiration, uCRS commitment, and stake loss/return.
- Gold server protocol: record format, discovery, publication of the full claims list, marker records.
- Dispute resolution: Kleros-style or alternative courts; agentic first pass; who selects seats at each escalation level; funding of courts by the human.
- Humanity verification methods that the Gold server will accept (Worldcoin reference, oAuth paths, ISP-native auth).
- Renewal term growth rules that are hard to game and preferably immutable once earned.
- Relationship to existing IANA names (always preferred) and to specific TLDs such as .claw that may adopt the model.
- Resolver policy, DNSSEC interaction, and incremental deployment without requiring root changes.
Educational and standards institutions
Universities, research groups, and standards bodies can host discussions, run experiments, or contribute to the open specification. The base protocol intentionally does not require a particular blockchain, token, or company.
Reference material
The existing protocol repository contains the manifesto, architecture, threat model, and draft specification including the DannyClaw reference architecture:
This site is a public explanation and call for contribution. Pull requests, design proposals, and security analyses are welcome in both repositories.