Lightning Specification Meeting 2020/02/17

[cdecker]

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

Pull Request Review

• Bolt 1: Specify that extensions to existing messages must use TLV Bolt 1: Specify that extensions to existing messages must use TLV #714
  • Shall we make TLV the only extension mechanism, and how do we work around non-mandatory fields that are not TLV fields (e.g., option_upfront_shutdown_script)
• BOLT 1: add networks to init message. BOLT 1: add networks to init message. #682
  • Interop testing done
  • c-lightning: Add network to init message ElementsProject/lightning#3300 and connectd: check all chain hashs of the network array in init ElementsProject/lightning#3371
  • Eclair: Add networks to init message ACINQ/eclair#1254)
• A home for BOLT A home for BOLT #738
  • @URoZYMP43wPs proposes publishing the spec as a gitbook on ln.dev (preview here)
• [ ] Reply channel range simplification Reply channel range simplification #737
  • Adds details to the spec which were interpreted differently by the implementations.
• [ ] BOLT11 additional and negative tests BOLT11 additional and negative tests #736
• Avoid stuck channels after fee increase Avoid stuck channels after fee increase with additional reserve #740
  • Add some additional constraints to the fee-paying party to guarantee the ability to add an HTLC even in the presence of a 2x feerate spike.

Long Term Updates

- [ ] Protocol testing framework (@rustyrussell). See the tools/ and tests/events directories in lightning-rfc-protocol-test for details.

• Poor man's rendez-vous routing (@t-bast). See mail by t-bast and gist for details. (Since this is a fresh proposal still in everybody's mind this moved up the list to minimize loss of context).

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.

- [ ] Current status of the trampoline routing proposal (@t-bast)
- [ ] How can we improve the gossip (gossip_queries_ex)? (@sstone )

---

Post-Meeting notes:

Action items

• t-bast: give reviewers a few more days and then merge Bolt 1: Specify that extensions to existing messages must use TLV #714
• rusty: get in touch with URoZYMP43wPs about the ln.dev hostname
• everyone: keep exploring solutions to Avoid stuck channels after fee increase with additional reserve #740
• everyone: review Anchor outputs #688 (comment) (anchor outputs)
• cdecker: explore full sphinx rendezvous solutions
• t-bast: iterate on decoys and poor-man's rendezvous route-blinding
• everyone: review https://gist.github.com/t-bast/9972bfe9523bb18395bdedb8dc691faf

The full logs can be found here

[t-bast]

Could we also look at #714 which is carrying over from last time? I updated the PR but didn't get reviews yet. I'm hoping that the first three reviews (#738, #737 and #736 could be done fairly quickly, but maybe I'm overly optimistic).

[darosior]

Maybe #682 too ?.. Since interop testing has already been done it shouldn't be long

[cdecker]

Ok, added both to the agenda, and I also added a brief summary of where we are with the various things.

[joostjager]

Short update on anchor format now that we've decided to not to symmetric csv (yet): #688 (comment)