Meeting Notes 2020 11 16
Chair: @ariard
arik-so TheBlueMatt ariard moneyball devrandom valentinewallace jkczyz
MPP (#563) Fuzzer updates lightning-block-source ldk-nodejs code generation Signer "phase 2" API (#742) node-sample lightning-persister
0.0.12 is almost done, the last piece to land is valentinewallace's #611 and TheBlueMatt's #749.
There is a pending debate on #742 on a "functional-vs-oop" to isolate cleanly onchain transactions naming ("broadcaster/countersignatory") from offchain channel directions ("holder/counterparty"). TheBlueMatt favors a functional approach. ariard a functional one after PR discussions with devrandom. The debate is left to be solved after a review round on the PR by TheBlueMatt.
TheBlueMatt would like to explore symbolic execution fuzzing in the future. Also noting on mutation testing " mutagen isn't a fan of the idea of exiting with a failure if there is missing coverage instead noting that mutation is really a coverage generator not so much a unit test generator...which is fair, but I'm not aware of any way to get mutagen output to show up in codecov or so." (TheBlueMatt).
The next step after node-sample workable and language bindings is to write down "look how everything you can do with LDK" dev docs. jkczyz pointed it would be good to agree first on information hierarchical outline, identifying user journeys and focus on critical ones.
Folks somehow agree that a 0.0.13 should incorporate gossips and MPP.
devrandom and ariard discussed about the next key-management steps. One unsolved question is about the bumping utxo anchor output API if it should be a layer-1 operation (outside the keyinterface) or a layer-2 one. Maybe "Don't sign this CPFP for this commitment because HTLC aren't economically interesting" policy would make sense to make bumping utxo signing a layer-2 operation. A clean separation between layer-1/layer-2 operation in itself is a good question.
On persistence, valentincewallace is working on a channelmanager PR. Upcoming, are route graph persistence, see #752 for tracking.
It turns out the team had issues coordinating on complex topics (i.e generic channels, autopilot infrastructure, ...) . Sharing projects rights to everyone might be a solution with informal owner could be great.
Fee leak Offers Route blinding
Coming up with your nice "what-to-build-with-LDK" ideas for the next meeting. Sharing backlogs yet-to-be-done to give visibility to others.
646 611 742