Skip to content

Meeting Notes 2023 08 07

Jump to bottom
Elias Rohrer edited this page Aug 7, 2023 · 1 revision

##Releases

Roadmap Progress

  • Developer support
  • Payment protocols
    • 117 will be the big release for BOLT 12, lots of PRs out for review
    • Val to review Jeff’s outbound offer PR today
    • Jeff to continue review on the 3 dependent route blinding PRs
  • Language bindings
    • Autogenerated code should be more readable now. Lots of generator improvements
  • Taproot support
    • Spec side, gonna be talking to Jesse soon re: feasibility of nested FROST inside musig2. Not needing to nest is the benefit of not using nonces that zman proposed, so we want to see whether it’s really such a big benefit that it deserves further contemplation
  • Anchor outputs
    • As mentioned, we have a livestream and blog post on this but anchors is done
    • Last remaining item is figuring out how we can deal with the reserves and enforcing that from the LDK side. But that’s tbd
  • LSP
    • Nslaney: Zman put up some PRs for LSPS2, trying to solve for the prepayment probing use case
    • We’re still moving forward with LSPS2, talking on ways to mitigate without too much overhaul
  • VSS (Versioned Storage Service)
    • Working on LDK Node integration
    • Upgrading the KVStore interface in rust-lightning, and after that we are discussing whether it makes sense to have VSS integration in main LDK instead of LDK Node
  • LDK Node
    • Upgrade to 116 is ready
    • Looking to ship a new minor release this/next week bc there was a new release from BDK that broke LDK Node, would like to fix that sooner
    • On the fence about adding anchors, whether to wait for quality of life improvements that come with 117
    • Idea is that the default would be anchors. Q is how to expose it in a sane default way in the API, and how to communicate that the user needs to keep reserve funds that they shouldn’t spend
  • Dual funding channels
  • Splicing

Dependent Projects

  • VLS (https://gitlab.com/lightning-signer/validating-lightning-signer)
    • Working on a part 1/intermediate release of resource constrained signer
    • Also includes upgrading to CLN 24.08
    • Important new features: p2tr wallet support, 0-fee anchors
  • Synonym (https://github.com/synonymdev/ldk-node-js)
  • Mutiny
    • Tony: one of my big efforts on LDK side has been probing. Seeing a lot of payment failures, so started another LDK Sample based project that probes a bunch of destinations and ships the scorer. Payment success has improved a lot!
    • Any wallet will need scoring, so talked to steve about whether to open source scoring data or probing. Possibly integrating it into RGS
    • Probing strategy: targeting 1 million sats as probe amount, cut in half then double approach. Read from a list of pubkeys, then try to send out 1mil sat probes, then try to find an amount that does work if that fails. Mostly we take the path the scorer gives us, but we do check failures and do a bunch of different routes until we find a path that works, so if any failed we add that to the ignore list for the pathfinding algo
    • Could prob open source some LDK based probing as an example if anyone’s interested. Needs a lot of improvements/efficiency still
    • Would be cool to download 5 different LSP’s scoring data and merging them
    • Ben: our BDK wallet, we use esplora backend and got rate limited by mempool.space. Not sure if transaction-sync crate in LDK is at risk of rate limiting as well
    • Elias: we had a few reports of users getting rate limited, so i changed our intervals to ping them less often, and the BDK people also shipped some fixes that reduced the number of requests. Esplora will generate a lot of reqs though, generally. Existing issue
    • Mempool.space’s response is to
  • c=
    • No major updates
  • Lightspark
    • Cwaterson: have several PRs open. Including pending HTLCs is one, significant for being able to audit stuff. Review appreciated!
    • Pinged ken to look into VLS, them to sync up offline for that
  • Komodo DEX (https://github.com/KomodoPlatform/atomicDEX-API)
  • Lexe

Spec

  • 2022/07/31 meeting
    • Onion messages PR merged!
    • Jeff opened a PR to make offer QR codes smaller by allowing an SCID to be used optionally instead of a node id in blinded paths

Misc

  • review begs?
    • RGS server has a PR open by Arik #51 https://github.com/lightningdevkit/rapid-gossip-sync-server/pull/51
    • Reason to allow arbitrary logger types – need the tests to be able to check that a certain log output has been created. However, previously the logger was really opinionated and it was assumed that the logger was of a certain type specific to RGS
Clone this wiki locally