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
Add specification requirements for using route blinding to make payments
while preserving recipient anonymity. Implementers must ensure they
understand all those requirements, there are subtle attacks that could let
malicious senders deanonymize the route if incompletely implemented.
| 18/19 |`option_support_large_channel`| Can create large channels | IN ||[BOLT #2](02-peer-protocol.md#the-open_channel-message)|
41
-
| 20/21 |`option_anchor_outputs`| Anchor outputs | IN |`option_static_remotekey`|[BOLT #3](03-transactions.md)|
42
-
| 22/23 |`option_anchors_zero_fee_htlc_tx`| Anchor commitment type with zero fee HTLC transactions | IN |`option_static_remotekey`|[BOLT #3][bolt03-htlc-tx], [lightning-dev][ml-sighash-single-harmful]|
43
-
| 26/27 |`option_shutdown_anysegwit`| Future segwit versions allowed in `shutdown`| IN ||[BOLT #2][bolt02-shutdown]|
44
-
| 44/45 |`option_channel_type`| Node supports the `channel_type` field in open/accept | IN ||[BOLT #2](02-peer-protocol.md#the-open_channel-message)|
45
-
| 46/47 |`option_scid_alias`| Supply channel aliases for routing | IN ||[BOLT #2][bolt02-channel-ready]|
46
-
| 48/49 | `option_payment_metadata` | Payment metadata in tlv record | 9 | | [BOLT #11](11-payment-encoding.md#tagged-fields)
| 18/19 |`option_support_large_channel`| Can create large channels | IN ||[BOLT #2](02-peer-protocol.md#the-open_channel-message)|
43
+
| 20/21 |`option_anchor_outputs`| Anchor outputs | IN |`option_static_remotekey`|[BOLT #3](03-transactions.md)|
44
+
| 22/23 |`option_anchors_zero_fee_htlc_tx`| Anchor commitment type with zero fee HTLC transactions | IN |`option_static_remotekey`|[BOLT #3][bolt03-htlc-tx], [lightning-dev][ml-sighash-single-harmful]|
0 commit comments