Lightning Specification Meeting 2021/09/27

[t-bast]

The meeting will take place on Monday 2021/09/27 at 8pm UTC on Libera Chat IRC #lightning-dev. It is open to the public.

Pull Request Review

• Restrict bitcoin amounts Restrict bitcoin amounts #908
• Feature bit for channel type BOLT-02+09: introduce feature bit to gate new channel_type feature - 44/45 #906
• Check each other's dust limits Peers need to check each other's dust limit #894
• 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
• Add payment metadata to payment request Add payment metadata to payment request (feature 48) #912
• BLIPs process: bLIP 0001 #884
• Simple turbo channels enablement Explicitly allow funding_locked early, and support alias scids (feat 46/47/50/51) #910
• Warning messages BOLT 1: introduce warning messages, reduce requirements to send (hard) errors #834

Long Term Updates

• Dual funding interactive-tx: Add dual-funding flow, using the interactive tx protocol (feature 28/29) #851
• Splicing Splice draft (feature 62/63) #863
• Blinded paths Route Blinding (Feature 24/25) #765
• Onion messages BOLT 7: Onion message support (features 38/39) #759
• 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.

• Hornet
• lnprototest https://github.com/rustyrussell/lnprototest

[t-bast]

As usual, don't hesitate to submit topics, or ask to reorder - we have many pending PRs and it's hard to judge which ones folks find more interesting.

[joostjager]

For the topics for which there is no preference, maybe it works to apply some kind of deterministic scheduling. For example "shortest diff first" or "longest time since last discussed first".

To increase the chances of getting things done without adding any personal preference.

[t-bast]

I'm not sure any kind of deterministic scheduling makes sense, in my opinion we should only discuss what most people are interested in (otherwise most people will just stay silent during the meeting). I'd like to see people push for the topics they're interested in, and that should give enough data to decide what topics should be prioritized.

Ideally that means many people should vote for what topics they're interested in before the meeting, and then we'd sort them by interest. Unfortunately people tend to have too many things on their plate and not enough time to prepare before the meeting. Or maybe we're just not using the right tools, and if we had a very simple way of voting for topics people would do it beforehand? If people want to chime in on that, I'd like to have some feedback.

[t-bast]

Actually thinking about this more, we don't need to add new processes to get this end result.
We can get satisfying results if:

• the meeting chair changes often enough to reflect every team regularly
• the meeting chair takes meeting items in the order that she's interested in (instead of the order listed in this issue)

I think we're mostly good on the first point, but no-one does the second one yet.

To all future meeting chairs: don't hesitate to do it! If you're chair, you get to chose what we discuss! That's an effective way to ensure we cover varying topics.

[t-bast]

Here are the meeting logs:

• Minutes: https://lightningd.github.io/meetings/ln_marketing_committee/2021/ln_marketing_committee.2021-09-27-20.07.html
• Minutes (text): https://lightningd.github.io/meetings/ln_marketing_committee/2021/ln_marketing_committee.2021-09-27-20.07.txt
• Log: https://lightningd.github.io/meetings/ln_marketing_committee/2021/ln_marketing_committee.2021-09-27-20.07.log.html