Skip to content

spec: upgrade hash+feePayer limitation to BCP 14 language#204

Merged
brendanjryan merged 1 commit intomainfrom
brendan/hash-feepayer-bcp14
Mar 27, 2026
Merged

spec: upgrade hash+feePayer limitation to BCP 14 language#204
brendanjryan merged 1 commit intomainfrom
brendan/hash-feepayer-bcp14

Conversation

@brendanjryan
Copy link
Copy Markdown
Collaborator

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:

  • Clients MUST NOT use type="hash" when methodDetails.feePayer is true
  • Servers MUST reject such credentials

This makes the rule testable and unambiguous for implementers.

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
@github-actions
Copy link
Copy Markdown

Spec Preview

Spec Changed
draft-card-charge-00 -
draft-httpauth-payment-00 -
draft-lightning-charge-00 -
draft-lightning-session-00 -
draft-payment-discovery-00 -
draft-payment-intent-charge-00 -
draft-payment-transport-mcp-00 -
draft-solana-charge-00 -
draft-stripe-charge-00 -
draft-tempo-charge-00 Yes
draft-tempo-session-00 -

Download spec artifacts (HTML, TXT, XML, PDF)

@brendanjryan brendanjryan enabled auto-merge (squash) March 24, 2026 21:57
@brendanjryan brendanjryan requested review from jxom and tmm March 25, 2026 15:11
@brendanjryan brendanjryan merged commit b2d0187 into main Mar 27, 2026
2 checks passed
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