-
Notifications
You must be signed in to change notification settings - Fork 367
Meeting Notes 2023 11 13
Elias Rohrer edited this page Nov 13, 2023
·
1 revision
- 0.0.119 (https://github.com/lightningdevkit/rust-lightning/milestone/37)
- Issue list is long atm, hasn’t been pruned yet
- Async signing is one of the big goals here
- Also more BOLT 12 support
- Devrandom: i have a PR 2635, so i want to be able to change the chan value and funding keys because i’m supporting splicing in VLS. the solution i had in the PR wasn’t super clean, but would be good to have some way to do that.
- Matt: was hoping to see what we did for splicing because more likely … i don’t think this solved the issue for LDK splicing clients, so was hesitant, specifically bc within one in-mem chan we have one in-mem signer, which supports multiple diff spliced versions, so we’ll probably need to pass the channel value.. We need a bigger api change in general here for splicing.
- 0.1 (https://github.com/lightningdevkit/rust-lightning/milestone/1)
- Developer support
- Jeff opened a PR to refactor chanman documentation. Conor and jeff have committed to make some improvements there on a weekly basis.
- Swift LDK node tutorial up: https://www.youtube.com/watch?v=rcU3LU6iZCs
- https://www.youtube.com/watch?v=093HUi34E_0&list=WL&index=17
- Payment protocols
- Trying to get more BOLT 12 support into 119
- Jeff has a PR open starting to support direct-connection, should go under review this week
- Val next route blinding PR close to merge. Hoping to support multi-hop blinded path receiving in 119, and full blinded forwarding support in 120
- Language bindings
- Nothing new here on the swift end
- Matt: we have early alpha of c# bindings! We should have an early tester this week too.
- Taproot support
- Arik: was able to rebase next TR PR. still revising it to make sense w the current codebase. Hoping to get some PRs in 119.
- There’s been some reshuffling of priorities so we may be deprioritizing TR after this for a couple months in favor of async payments
- Anchor outputs (DONE)
- RGS (Rapid Gossip Sync)
- Some bug fixes have been merged into the server as of saturday
- Recommend that people upgrade their RGS servers to the latest version
- It’s an edge case that’s fixed but still
- LSP
- Jcantrell: working on getting review for latest features such as MPP support and more follow-ups
- Plan to rename crate and move it
- VSS (Versioned Storage Service)
- Next step merged into LDK
- Working on client side encryption
- Some discussion over vec allocation
- After that, will go ahead with phase 1 launch
- LDK Node
- Aiming for the next release soon-ish
- Adding electrum support to the lightning-transaction-sync crate within LDK
- Dual funding channels + Splicing
- Dunxen and jurvis and wilmer are primarily working on this
- There’s a review club after this meeting touching on interactive tx construction portion of this. Recommend attending if you’re interested
- VLS (https://gitlab.com/lightning-signer/validating-lightning-signer)
- Devrandom prefers new meeting time. Ken neutral
- In terms of update, working on splicing. Have the 1 ask mentioned previously (https://github.com/lightningdevkit/rust-lightning/pull/2635)
- Our SoB person has been working on docker images
- Synonym (https://github.com/synonymdev/ldk-node-js)
- Matt: they were struggling w payment success rates, esp on mobile without probing. We did start snapshotting the netgraph off my node, which does some probing, and putting it on the rapidsync.lightningdevkit.org domain. So if anyone wants to test that, go for it, seems useful so far at least for dev purposes. Generating your own graph on mobile needs some alternate data source that’s probing/sending payments, and ideally that’s from a similar perspective of the netgraph.
- Mutiny (https://github.com/MutinyWallet)
- Ben: had a spike in force closes since moving to async storage. Need https://github.com/lightningdevkit/rust-lightning/pull/2721
- Matt: 2 issues here – iOS does some harebrained thing where it runs 2 clients at once, so splitbrain problem causes FCs. other problem is clients being offline for a long time, so https://github.com/lightningdevkit/rust-lightning/issues/2698 should help too. If there are FCs you’ve seen that aren’t explained by those 2 issues, we need to sync more.
- c=
- Prefers old meeting time
- Nick slaney: no major updates.
- Lightspark
- Alec: for now, there’s a lot going on, but no specific asks that i know of. Will take a poll of people’s preferred meeting time.
- 2023/11/06 (https://github.com/lightning/bolts/issues/1116)
- Some BOLT 12 retries discussion. We’re sticking with our strategy of firing off several invoice requests at the start and not bothering to retry
- Optimistic about coop close rewrite, should allow us to remove a whole class of FCs where we fail to negotiate fees. Would like to have that done when lnd ships it.
- review begs?