Lightning Specification Meeting 2020/02/03

[cdecker]

The meeting will take place on Monday 2020/02/03 on IRC #lightning-dev. It is open to the public.

Pull Request Review

• Single-option large channel proposal Single-option large channel proposal #596
• BOLT 7: be more aggressive about sending our own gossip. BOLT 7: be more aggressive about sending our own gossip. #684
• Bolt 1: Specify that extensions to existing messages must use TLV Bolt 1: Specify that extensions to existing messages must use TLV #714 (@t-bast)
• Gossip channel queries
  • BOLT7: reply_channel_range parameter BOLT7: reply_channel_range parameter #560
  • BOLT 7: clarify how to decode empty arrays BOLT 7: clarify how to decode empty arrays #729: this has been discussed on the PR and, given that empty byte arrays are not a valid zip-encoded payload despite specifying a zip-encoded payload, the PR has been withdrawn.
  • BOLT 7: clarify how to encode multiple reply_channel_range messages BOLT 7: clarify how to encode multiple reply_channel_range messages #730

Long Term Updates

• Current status of the trampoline routing proposal (@t-bast)
• Current state of the anchor output proposal (@joostjager )

Research

• How can we improve the gossip (gossip_queries_ex)? (@t-bast)

@niftynei has split out the collaborative construction of transactions from her dual-funding proposal as an intermediate step. I'd like to encourage everyone to participate in the discussions on the mailing list, and we will likely revisit that proposal during the 2020/02/17 meeting.

---

Post-Meeting notes:

Action items

• t-bast: implement proposed mitigation for Stuck channels because of small fee increase #728 and document that
• cdecker to change the featurebits to 18/19 and merge Single-option large channel proposal #596
• t-bast and araspitzu to brainstorm an advisory section in a new PR explaining how confirmations should scale with the funding amount
• cdecker to rebase and merge BOLT 7: be more aggressive about sending our own gossip. #684
• everyone to continue the discussion of Bolt 1: Specify that extensions to existing messages must use TLV #714 on GH
• everyone to discuss the minutiae of BOLT7: reply_channel_range parameter #560 and BOLT 7: clarify how to encode multiple reply_channel_range messages #730 on GH
• rusty to rework 560 and 730 to assume ascending order.
• everyone to keep an eye on the anchor outputs proposal and help wherever possible :-)

The full logs can be found here

[t-bast]

A suggestion of long-standing PRs that we could look at:

• Wumbo: Single-option large channel proposal #596
• Channel queries clarifications:
  • BOLT7: reply_channel_range parameter #560
  • BOLT 7: clarify how to decode empty arrays #729
  • BOLT 7: clarify how to encode multiple reply_channel_range messages #730
• A gossip fix CL, Eclair and LL all implemented but should be clarified at the spec level: BOLT 7: be more aggressive about sending our own gossip. #684

[t-bast]

And thanks again, I really think preparing an agenda before-hand help make progress during the meeting.

[cdecker]

Added #596 and #684 👍 I'll skim the others before committing to having them on the agenda :-)

[t-bast]

If I can also selfishly push for this one: #714

The currently optional upfront_shutdown_script is a pain for extensibility via TLV, the proposed solution (that needs feedback) to make it mandatory will potentially imply a small amount of work from every implementation and a release. Since this will take a bit of time, better to agree on the concept early ;)

[cdecker]

@Roasbeef I think you guys were working on anchor outputs, do you have anyone in mind that could give a brief summary of were we stand, what the open questions are, and how we can proceed/help with the proposal?

Otherwise we can postpone it to the 2020/03/17 meeting or later 🙂

[andrerfneves]

@cdecker do meetings happen on the #lightning-dev IRC channel? - (aka, would love to sit idly and read/watch the conversation and discussion)

[joachimneu]

Also, at what time will this meeting take place?

[t-bast]

This is detailed here: https://github.com/lightningnetwork/lightning-rfc/blob/master/CONTRIBUTING.md#Specification-Modification-Process

Spec meetings are bi-weekly on the #lighting-dev IRC channel. Everyone is welcome to join!

[t-bast]

Tonight the meeting is at 7pm UTC time.

[andrerfneves]

Thanks @t-bast!