Skip to content

Meeting Notes 2024 01 08

Jump to bottom
Elias Rohrer edited this page Feb 5, 2024 · 1 revision

Releases

  • 0.0.119 (https://github.com/lightningdevkit/rust-lightning/milestone/37)
    • Bindings coming soon
    • Might skip bindings for this irelease in favor of getting a quick 120 out
  • 0.0.120 (https://github.com/lightningdevkit/rust-lightning/milestone/38)
    • Some issues have cropped up with zero conf/anchors/channel opens where there’s a reachable unwrap. So we want to get this out sooner rather than later.
      • Pretty important bug to fix, we saw it in the wild
      • Matt has a bunch of fuzzer updates out that would have caught this
      • Impacts anchors/zeroconf users
      • More of a DoS concern than a funds-loss concern, and obv zero-conf users are likely to have semi-trusted counterparties that probably won’t DoS them
      • Dom: forking+fixing this is easy, we’re eager to get in the features of 119. Not too big a deal from our PoV, we were not expecting the rushed fix.
    • Async signing is also 1 PR away. May be we can land it in the next week or so.
    • Some other contenders for this release too
    • Matt: Let’s try to get this out this week or next
    • Jeff: we could cut it today
    • Matt: yeah, open to that too
    • Steve: mutiny wants the time fix, which is another reason for a quick release.
    • We could also get in some tail-end offers stuff into 120
  • 0.1 (https://github.com/lightningdevkit/rust-lightning/milestone/1)

Roadmap Progress

  • Developer support
  • Payment protocols
    • 119 has beta bolt12 support and is ready for user integration! 🎉
    • Some tail end things that jeff and I are working on/getting help with
      • if people want to help, there’s a lot of stuff on #1970 issue. Talk to jeff to help with this
    • Async payments and trampoline work should be commencing.
  • Language bindings
    • Some work on 119 binding but no concrete update on release timeline
  • Trampoline
  • Taproot support
    • Deprioritized in favor of trampoline
  • Anchor outputs (DONE)
    • Wilmer started working on docs improvements prior to the new year, work will continue
  • RGS (Rapid Gossip Sync)
    • Seems quite stable, no complaints
    • Working on a strategy for releases.
  • LSP
    • Elias: a lot of restructuring and api updates on the lightning-liquidity client. I recently started LDK Node integration and have a branch that is almost ready with the client side flow.
      • Upstreamed a lot of changes along the way
    • Server side persistence is missing. Elias may pick this up in a bit.
  • VSS (Versioned Storage Service)
    • Landed some PRs
    • One open for retry mechanism, and another on client side integrating previous PRs
    • We’ll consider exposing experimental branch in LDK Node for this
  • LDK Node
    • Recently the 0.2 release shipped
      • Some stability improvements
    • Liquidity client integration for LSPS2 and VSS integration are progressing well.
    • Offers integration is planned to be soon too, and catching up on new LDK features in general
  • Dual funding channels
    • Dunxen: working on pre-factor PRs, such as removing outpoint_to_id method.
  • Splicing
    • Dunxen: meeting with opt21 about splicing soon
    • Wilmer: hoping to make a lot of splicing progress this quarter. Stay tuned to #splicing channel
      • My goal is to get all the offchain stuff happening this quarter. It’s a lot.
      • I have a quiescence PR coming up soon.
      • Got interactive tx constructor which got some review recently soon

Dependent Projects

  • VLS (https://gitlab.com/lightning-signer/validating-lightning-signer)
    • Been busy with DF and splicing
    • Would benefit from an explicit notification from a node that a channel may be forgotten forever
    • What happens is we’ll get a call “please unilaterally close this channel” and we won’t know about the channel, which is bad
    • Dom: ken makes a good point because for us, knowing a safe time to get rid of monitors helps from an operational point of view. We have them hanging around forever and that leads to long startup times and high i/o on startup. We plan to do something about that and can infer when it’s safe to archive, but the ideal would be an LDK event that says we’re finished.
  • Synonym (https://github.com/synonymdev/ldk-node-js)
  • Mutiny (https://github.com/MutinyWallet)
  • c=
    • Panic mentioned for 120 release was our big topic
    • Jcantrell: i would like some review on a tbd-lightning PR that seems a bit dangerous https://github.com/tbdeng/tbd-lightning/pull/737
    • Elias will take a look
    • Willem: you all were talking about moving all state into channel monitors. How’s that going?
    • Jeff: it’s a long term plan
    • Matt: sadly we haven’t made forward progress towards that. We’ve made progress on async persistence, which helps, but the long term changes are still tbd.
  • Lightspark

Spec

N/A

Misc

review begs?

Clone this wiki locally