Add two-TS Transparent Statement: Microsoft CCF dev + ASG RFC 9162 SHA-256 - #4
Open
StevenMih wants to merge 1 commit into
Conversation
ES256/did:x509 Signed Statement made transparent in two independent Transparency Services: Microsoft CCF dev node (ccf.v1 / vds=2 / ES384) and Action State Group (RFC 9162 SHA-256 / vds=1 / EdDSA). Both receipts are embedded in the unprotected header under key 394, following the pattern of the existing cose-hash-envelope-0 example. Statement SHA-256 (leaf entry): 02ec7822cd91641c74ee0d125ad9b89fc6961400c6efb69ec9aff65f3b23d567 Transparent statement SHA-256: aa9e2e7f5d62b501dbd2f2d3179e8f9aac5bde91009441d6ba872b94f0de2597 Both receipts verified ok=True with scitt_cose.verify_receipt before submission. CCF receipt is from a dev node — not a production deployment. Produced during IETF 126 / Vienna 2026 cross-implementation interop (draft-mih-scitt-agent-action-capsule). Full interop artifacts and verify steps in action-state-group/scitt-cose interop/ccf/.
achamayou
approved these changes
Jul 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a Transparent Statement carrying receipts from two independent Transparency Services with different receipt profiles, following the pattern established by
cose-hash-envelope-0-with-microsoft-mst-and-datatrails-mmr-receipts.scitt.As noted during IETF 126 / Vienna 2026 interop: receipt profiles can be used in conjunction as well as in isolation. This is a second instance of that pattern with a different TS pair.
New file:
Statement
did:x509(Amaury Chamayou / Microsoft)application/json02ec7822cd91641c74ee0d125ad9b89fc6961400c6efb69ec9aff65f3b23d567achamayou/scitt-ccf-ledgerbranchproduce-ccf-profile-receipts-for-capsuleReceipts (unprotected header key 394)
ccf.v1/vds=2/ txid2.15vds=1The Microsoft receipt is from a CCF dev node, not a production deployment.
Verification
Both receipts verified with
scitt_cose.verify_receiptbefore submission. Full interop artifacts and three-receipt verify output are inaction-state-group/scitt-coseatinterop/ccf/shared-vector.json(version 2).Suggested reviewer: @achamayou