-
Notifications
You must be signed in to change notification settings - Fork 371
Meeting Notes 2023 01 10
Elias Rohrer edited this page Jan 10, 2023
·
3 revisions
- 0.0.113 (https://github.com/lightningdevkit/rust-lightning/milestone/30)
- Still an upstream PR waiting on review
- 0.0.114 (https://github.com/lightningdevkit/rust-lightning/milestone/31)
- Bunch of stuff in-flight that made a lot of progress.
- Hopefully will land in 114
- Should be able to make pretty quick progress on stuff this week
- Viktor's 1507 around changing the locking in channelmanager. Would like to land that early this week because it causes conflicts.
- Viktor: i still have a strange windows lockorder violation here. Going to try to solve it, but if i can't tonight i'd appreciate if someone could take a look
- Matt: will take a look soon
- Bolt 12 invoice stuff, maybe make them public? We need a fuzzer. Not super useful without onion messages but could get it moving.
- Payment retries in channelmanager
- Should be a pretty huge release even with stuff we're gonna land this week. And a bunch of small stuff. So should probably start getting to work on the small issues tagged 114
- 0.1 (https://github.com/lightningdevkit/rust-lightning/milestone/1)
See Dependent Projects for per-LDK-project priorities
- Developer support
- We have a stackexchange set up by murch https://bitcoin.meta.stackexchange.com/questions/1155/monthly-topic-challenge-lets-ask-about-lightning-development-kit
- It would be nice if this month, we could get some questions asked & answered over there
- Bit weird since discord is our main hub for support. But good to provide the option to ask there too. Helps us build up a static library of FAQs so people can self-triage
- Also a bounty that was put out by a fediment dev, he set up a 6mil sat bounty
- https://gist.github.com/elsirion/8c1453fe3120dc3f7ba843a6a062dc9e
- https://github.com/lightningdevkit/rust-lightning/issues/1385
- Put up sensei case study on the LDK website too. Thanks jcantrell for writing that
- If anyone else in this call is interested in writing a case study of their ldk usage, let Conor know. Nothing major, a simple 1-page would always be welcome
- Payment protocols
- Offers PRs being merged at a clip
- Payment retries PR to be updated today
- Need payment retries in channelmanager for trampoline, which we need for async payments so the sender's LSP can retry on the sender's behalf
- Language bindings
- Not a ton of updates here
- Taproot support
- Have a PR that needs a bit of commit restructuring.
- Looking good on spec side with laolu
- Anchor outputs
- Good progress, major stuff merged. Still behind a feature flag for now.
- Right now, the PR next in the queue is supporting opening and accepting channels with anchors. Hoping to land this week, then i'll shift to working on the event handler that is consuming those events for users
- LSP
- Synonym:
- Holidays disrupted a bit, but currently starting to implement the channel request spec (LSPS1)
- Hoping to see breez implement it as well, so we can have our wallet users choose their LSP instead of forcing them to use ours. Solving some of our unique issues where we can't sell to US users, they must choose another LSP
- Worked on the marketplace spec, pretty quick/simple. It should evolve once someone in the group implements it, but still a bit early. We would try to look at it ourselves when we try to use liquidity ads
- Started work on splicing spec
- Have some rough spec started, early days though.
- Another area of interest is making LN more censorship-resistant.
- Synonym:
- VSS (Versioned Storage Service)
- Looking to create a PR for the impl, several in the pipeline as well
- LDK Node
- First update - project was previously known as LdkLite, now named LDK Node.
- Quite a bit of progress: transaction sync PR to upstream against esplora upstream could be considered safe now.
- Electrum version is in the pipeline too, started working on that, to be a follow-up PR
- Then i improved integration bdk on-chain wallet. Whenever a channel is closed, it'll now go back to outputs managed by bdk wallet. No extra spend there.
- Progress on UniFFI bindings, but still pending because it's tricky. Bindings generation works, but still need some glue code for swift bindings to build/wrap in proper packages. But there has been some progress - bitcoin savior announced he made progress on flutter bindings for LDK Node.
- Dual funding channels (new)
- Dunxen: Jeff and I are meeting to discuss the InteractiveTxConstructor which overlaps with splicing
- Splicing
- VLS (https://gitlab.com/lightning-signer/validating-lightning-signer)
- Main thing we want is BOLT 12 and VSS.
- Encrypted values that are stored. Initial heartbeat code up and working. Added xpubs to our allowlist format.
- Progress on CLN upstream refactors needed
- Fixing bugs for MVP1 milestone
- Sensei (https://github.com/L2-Technology/sensei)
- Synonym (https://github.com/synonymdev/ldk-node-js)
- Looking forward to routing working, inside of bitkit
- Interested in splicing
- Interested in async payments + trampoline routing
- Possibly interested in liquidity ads/peerswap
- Interested in some FOSS full node impls we can pick up for LDK
- Steve: curious re: running ldk in a server - would you want the full ldk api, and if so, which language? If not, we're developing LdkNode focused on mobile rn, but it could be a project in the future to configure it for servers with an rpc api.
- Specific interest is the LSP use case. The spec API.
- As far as mobile, already built our own react native LDK mobile node. But if LDK Node is better, we'd consider it, but we're likely too deep in our own implementation
- Steve: not aware of ldk pathfinding issues. More details?
- Jay: we had some unreliability with routing payments for mobile. May have had to do with starting with a blank scorer, but it seemed to take multiple hops where it should've just taken 1 hop through the LSP
- Matt: would really like to better understand this. Please follow up on discord with examples of paths that it took that it shouldn't have, with logs. It's straight dijkstra's, should just pick the best total score path, where the score is the fee + whatever the scoring penalty is. It also penalizes per-hop
- Jay: i'll send some specific examples.
- Komodo DEX (https://github.com/KomodoPlatform/atomicDEX-API)
- Lexe
- We've been working with bdk. Lots of sync stuff that we need to rewrite as async. Everything on the LDK side is looking good.
- Tony
- Looking for async traits on our side
- 2023/01/02 (https://github.com/lightning/bolts/issues/1048)
- review begs?