docs: 3.1.2, payment/buyer/seller fields described as billing of the certification - #6
Merged
Merged
Conversation
…n de la certification Wording seul, aucun changement de format, d'algorithme ni de données de vecteurs. Le but et les descriptions présentaient chaque preuve comme un achat entre acheteur et vendeur ; une note explique que ce sont des noms historiques conservés pour le chain hash. Le README ne présente plus la vérification par concaténation comme générique : elle ne vaut que pour les preuves legacy. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
spec_version3.1.2.payment.*,buyer,sellerdescribed as billing of the certification, with a note on the historical names.Checks
check_consistency.py: ALL CHECKS PASSED.🤖 Generated with Claude Code