docs(ap2): add Settlement Attestation -- categorical post-settlement envelope (AlgoVoi-authored)#271
Open
chopmob-cloud wants to merge 4 commits into
Conversation
…envelope (AlgoVoi-authored, MiCA Art. 80 / DORA Art. 14)
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request introduces a new documentation file docs/ap2/settlement_attestation.md detailing the Settlement Attestation format, its fields, canonicalisation, and lifecycle. Feedback on the documentation suggests correcting an incorrect reference to RFC 3339 in the description of the amount_microunits field, as RFC 3339 specifies date and time formats rather than numeric string representations.
|
|
||
| | Field | Type | Description | | ||
| | :---- | :--- | :---------- | | ||
| | `amount_microunits` | integer | Settled amount in chain-native microunits. MUST be integer. RFC 3339 string forms rejected. | |
Contributor
There was a problem hiding this comment.
The description for amount_microunits mentions "RFC 3339 string forms rejected." However, RFC 3339 is a specification for date and time formats, not numeric values. It should be updated to refer to string representations or decimal string forms instead.
Suggested change
| | `amount_microunits` | integer | Settled amount in chain-native microunits. MUST be integer. RFC 3339 string forms rejected. | | |
| | `amount_microunits` | integer | Settled amount in chain-native microunits. MUST be integer. String representations rejected. | |
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
1 participant
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
docs/ap2/settlement_attestation.md-- the AlgoVoi-authored Settlement Attestation format, the post-settlement categorical record emitted by a facilitator after on-chain confirmation.SETTLED/PENDING_FINALITY/REVERSEDsettled_payment_refbinds the attestation to its Payment Mandate via JCS canonicalsha256:referenceurn:x402:canonicalisation:jcs-rfc8785-v1(RFC 8785 JCS), byte-for-byte cross-validated across 8 independent implementationsNormative wire format: IETF Internet-Draft draft-hopley-x402-settlement-attestation (https://datatracker.ietf.org/doc/draft-hopley-x402-settlement-attestation/)
Reference implementations (Apache 2.0): algovoi-settlement-attestation on PyPI, @algovoi/settlement-attestation on npm.
Production: live against Base Sepolia (eip155:84532) since 2026-05-26.
Sibling to PR #269 (Compliance Receipt) and PR #270 (Payment Lifecycle). AP2 references the format; AP2 does not redefine it. AlgoVoi is sole author.
AlgoVoi (chopmob-cloud) -- Acquisition enquiries: https://docs.algovoi.co.uk/acquisition