MyShape

Develop

Reproduce CPS-0001 without trusting the issuer — or MyShape. The protocol is engine-independent; this is the order in which to reproduce it.

  1. 01Specification→

    CPS-0001 Continuity Protocol Core v1.0-RC1 — normative serialization plus the V₁–V₇ verification rules.

  2. 02Test vectors↗

    Frozen reference receipts (valid and invalid) with recorded SHA-256 hashes. The file bytes are normative.

  3. 03Reference verifier→

    Build and verify a receipt in the browser, or read the engine-independent reference implementation (no engine imports).

  4. 04cps-verify↗

    Standalone CLI reference verifier. Current CLI scope is V₁–V₆ — it has no V₇ chain traversal, so chain integrity needs the reference helper.

  5. 05Reproduce↗

    Create a receipt from any evidence engine, verify it, and run the frozen conformance suite. No MyShape required.

Boundaries

  • SDK 0.3.0 — evaluation only. It predates the Batch-2D hardening; for hardened verification use the repository reference verifier / cps-verify.
  • The SDK is not the only verification path. CPS-0001 is engine-independent: any conforming verifier can validate a receipt.
  • CPS-0001 verifies receipt integrity and continuity assertions. It does not prove a subject is a specific human, guarantee identity, or attest to issuer trustworthiness.
Lab PlaygroundMyShape Developer Docs

Repository: github.com/myshapeprotocol/myshape-protocol