spec: upgrade hash+feePayer limitation to BCP 14 language#204
Merged
brendanjryan merged 1 commit intomainfrom Mar 27, 2026
Merged
spec: upgrade hash+feePayer limitation to BCP 14 language#204brendanjryan merged 1 commit intomainfrom
brendanjryan merged 1 commit intomainfrom
Conversation
The existing informal text 'Cannot be used with feePayer: true' is a normative rule. Upgrade to proper RFC 2119 keywords: - Clients MUST NOT use type="hash" when feePayer is true - Servers MUST reject such credentials
Spec Preview
Download spec artifacts (HTML, TXT, XML, PDF) |
jxom
approved these changes
Mar 27, 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
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.
Upgrades the informal hash settlement limitation from plain text to proper RFC 2119 keywords.
Before: "Cannot be used with
feePayer: true(client must pay their own fees)"After:
type="hash"whenmethodDetails.feePayeristrueThis makes the rule testable and unambiguous for implementers.