Skip to content

docs(specs): name the component that enforces the commitment algorithm; let a metadata-only Consumer reject stale evidence - #24

Merged
Wondertan merged 1 commit into
mainfrom
spec/req-38-25a
Sep 3, 2026
Merged

docs(specs): name the component that enforces the commitment algorithm; let a metadata-only Consumer reject stale evidence#24
Wondertan merged 1 commit into
mainfrom
spec/req-38-25a

Conversation

@xgreenx

@xgreenx xgreenx commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Draft into docs/ceremony-browser-contract.

  • REQ-COMMON-38: assigns the commitment-algorithm pin to the component that can enforce it — the Proving Circuit opens commitments with the pinned algorithm only, so a commitment made any other way fails the proof. No Consumer Chain component can see the algorithm; the format carries no identifier.
  • REQ-COMMON-25A / TEST-COMMON-13: a Consumer whose only authoritative effect is the metadata write rejects stale evidence instead of spending the digest for nothing. Matches IdentityNames (StaleProof). Consumers with a further effect still complete it.

Lint: no findings introduced over the base.

@xgreenx
xgreenx force-pushed the spec/req-38-25a branch 3 times, most recently from fe5c1bb to 3e95995 Compare September 3, 2026 00:55
@xgreenx
xgreenx marked this pull request as ready for review September 3, 2026 00:56
@xgreenx
xgreenx requested a review from Wondertan September 3, 2026 01:01
@Wondertan
Wondertan changed the base branch from docs/ceremony-browser-contract to main September 3, 2026 09:07
…a-only Consumer rejects stale evidence

REQ-COMMON-38 asked the Platform Verifier to reject a commitment made with
another hash algorithm, which nothing on a Consumer Chain can see. The
Proving Circuit opens commitments with the pinned algorithm and no other; a
commitment made any other way fails the proof. The requirement says that now.

REQ-COMMON-25A asked every Consumer to complete an operation with stale
metadata. A Consumer whose only effect is the metadata write would spend the
Authorization Digest for nothing; it now rejects stale evidence, and
TEST-COMMON-13 distinguishes the two cases.

Signed-off-by: xgreenx <xgreenx9999@gmail.com>
Assisted-by: Claude Fable 5.1
@Wondertan
Wondertan merged commit 4f205fd into main Sep 3, 2026
4 checks passed
@Wondertan
Wondertan deleted the spec/req-38-25a branch September 3, 2026 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants