Lightning Specification Meeting 2021/12/06

[t-bast]

The meeting will take place on Monday 2021/12/06 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

Pull Request Review

• 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
• Route blinding Route Blinding (Feature 24/25) #765
• Onion messages BOLT 7: Onion message support (features 38/39) #759
• 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
• Simplified commitment Feature 106/107: option_simplified_update. #867
• 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)

[t-bast]

@michaelfolkson sorry for the late notice, if you're available to do transcripts for this meeting it would be great!
If you prefer something else than Google Meet, simply provide a link that lets anyone join the meeting without installing any software and we should be good to go.

[michaelfolkson]

@t-bast: Sure, it is in my diary now.

The transcript from the last spec meeting: https://btctranscripts.com/lightning-specification/2021-11-22-specification-call/

Let's try Jitsi (open source, Tor support) as a number of people expressed a preference for it last time: https://meet.jit.si/Lightning-Spec-Meeting

If there are any problems we can always fall back to Google Meet.

[michaelfolkson]

Btw if anyone wants their personal comments in future transcripts to be attributed let me know. By default I will anonymize unless someone lets me know otherwise. But it is totally individual preference.

[t-bast]

I'm fine with anonymizing comments by default, in theory it lets readers focus on the content, not on individuals.

[michaelfolkson]

Transcript: https://github.com/michaelfolkson/bitcointranscripts/blob/lightning-2021-12-06/lightning-specification/2021-12-06-specification-call.md

[t-bast]

Thanks @michaelfolkson 👍