archetech / archon / 34709716222

87%

push

github

feat: Bind the proof configuration into DID operation proofs (#1127)

Operation proofs declared EcdsaSecp256k1Signature2019, a registered type whose
specification requires RDF canonicalization and a jws member, while signing
JCS-canonical bytes into proofValue -- and its payload was the operation alone,
leaving created and proofPurpose outside the signature. created selects the
controller document version that authorizes an asset operation.

Operations now carry archon-ecdsa-jcs-2019, the suite credentials moved to in
#1085, whose payload hashes the proof configuration alongside the operation.
Both gatekeeper ports choose the payload from the proof's own type, so the
legacy form keeps verifying byte for byte -- permanently, since every anchored
operation carries it and each node replays its own history on restart.

ARCHON_PROTOCOL moves to /ARCHON/v0.13-beta. The topic names the wire format
rather than the release, which is why it sat at v0.8-beta until this change.

The seed bank's create operation keeps the legacy proof: its DID is the CID of
that operation including the proof, so signing it any other way would orphan
every wallet holding one.

Closes #1087.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

4139 of 4757 branches covered (87.01%)

Branch coverage included in aggregate %.

24 of 24 new or added lines in 2 files covered. (100.0%)

8796 of 9233 relevant lines covered (95.27%)

763.33 hits per line