Repository navigation
spec(exo-dcc.5): s3 holds the payee-chosen confirmation depth - #334
Merged
Merged
Conversation
The XMR request's typed spec, amended through discuss-issue (operator sign-off 2026-10-21). This follows #333, which made the confirmation depth the payee's choice. s3 now reads: a part is confirmed only with at least the confirmation depth the agreed request names (1-720 blocks, 10 when it names none). The depth is part of what everyone signed, so the same request at another depth is a different request no one agreed to. A depth out of range, or one on a non-Monero split, is refused. s1, s2 and s4-s7 are unchanged. A new s3 oracle, probe_xmr_depth_stepper, is a model check over: - each named depth against the confirmation counts around it, through the real propose, agree and confirm pump; - an agreement signed at one depth, refused at every other; - the refusals. The default-depth stepper is untouched (append-only). Tested-Behavior: grade-specs exo-dcc.5 8/8; exophial validate_spec OK; mutation checks — a confirm path ignoring the named depth fails the depth-1 state, and a depth left out of the signed bytes fails the signed state Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Session-Id: 836705fe-fda9-501b-8ac2-1ce50b5af64a
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
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.
This amends the XMR-request typed spec
derived-exo-dcc.5through discuss-issue, with your sign-off on 2026-10-21. It follows #333.What changes in the spec
The new oracle.
probe_xmr_depth_stepperis a model check over three things:The default-depth stepper is untouched, since invariant tests are append-only.
Tested
grade-specs exo-dcc.5: 8/8.validate_spec: OK.🤖 Generated with Claude Code