CPS-0001: Independent Implementation Challenge

[RaymondHWu]

This discussion is the structured successor to earlier CPS-0001 implementation challenge posts in this repository. Earlier discussions (#2 and #4) explored the same general question; this version consolidates the challenge into a more explicit, reproducible procedure and reporting format.

We are opening a small independent implementation challenge for CPS-0001, the Continuity Protocol core specification.

CPS-0001 defines a Continuity Receipt: a cryptographically verifiable statement about continuity-related evidence collected over a bounded interval.

The protocol is engine-independent: a receipt can be produced from evidence generated by different sensors, algorithms, or other observation mechanisms.

Current specification:

• CPS-0001 v1.0-RC1
• Apache 2.0
• Public specification and implementation materials are available in this repository.

The challenge

We are looking for developers who are willing to independently implement the minimum CPS-0001 flow from the public specification.

Estimated time: 30–90 minutes.

No prior knowledge of MyShape or The Continuity Lab is required.

The basic task is to:

1. Read the public CPS-0001 specification and implementation guide.
2. Implement a minimal CPS-0001 receipt independently.
3. Construct the canonical signing payload.
4. Sign it using Ed25519.
5. Compute the required receipt hash.
6. Verify the resulting receipt against the public conformance materials.

Independence

For the initial implementation, please do not use:

• the MyShape SDK
• MyShape application source code
• MyShape frontend/backend runtime
• the MyShape API
• the reference verifier
• the second-producer implementation

The goal is to see whether the protocol can be implemented independently from its normative documentation.

After your independent implementation is complete, you may compare your result with the reference implementation and conformance materials.

What we would like to learn

We are interested in both successful and unsuccessful implementations.

If something is ambiguous, difficult to implement, or appears inconsistent, please report it. A failure or ambiguity is useful evidence for improving the specification.

If you participate, you can optionally share:

• implementation language
• CPS-0001 version used
• whether you generated a receipt
• verification/conformance result
• receipt hash
• anything that was unclear or difficult
• optional repository or implementation link

You do not need to publish your source code.

Participation

If you are interested, reply to this discussion and let us know that you are attempting the challenge.

There is no deadline and no prior relationship with the project is required.

The purpose of this challenge is simple: determine whether an independent developer can implement CPS-0001 from the public specification without relying on MyShape's own implementation.

Please report the result honestly, including partial or failed results.