Skip to content

Meeting Notes 2024 01 22

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

Releases

Roadmap Progress

  • Developer support
    • Conor: couple small things, added some sample code for creating a custom keys manager for people who want their channel closes go to an onchain wallet.
    • https://github.com/lightningdevkit/lightningdevkit.org/pull/245#pullrequestreview-1836014791
    • Bitkit team has used some of this code
    • Also, summer of bitcoin is coming up again soon. Applications open Feb 1, so will be spending time learning more about how last year went.
    • Am curious to hear people’s thoughts on the LDK project since we had quite a few mentors last year. Positive? Do you plan to mentor again?
    • Ken: we had 2 mentees, worked quite well. One joined on an ongoing basis. So we’ll definitely do more. One comment: the investment in identifying the project areas/request for proposals is well spent. The one that worked out is the one we spent more time thinking about and defined better.
    • Jeff: We had some mentees not meet expectations, and I think we could’ve benefited from spending more time on the description.
    • Elias output sweeper project may be relevant to custom keysmanager example code
  • Payment protocols
    • Got a bunch of important BOLT 12 stuff in 120
    • Val working on adapting BOLT 12 for async payments
    • Jeff put out a doc for using a point-of-sale that doesn’t have channels but manages accounting using BOLT 12
  • Language bindings
    • We’re gonna skip language bindings for 120 since we’ll get 121 out later today/tmrw
  • Trampoline
    • Arik: we’ll likely go with t-bast’s proposal, there are some issues with multiple trampoline nodes being included by the sender.
  • Taproot support
  • Anchor outputs (DONE)
    • Wilmer: there will be updates shortly, just need to finish up some work
    • Let’s keep this topic on the agenda as there will be things relevant to users integrating anchors
  • RGS (Rapid Gossip Sync)
    • Nothing customers are clambering for atm, we can remove this from the agenda
    • One thing we’ve been working on for RGS is encoding everything with gzip. I don’t know how people are doing the decompression locally. Generally in browsers things sent with CONTENT-ENCODING can be decoded natively.
  • LSP
    • Elias: lsp integration in ldk node is working so far. Just a bit held off bc there are some updates to lightning-liquidity crate that are almost shipped. It recently dropped versioning support, and is on par with the spec.
  • VSS (Versioned Storage Service)
  • LDK Node
    • Apart from LSP updates above, not much.
    • Elias started looking into anchors integration again.
    • Async event handling also in progress. It’s an easy review if someone’s interested.
  • Dual funding channels
    • No updates except dunxen is looking for review on his prefactor PRs
  • Splicing
    • Wilmer: we hit a minor setback needing to refactor something in channelmanager. Once that roadblock is done, we’ll keep pushing on quiescence. If you want more in depth updates on splicing, feel free to join our weekly calls on thursdays 9am PST. we also post notes.
  • Interactive tx constructor PR needs review but also has pending review to be addressed

Dependent Projects

  • VLS (https://gitlab.com/lightning-signer/validating-lightning-signer)
    • Ken: we need an explicit revoke holder commitment tx API. we hit an issue where we released the secret that revoked an older commitment version. Problem is when VLS is synchronizing with a node, it’s possible to get them out of sync. So we would get the validate, release the secret so we can’t sign it anymore, but then the node crashed and when it came back up it gave us a different commitment to validate. So what used to be one api call needs to be 2.
  • Synonym (https://github.com/synonymdev/ldk-node-js)
    • Waiting on latest language bindings
  • Mutiny (https://github.com/MutinyWallet)
    • Nothing major, we’ve been on 118 for a while.
    • One issue we have now is we added fediment stuff, and they’re using LDK’s lightning-invoice crate in 118. So we have to do a bunch of conversions back and forth if we wanna update. So idk if there’s an easier way to solve that…
    • We call create_invoice_from_channelmanager atm. Maybe we throw that out and write our own invoice builder
    • Matt: no great answer, may have to encode the invoice to a string and decode it again.
  • c=
    • Nick: nothing major, we shared some potential roadmap priorities with the spiral team and we’re gonna meet this week about it
  • Lightspark
    • Wilmer meeting with them today regarding async signing
  • They have some open PRs unrelated to async signing that we should keep moving forward on

Spec

Misc

  • review begs?
Clone this wiki locally