Six days of explaining what we built and why. Today we stop explaining.
We're issuing a challenge instead.
═══════════════════════════════════════
THE BAR WE SET We built the protocol for cryptographic continuity. Now, we're asking you to break it.
A clean machine, no prior exposure, one command — and every check passed. That's our standard. Not "read our whitepaper and believe us." Not "trust our benchmark numbers." Run it and see.
═══════════════════════════════════════
HOW TO TAKE THE CHALLENGE
-
THE ONE-COMMAND CHECK
npx @thecontinuitylab/myshape
If you have Node installed, the package downloads, loads, and self-checks instantly.
-
TEN LINES OF CODE
npm i @thecontinuitylab/myshape
Call verifyContinuity() with your own sensor data and watch a real cryptographic verdict come back.
-
THE HARD MODE — IMPLEMENT CPS-0001 YOURSELF
The spec is public. Produce a Continuity Receipt without our help, in your own language, from a fresh reading of the specification.
A protocol is only real if it survives contact with people who have no reason to be kind to it. Break it, implement it, or ignore it — all three are data we want.
You don't need to trust us. Run it yourself.
Spec: github.com/myshapeprotocol/myshape-protocol Research hub: thecontinuitylab.org
#TheContinuityLab #CPS0001 #OpenProtocol #Cryptography #ZeroKnowledge #HackerChallenge