-
Notifications
You must be signed in to change notification settings - Fork 367
Meeting Notes 2022 08 22
Elias Rohrer edited this page Aug 22, 2022
·
3 revisions
- 0.0.111 (https://github.com/lightningdevkit/rust-lightning/milestone/28)
- Matt: so it’s been 3 weeks since the last one, we try to do releases monthly. That said, not a ton currently there for a release. A lot of work lately has been stuff like OMs, bolt12, that’s not done yet. We’ve made good progress but it’s gonna be a while before we land enough stuff that we’re shipping it and it’s useful for end users. There are still a number of bugfix-y things around balances and async persistence. Would love more progress there, not in a huge rush to ship what we have now for 111, so i kinda was just letting us make a little more progress. There are a number of nice things, once we land a few more things, i think it would make sense to cut a release and land a bunchof stuff tagged 111. If it slips to a month and a half for this release, that’s fine, i don’t see an issue with that. Will reconsider in a week or so.
- Developer support
- Some churn on website design, architecture
- Payment protocols
- Slow and steady progress here
- OM PRs in review, a few more planned
- Encoding stuff in progress, lots of spec evolution there too
- Stitching together tlv streams and not having to repeat the code
- OMs: how confident are we that the format there is final? If we hit merge, do some testing with eclair and CLN? Or is the bolt PR still a ways away, but tha
- Need to make blinded path encoding the same across reply path and encoding. And adding a byte to the OM version of it. I think rusty was thinking he wants everything finalized before their next release (<2 mo away)
- Missing a few things to add the test vector, but if we test with eclair/cln that’s fine
- Val to give a review for readability/comprehensibility of the spec
- Language bindings
- Jurvis to look into BW issues today
- J: have a couple of ideas here. Working w/ cocoapods
- rapid graph sync
- Almost done here!
- Taproot support
- Feature negotiation for taproot working
- Channel open is almost there
- Anchor outputs
- Very close, cleaning up some final things so i should def have sth up this week
- LSP
- John Carvalho: Not sure we all agree on how to proceed
- Simplest place to start: min info required for someone to have a listing on the marketplace (terms etc of a channel sale)
- Some people wanna frame it as a channel sale, w bids and asks
- I differ: convo made me appreciate liquidity ads more than sth like Pool, but still up in the air
- Someone from the ldk group, please try to chime in on telegram or the next call
- Matt: anything relevant to ldk specifically there? Sounded like the convo was stuff around how to format things that don’t impact the LN node.
- Nick slainey: https://github.com/BitcoinAndLightningLayerSpecs/meetings/blob/main/2022-08-17.md
- JC: on a technical level, no nothing specific to ldk
- My q: does ldk have any feelings as far as supporting sth like liquidity ads or creating sth like Pool? Any thoughts?
- We will move onto other lsp related services after this project, so may become relevant later, e.g. how watchtowers fit in.
- Steve: async payments
- JC: def interested in that. And peerswap
- VLS (https://gitlab.com/lightning-signer/validating-lightning-signer)
- Ken sedgwick: working w stackworks, sorting out feature config, dependencies, how debugging works… so that’s ongoing and we’re appreciative of their input
- Been tracking cln’s v12 release, buncha release candidates, found some stuff.
- Devrandom added velocity controls, have an initial version of that
- Ken sedgwick: working w stackworks, sorting out feature config, dependencies, how debugging works… so that’s ongoing and we’re appreciative of their input
- Sensei (https://github.com/L2-Technology/sensei)
- Synonym (https://github.com/synonymdev/ldk-node-js)
- Got on latest ldk framework
- WSP (wallet service provider)
- Gursharan: for context, we are starting a storage project for the wallet providers.
- https://docs.google.com/document/d/1DfV7m2fBAjehZLMe_g9eACUkKFuNF2er7Q6tK8bkrv8/edit?usp=sharing
- Steve: every wallet dev needs a storage solution. In addition, we wanna support multi device sync. blockstream/GL may be building their own solution here. There’s potential for collaboration. In the future, someone who isn’t using GL will likely need sth like this as well
- 1014 we need to do
- BOLT12/OMs: rusty has been implementing a lot of changes here from our feedback. Implementations seem to be driving forward with this
- review begs?