-
Notifications
You must be signed in to change notification settings - Fork 366
Meeting Notes 2020 10 05
Chair: @ariard
arik-so naumenkogs devrandom TheBlueMatt ariard valentinewallace jkczyz moneyball sr-gi Ken Sedgwick
ChannelData Persister (#681) Signer "phase 2" API (#723) LDK java bindings LDK wasm bindings Lightning-signer reference implemention MPP Routing (#646) Anchor outputs (#642/#725/#726)
naumenkogs is looking to work on channel scoring/autopilot post MPP. Before doing any automatic channel management, basic data tracking about channels is necessary (uptime, flapiness, profitibality, activity, peer, balance, volume, channel age)
Refactoring HolderCommitmentTransaction, only storing new/per-tx data in this struct, as motivated by devrandom work around signer API modifications.
Finalizing the 0.0.12 release (https://github.com/rust-bitcoin/rust-lightning/milestone/11), mostly landing #681 and few other bug fixes.
A sample node with the following components is the highest priority: chain data, on-chain UTXO management, on-chain transaction broadcasting, storage mapping, networking mapping, source of randomness, LN routing, fee-estimation.
moneyball proposed the following LDK dev onboarding process :
- "download" the LDK
- follow the readme to build and run the sample node (bonus: have eye of satoshi watchtower running too)
- browse the sample code to understand how it works
- read dev docs to understand how it works
- bonus: example code written in swift, javascript, java
- start modifying and tinkering
- integrate with an existing wallet for proof of concept
It sounds like potential users prefer good demo code over exhaustive manual. A walking through tutorial Learn LDK has been proposed by jczyz. TheBlueMatt underscored the needs for better module-level docs. Graphical representations like diagrams should also be added (Ken Sedgwick suggestion about diagrams.net)
681 ; 653 ; 646