Lightning Specification Meeting 2021/11/22

[t-bast]

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

A video link is available if higher bandwidth communication is necessary at some point during the meeting: https://meet.google.com/abb-ekvg-oaw

Pull Request Review

• Route blinding Route Blinding (Feature 24/25) #765
• Onion messages BOLT 7: Onion message support (features 38/39) #759
• Add payment metadata to payment request Add payment metadata to payment request (feature 48) #912
• Advertize compression algorithms in init Advertize compression algorithms support in init (features 32/33) #825
• Dynamic DNS support in gossip messages BOLT 7: add gossip address descriptor type DNS hostname #911 or BOLT 1: adds remote address to optional init_tlvs (IP discovery) #917
• BLIPs process: bLIP 0001 #884
• Simple turbo channels enablement Explicitly allow funding_locked early, and support alias scids (feat 46/47/50/51) #910
• Anchor outputs clean-up anchors: follow up changes after initial zero fee anchors merge #903
• Feature bit for channel type BOLT-02+09: introduce feature bit to gate new channel_type feature - 44/45 #906
• Warning messages BOLT 1: introduce warning messages, reduce requirements to send (hard) errors #834
• Clarify channel_reestablish requirements Clarify and relax requirements on channel_reestablish #932
• Add dust exposure threshold Add a max_dust_htlc_exposure_msat #919
• Drop ping sending limitation Drop ping sending rate-limit suggestion #918

Long Term Updates

• 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
• Splicing Splice draft (feature 62/63) #863
• Offers Offers #798
• Trampoline routing Trampoline Routing (2021 edition) (Feature 56/57) #829 and Trampoline onion format (Feature 56/57) #836
• Upfront payments / DoS protection Hold fees #843
• Peer storage backup Peer backup storage (feature 40/41/42/43) #881

Backlog

The following are topics that we should discuss at some point, so if we have time to discuss them great, otherwise they slip to the next meeting.

• lnprototest (https://github.com/rustyrussell/lnprototest)

[michaelfolkson]

Hey @t-bast

A video link is available if higher bandwidth communication is necessary at some point during the meeting:

If you want to try doing these meetings entirely on video (with someone monitoring IRC for additional comments/questions) I am happy to do a transcript like I've been doing for the c-lightning dev meetings. Too late notice for today's meeting but something to consider for future meetings perhaps.

[t-bast]

Thanks @michaelfolkson, our main concern was indeed the lack of a transcript if we did the meeting over video, if you kindly propose to do it would be great! I'll mention it tonight and if we have rough agreement, we can try it for the next meeting.

[vincenzopalazzo]

If you want to try doing these meetings entirely on video (with someone monitoring IRC for additional comments/questions) I am happy to do a transcript like I've been doing for the c-lightning dev meetings. Too late notice for today's meeting but something to consider for future meetings perhaps.

Concept ack

[lucasdcf]

Hey @t-bast

A video link is available if higher bandwidth communication is necessary at some point during the meeting:

If you want to try doing these meetings entirely on video (with someone monitoring IRC for additional comments/questions) I am happy to do a transcript like I've been doing for the c-lightning dev meetings. Too late notice for today's meeting but something to consider for future meetings perhaps.

I was actually planning on proposing the same thing. I can help you if needed.

[t-bast]

One of my highlights from yesterday is that we're having issues agreeing on when/how feature bits and channel types should be used (in the context of #910, but it's something we bumped into a few times before).

I think it would be useful to focus on this particular topic during the next spec meeting, clarifying that meta topic will help speed up future discussions. We can use 0-conf as an example scenario to highlight our disagreements. @Roasbeef can you write something down to detail your approach (maybe in a new issue) and I'll do the same in parallel, and we can use that to guide the discussions next time?

[michaelfolkson]

Transcript (not yet merged but can be read here): https://github.com/michaelfolkson/bitcointranscripts/blob/lightning-2021-11-22/lightning-specification/2021-11-22-specification-call.md

[t-bast]

Thanks @michaelfolkson !