Mutiny PPPs: Week 5
We had a fun monday whiteboard session (pictured) where we mapped out all the work we have left.
We worked at all layers of the stack this week, but we didn't quite make them all "kiss" yet. A ton of frontend screens are stubbed out, some major new LDK components landed, and we wrote dummy functions that the frontend will eventually use to talk to the node implementation.
It's a little down to the wire but still hopeful we can get something working by submission time.
Progress ✅
-
A bunch of blockchain stuff for LDK https://github.com/BitcoinDevShop/mutiny-web-poc/pull/42
-
Stub out front end apis https://github.com/BitcoinDevShop/mutiny-web-poc/pull/49
-
Option for 12 word seeds https://github.com/BitcoinDevShop/mutiny-web-poc/pull/54
-
Sync LDK nodes https://github.com/BitcoinDevShop/mutiny-web-poc/pull/55
-
Make the frontend (but it doesn't do anything yet) https://github.com/BitcoinDevShop/mutiny-web-poc/pull/56
-
Fix cache size error (our WASM bundle is kind of large!) https://github.com/BitcoinDevShop/mutiny-web-poc/pull/58
-
LDK event handler almost ready (where a lot of the magic happens!) https://github.com/BitcoinDevShop/mutiny-web-poc/pull/57
-
Landed LDK ChannelManager https://github.com/BitcoinDevShop/mutiny-web-poc/pull/40
Problems ✋
-
We're running out of time and have a lot left to do
-
Vectors apparently don't play very nice in Rust WASM (serialize an invoice over to JS? Easy! An array of invoices? Horror!) https://github.com/rustwasm/wasm-bindgen/issues/111
-
Errors aren't very ergonomic to write yet and it's all Paul's fault
-
Somehow managed to break scrolling on the frontend. CSS is hard.
Plans 📆
-
Finish the rest of the LDK components: https://github.com/BitcoinDevShop/mutiny-web-poc/issues/48, https://github.com/BitcoinDevShop/mutiny-web-poc/issues/47, https://github.com/BitcoinDevShop/mutiny-web-poc/issues/46
-
Wire up the stubbed out frontend API surface to operate the LDK / BDK nodes and on-chain wallet
-
Wire up the frontend to use that API
-
Any time polishing we can afford (nice frontend errors? easy performance optimizations? QR code scanner?)
-
Make a video explaining Mutiny, presuming we have a Mutiny to demo