Lightning Specification Meeting 2021/09/13

[t-bast]

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

Pull Request Review

• Warning messages BOLT 1: introduce warning messages, reduce requirements to send (hard) errors #834
• 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 and Allowing dust limit below 546 sats #905
• Simple turbo channels enablement Explicitly allow funding_locked early, and include scid. #895
• Add payment secret feature to Bolt 11 test vectors Add payment secret feature to Bolt 11 test vectors #898
• Advertize compression algorithms in init Advertize compression algorithms support in init (features 32/33) #825
• BLIPs process: bLIP 0001 #884
• Restrict bitcoin amounts Restrict bitcoin amounts #908
• Dynamic DNS support in gossip messages BOLT 7: add gossip address descriptor type DNS hostname #911

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
• Trampoline routing Trampoline Routing (2021 edition) (Feature 56/57) #829 and Trampoline onion format (Feature 56/57) #836
• Onion messages BOLT 7: Onion message support (features 38/39) #759
• Blinded paths Route Blinding (Feature 24/25) #765
• Offers Offers #798
• 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 add/remove/reorder topics.

[cdecker]

#911 looks like a simple one to discuss (not implemented and thus not mergeable yes, but a good idea imho)

[t-bast]

Added to the PR list. I think it will probably slip to the next meeting though, since the PR was just submitted and I don't expect many people to have looked at it before the meeting?

[ryanthegentry]

I think #884 just needs a final ACK before merging? Does it need to be on the agenda or can the ACK happen async?

[t-bast]

I think #884 just needs a final ACK before merging?

Not yet, at least on my part it's not an ACK yet.

I think this comment indicates that we're still not sure whether this should be in the spec repo or a separate one. We should probably have some kind of vote to settle it (which means we need enough participants to have a meaningful vote).

And IMHO, we cannot merge this without including the "companion blip" that structures how to reserve scarce identifiers. This is only mentioned in blip-0001, but I think it's insufficient, we really need that before we can proceed.

I'm adding this to the agenda.

[ryanthegentry]

Yes I think there are differences of opinion on the "companion blip" - should there be a single central blip doc that replaces #605 and #716 and is referred to in the respective BOLTs? Or should the assignments be made into the BOLTs themselves (which is how I currently have it)? Looking forward to discussing in an hour!

[t-bast]

Meeting minutes: https://lightningd.github.io/meetings/not_the_marketing_committee/2021/not_the_marketing_committee.2021-09-13-20.06.html

Log: https://lightningd.github.io/meetings/not_the_marketing_committee/2021/not_the_marketing_committee.2021-09-13-20.06.log.html