You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make the payment secret ('s' field) mandatory for readers in addition
to writers, and update the payment_secret feature to ASSUMED status in BOLT 9.
This formalizes the expectation that all Lightning invoices must include
a payment secret after ~4 years of writer-side requirements.
The payment secret prevents intermediate nodes in the payment path from
probing for the destination by generating their own payment onions,
enhancing privacy in the Lightning Network.
- Add requirement for readers to fail payment if 's' field is missing
- Remove requirement to skip 's' fields with incorrect length
- Add test vector demonstrating an invalid invoice missing 's' field
- Change payment_secret feature to ASSUMED in BOLT 9
This aligns with existing implementations like LDK which already refuse
to pay invoices missing a payment secret.
Co-authored-by: morehouse <[email protected]>
Co-authored-by: brunoerg <[email protected]>
| 18/19 |`option_support_large_channel`| Can create large channels | IN ||[BOLT #2](02-peer-protocol.md#the-open_channel-message)|
44
44
| 22/23 |`option_anchors`| Anchor commitment type with zero fee HTLC transactions | IN ||[BOLT #3][bolt03-htlc-tx], [lightning-dev][ml-sighash-single-harmful]|
0 commit comments