Lightning Specification Meeting 2023/12/18

[t-bast]

⚠️ This meeting will be skipped, go enjoy your holidays folks, get away from that keyboard for a few days! ⚠️

The meeting will take place on Monday 2023/12/18 at 7pm UTC (5:30am Adelaide time) on Libera Chat IRC #lightning-dev. It is open to the public.

A video link is available for higher bandwidth communication: https://meet.jit.si/Lightning-Spec-Meeting

Special topics

• Final call for mailing list host ending support in 2023

Recently Updated Proposals / Seeking Review

This section contains changes that have been opened or updated recently and need feedback from the meeting participants.

• Dual funding interactive-tx: Add dual-funding flow, using the interactive tx protocol (feature 28/29) #851
• Liquidity ads option_will_fund: liquidity ads #878
• Simplified mutual close option_simple_close (features 60/61) #1096
• Quiescence BOLT 2: quiescence protocol (feature 34/35) option_quiesce #869
• Trampoline routing Trampoline Routing (2021 edition) (Feature 56/57) #829 and Trampoline onion format (Feature 56/57) #836 (2024 is going to be the year of trampoline 🎉)
• Spec clean-up Clean up: remove two unused features, assume four more #1092
• Offers Offers #798
• Taproot extension-bolt: simple taproot channels (feature 80/81) #995
• Taproot gossip extension-bolt: taproot gossip (features 70/71/72/73/74/75) #1059
• Attributable errors Attribution data (feature 36/37) #1044
• Channel jamming draft: Staking Credentials token issuance/redemption #1043 draft: HTLC Endorsement to Mitigate Channel Jamming #1071
• Splicing Splice draft (feature 62/63) #863 vs Dynamic Commitments zzz-extension-bolt: a proposal for dynamic commitment upgrades #1090 Extension/dynamic commitments #1117 vs Upgrade on reestablish BOLT 2: upgrade protocol on reestablish #868
• Clarify channel_reestablish requirements Clarify channel_reestablish requirements #1049 or Rework channel_reestablish requirements #1051
• Peer storage backup Peer backup storage (feature 40/41/42/43) #881 or Peer storage for nodes to distribute small encrypted blobs. #1110

Stale Proposals

This section contains pending changes that may not need feedback from the meeting participants, unless someone explicitly asks for it during the meeting. These changes are usually waiting for implementation work to happen to drive more feedback.

• Inbound fees Inbound routing fees blips#18 and Add a bLIP for backwards-compatible inbound fees blips#22

Waiting for interop

This section contains changes that have been conceptually ACKed and are waiting for at least two implementations to fully interoperate.
They most likely don't need to be covered during the meeting, unless someone asks for updates.

• Don't force close until error is received after channel_reestablish Nodes shouldn't publish their commitment when receiving outdated channel_reestablish #934

Long Term Updates

This section contains long-term changes that need review, but require a substantial implementation effort.

• Simplified commitment Feature 106/107: option_simplified_update. #867
• Hold htlcs before forwarding Add the ability to hold HTLCs before forwarding (FEAT 52/53) #989
• lnprototest (https://github.com/rustyrussell/lnprototest)

[TheBlueMatt]

This is a week before christmas, lets skip it.

[t-bast]

Works for me, Rusty said he would be on vacation as well, let's do sync in early January then!

[morehouse]

Works for me, Rusty said he would be on vacation as well, let's do sync in early January then!

Do we have a final plan for the mailing list? IIRC, it will go away at EOY, and it seems we might not have a replacement before then.

[t-bast]

Do we have a final plan for the mailing list? IIRC, it will go away at EOY, and it seems we might not have a replacement before then.

We can discuss that directly here I guess? I personally played around a bit more on delvingbitcoin and configured notifications, I'm happy with it, but I'd be happy with a standard mailing list as well. I haven't tried the discourse backup feature yet, I think that's one important thing to check.

[TheBlueMatt]

We can discuss that directly here I guess?

SG

I am fine with Delving Bitcoin. I set up the "ML mode" thing so I get a dump of every post on the whole website. Its broader than lightning but currently low enough traffic that I'm fine with it (but that might change). Sadly I can't reply without clicking a link and logging in, which may limit my posting, but probably not too much. I believe @Roasbeef had indicated he'd like our own DIscourse instance so that those that want a full email dump can have it be limited to Lightning. I'm not entirely convinced if we go our own way Discourse is any better than an ML, and would still prefer a classic ML, but if others agree/feel strongly I could also set up hosting for a Discourse instance.

[vincenzopalazzo]

I am fine with Delving Bitcoin but let keep the conversation in a single place, so when we move to Delving Bitcoin we should deprecate the list or something like that.

Otherwise it is hard to keep up with everything

[TheBlueMatt]

The existing list will stop working on Dec 31.

[t-bast]

I'm fine with either choice (discourse or standard ML), so I'll also let others who feel more strongly decide!

[ariard]

Can be pinned: #1126