Ten days ago we issued a challenge: "You don't need to trust us. Run it yourself."
A protocol is only real if it survives contact with people who have no reason to be kind to it.
There's one number the spec can't produce for us:
Zero Independent Implementations.
We are going to publish it just the same, because the entire point of this series is that we publish our limitations before we publish our claims.
What the number means:
The ecosystem is still one team.
The engine-independence claim the whole spec rests on has not been tested by a stranger.
The blind implementation test is still an empty template.
Why it matters:
If only one team can produce and verify receipts, the protocol is just that team's format. A protocol is only real when a single spec — no SDK, no source — produces a valid receipt.
The bar is low and open:
Your code → receipt.json → cps-verify → ✅ VALID
30–90 min, any language, any SHA-256 / Ed25519 / JSON library.
We don't ask you to believe anything. We ask you to read the spec, try to implement it, and tell us where you got stuck. Success or failure, your attempt is the data point we need.
The first independent implementation will be listed on the ecosystem page.
Try the two doors:
Implement it: github.com/myshapeprotocol — Independent Implementation Challenge
Join the study: thecontinuitylab.org/research/apply
TheContinuityLab #CPS0001 #OpenProtocol #DecentralizedIdentity #Web3Protocols #ZeroKnowledge #ProtocolDesign #IndependentImplementation #Rust #TypeScript #DeveloperExperience #VerifiableCredentials
Top comments (0)