Right now the docs correspond to what's on master. We need docs for each daemon release so developers can see what's available in the version they are using.

https://github.com/jimporter/mike may be helpful.

Background

When a node has multiple private channels with the same peer, the hop hints in their payment requests will be populated with multiple channels. The purpose of these hop hints is to specify the next node's key and indicate the fees and cltv delta needed for route construction.

In pathfinding, due to non-strict forwarding, an LND node paying to this destination will only use the

Suggesting that we change the default setting of Preferences->Open Web UI at Launch' to true` across all OSes. Right now we make this so for Linux, since some desktop envs don't have a tray for our "cube menu" to live in. However, this doesn't account for users on other OSes who may have extensions for decluttering system menus/trays, and thus have no initial "way in" to Desktop upon install.

Has msquic been tested against a browser client, like Chrome? I can't seem to get a connection to the mquic sample server (no sign from server that anything is attempted) with Chrome's example WebTransport over Quic client, but maybe it's too early in the game to expect this to work, or I'd be better off looking into quiche.

Example client here:
https://googlechrome.github.io/samples/webtransp

The main entry point of interest here is probably PartialDecode::new. This is a particularly important interface to audit as there are absolutely zero barriers to feeding data into it.

Today, my project's build failed in CI because of a problem downloading the cuckoo_generator executable in the run script. I'm not sure what the actual issue was (there was an issue extracting the URL from the GH API response), but it started working again by itself sometime later, so I'm assuming that it was a GH blip.

I find it a little strange that the SPM installation for Cuckoo depends

Forgot we don't use npm ci in Companion. Maybe we could ameliorate this for folks who do the same:

• Detect npm ci or npm i and throw an error that all-in-one npm run dev-build should be used instead
• Update README.md and DEVELOPER-NOTES.md accordingly