Skip to content

Meeting Notes 2024 03 18

Elias Rohrer edited this page Mar 18, 2024 · 1 revision

Releases

Roadmap Progress

  • Language bindings
    • There will be a minor release out for java, and some fixes for c#
  • Developer support
    • LDK hackathon last wednesday-friday at advancing bitcoin!
    • Conor: Worthwhile experience
    • In the end, had 14 submissions
    • Flow of hackathon: Spent the morning giving a high level overview of LDK -> LDK Node workshop -> sponsors presenting services -> hackathon
    • Probably could tighten up presentation of range of services available
    • Participants were successfully using LSPs, setting up BOLT 12. Few pain points – promising
    • 1-2 projects were focusing on their project and UX experience and wasn’t til the morning of day 3 that they actually started playing with LDK Node, and it Just Worked for them, which was good. We want devs to be able to focus on their product experience
    • Azz (hackathon winner):
      • i didn’t get onto messing around w LDK Node until the last day, but from my end, I wasn’t doing my usual thing which is more in depth lightning stuff. So this was relatively easy for me. Morning of last day, i built an ecash mint with LDK Node. not to the proper cashu specification, but a proof of concept of a p2p marketplace platform where you have a client-server relationship, but the idea is that the clients can buy/sell/list items to each other and pay each other via an ecash mint (you can transfer between users on the platform w/o fees). Also whole thing was e2e encrypted, so server can’t see what you’re buying/selling. So the first few days were building all the cryptography out.
      • We were using MutinyNet
      • Nothing to say for LDK at the end other than it was great/simple to use, and took maybe tops 30 minutes to implement it as the backend for the ecash mint
      • Demo: added LDK Node into the main server on the platform. All Rust, so no FFI bindings. Then built another small CLI tool to pay an invoice generated by the server. That was it!
      • One thing i ran into: tried to pay a small amount at the end, failed, obscure issue. Easy to solve once i talked to elias.
    • Esraa (2nd place hackathon):
      • What i did was build a desktop trusted node, and a mobile app that the trusted node could create multiple sub-accounts, using bolt 12.
      • Trusted node had access to LSP.
      • Idea was to give that node ability to manage liquidity for all the sub-accounts
      • Mobile node could just connect to trusted node to receive/send
      • Also option to do self-custodial, but didn’t get a chance to fully develop that at the hackathon
      • I already had a bit of experience with LDK Node, but at the hackathon B12/LSP stuff was not there yet, that was the main thing to work on, doing the sub-accounts based on the B12 stuff.
      • Experience with LDK Node in general was great. The fact that elias was there, every problem that we had he knew and had a patch ready.
      • Fun!
    • Nslaney: cool to see all the people there hacking on ldk!
    • Tnull: was a blast! Lots of good feedback on LDK Node.
  • Payment protocols
    • Jeff: was helping elias last week getting bolt 12 into LDK Node, esp with invoice notification. Through some talk w matt, instead of a dedicated event, have the info come when the HTLC comes. So i’ll be working on that this week or next. Mostly otherwise working on compact representation of blinded paths, should have something ready in a couple days.
    • Val: get bolt 12 language bindings-friendly interface in, as mentioned. Now working on onion message store-and-forward PR for async payments. got another async payments PR up as well.
  • Trampoline
    • Arik: would like to get 2756 landed asap, incorporated a bunch of other feedback.
  • Taproot support
  • Anchor outputs (DONE)
  • LSP
    • A few feature improvements under way
    • Looking into server-side persistence soon
  • VSS (Versioned Storage Service)
    • Willem: we’re updating the VSS client to be able to authenticate with LNURL-auth. Originally based on mutiny’s implementation, so i simplified our server side last week and am going to simplify the client side PR I open this week.
  • LDK Node
    • For the hackathon, we put up a development branch that included bolt 12 + anchors support, and a bunch of smaller features/bugfixes that haven’t been released.
    • We’ll be working on getting these things into main, it’s mostly blocked on the next LDK release atm
  • Dual funding channels
    • Interactive tx construction PR is almost ready to merge. That will open us up to moving forward on DF + splicing
  • Splicing

Dependent Projects

Spec meeting

Misc

  • Review club topic (Esraa)
    • We want more engagement here. Would be nice to get more feedback on the issue github.com/lightningdevkit/ldk-review-club/issues/31
    • Want to understand why people find it hard to participate
  • Also another issue in the rust-lightning repo about the integration of payjoin. We want to integrate payjoin, we have an open PR in LDK Node but there’s a couple of things that need discussion/decision making, mainly where we want to implement some of the stuff. Do we want to enable the functionality not only for LDK Node? Do we want it for the mutiny node, others?
  • Sharma: been working on peer storage for LDK.
    • Now writing code for inserting our peer storage into the peers that we have a channel with
    • Last time you advised me on how to encrypt the storage. Can you reiterate..?
    • Jeff: i was mentioning using something called the expanded key in ChannelManager. That key has been expanded to work for offers too.
Clone this wiki locally