rust-lightning

mirror of https://github.com/lightningdevkit/rust-lightning.git synced 2024-11-19 01:43:27 +01:00

Table of Contents

Releases
Roadmap Progress
Dependent Projects
Spec
Misc

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Note: our meetings will be temporarily moving to Google Meet due to Jitsi bugginess. Will check back on Jitsi later in the year.

Note: meeting time will be changing in some timezones next week to be 1 hour earlier for a lot of people. Check out the LDK meeting calendar.

Releases

0.0.118 (https://github.com/lightningdevkit/rust-lightning/milestone/36)
- Swift bindings are out! Java will be out today.
0.0.119 (https://github.com/lightningdevkit/rust-lightning/milestone/37)
- Big goal is to get more refined Offers support
- Another is async signing
- We have a potential MSRV bump to 1.63
- The thing that was holding us back was we had users that had an old glibc using the java bindings. 118 java bindings will use a newer glibc, and we are gonna wait and see if that causes problems for anyone. If it doesn’t, we’ll presumably bump MSRV
0.1 (https://github.com/lightningdevkit/rust-lightning/milestone/1)

Roadmap Progress

Developer support
Payment protocols
- 118 shipped alpha offers support! Yay
- Lots more improvements coming in 119, such as hopefully multi hop blinded path support
- Had ben from mutiny do a test with offers, which was nice to see initial success
- We were thinking it’d be helpful if CLN were to do the auto-connect for you if it has to route a payment and it’s from an LSP client peer. In talks with CLN about this.
- Jeff: Re: direct connect, thinking about LDK end – level of network connections lives outside of core RL. wondering if we can surface an event “peer connection required” or something like that.
- Matt: would be tricky w timing since events are processed async but messages are quicker. This seems like it should live in the OM router, which knows live when it needs to have a connection to a peer. We could have a callback that gets passed to default OM router, the user gives a callback that says “when you call this, i’ll connect to this peer”
- Steve: we all know B12 adoption is important, so happy it’s in a release so i can push adoption more in the ecosystem (started w/ mutiny). CLN and Breez SDK – i’d expect them as well to adopt it. In parallel, the LNDK project, which ben is also running (thanks ben) will at least be an option for LND users to send, which would really help. Hopefully a lot of users will build enough momentum that LND proper will integrate B12.
Language bindings
- Swift bindings are out! Java will be out today.
Taproot support
- Arik: busy rebasing.
- Spec status: we have several spec proposals now, one is just describing the channels, separately the gossip spec, and the main one “simple TR chans” seems ready to go w/ minor activity. Gossip is still further out, elle has been spearheading. Should have more time to dedicate to helping w that soon.
Anchor outputs (DONE)
- Still working on the docs.
- Wilmer worked w tnull a couple weeks back to add anchors to LDK Node, but still WIP
LSP
- Jcantrell: tnull and i and others were able to get LSPS2 stuff merged this morning!
- It’s an early alpha. It works, C= has an e2e integration test that uses it, but it still has a lot of work to be done to be prod ready. Some edge cases to handle + missing pieces in spec.
- From here my plan is to go update the mutiny and c= impls to match the latest version of the library, then go back to work on the library.
VSS (Versioned Storage Service)
- Gursharan: Updated to 118
- Now have to rebase PRs
LDK Node
- 117 upgrade finished, 118 upgrade is WIP. tnull to return to that this week.
- A bunch of PRs that should be close to merge as well
- Once these land, will cut the next release and experiment with integrating the LSP client support and first steps towards integrating electrum syncing
- Offers support also will be looked into post-118 upgrade
Dual funding + Splicing
- Dunxen has been integrating interactive tx construction branch. He’s been able to get some channels open, has it working up to but not including RBF. going smoothly so far. Getting ready to do interop testing with other implementations. Once that happens, then we’ll need to do RBF, which plays a part in splicing.
- Regarding splicing, no work has happened yet, waiting on interactive tx construction PR to get some review (it’s pretty much ready w one bugfix outstanding and needs better test coverage).
- Wilmer has WIP branch for quiescence, which is dependent on the channel state enum refactor open, since we’ll be adding a few new states for quiescence, and the channel state flags aren’t nice to work with right now.
- Hoping to get quiescence in 119 and to get interactive tx close at least for 119
RGS
- Arik: we’ve had this bad bug, pain to figure out. Nature of it was we had interlaced channel ups that were forcing us to present outdated data to users. Now fixed! Now trying to replicate another bug w incremental updates resulting in log “no channel to provide update to.” still investigating, but I think once my updated client has run for 6 days or a week it should be easier.
- Tony: i think things have been stable for us since we did full-syncs-only. Haven’t noticed any “insufficient fee” errors anymore.
- Thanks to Tony and all users for their patience on these bugs.

Dependent Projects

VLS (https://gitlab.com/lightning-signer/validating-lightning-signer)
- Busy with splicing and DF stuff.
- Busy with docker container stuff, so we can run VLS services in docker. Then we’ll partition them in useful groups.
Synonym (https://github.com/synonymdev/ldk-node-js)
Mutiny
- Ben: we might have a bug, it seems like we’re getting chanmon/chanman stuff out of sync more often since using async storage. Could be on our end but we’re trying to figure that out atm.
c=
- 118 is deployed! We’re migrating to the new persister. Life is good.
Lightspark
- Waterson: we fast forwarded to 118 and are running w that in our dev setup. Wilmer’s been helping a lot, we’re working on async signer atm. There’re 2 PRs for that. One is close to merge. Other one is more involved, with both PRs landed all operations can be done for signers that sign async. We’re running w these PRs in our test environment, seems to be working. Using an old version of LND as our counterparty, under some stress tests we see LND locking up. Wilmer suggested that’s due to using an old LND version so i’m upgrading that.
- Would love to get eyes on the 2 outstanding PRs

Spec

2023/10/23 meeting
- A few things we should start working on, some shutdown stuff.

Misc

review begs?