Next steps

[Evanfeenstra]

hardware

• LED responding to setup steps, and changing policy from frontend
• "reset" mode by connecting the two pins on the hardware.
  • connect for 10 seconds, the LED should blink yellow.
  • remove and reconnect and the Wifi creds are cleared
  • setup via app mode to accept new wifi creds only (not change the seed)
• running against full VLS testing suite
• optimization (speed)
• bug in updating allowlist on the fly when using a BackupPersister. ThreadMemoPersister panics with "not in persister context"

broker

• test with BITCOIND_RPC_URL (frontend) connectivity
• work on round-robin signing with state sync?

app

• setup process more flexible
  • setting up for first time - in app onboarding screens
• hardware policy changes
• "force close" mode to exit all sats from signer if LSP goes dark

swarm

• show connected signer in swarm UI
• VLS frontend to manage policies

[Evanfeenstra]

set_policy in signer/src/policy needs to update the VelocityApprover on the fly. Blocked by VLS #324 https://gitlab.com/lightning-signer/validating-lightning-signer/-/issues/324

Updating allowlist blocked by VLS #332 https://gitlab.com/lightning-signer/validating-lightning-signer/-/issues/332

[Evanfeenstra]

Force close all channels and recover funds to address

Should implement a handler to run this function on phone. https://gitlab.com/lightning-signer/validating-lightning-signer/-/blob/main/vls-proxy/src/recovery/mod.rs#L189

[irriden]

Running with the frontend, as in export BITCOIND_RPC_URL=http://127.0.0.1:18443 yields ERROR vls_protocol::msgs bad magic 3f4 on vls-mqtt.

EDIT:

issue above now fixed with d407ccf