elsirion

I think the solution is much simpler: 1. The client keeps a list of known gateways 2. If an invoice it wants to pay names one of these as a...

> But maybe we could include a mint identifier in the route hint? We need to do that anyway since the GW wouldn't know which mint to ask otherwise.

> self payments - special case of outgoing payments, where the gateway is directly bridging two mints Note that this isn't even supported currently. We'd need to think about this...

I'll think about it a bit more but this sounds like a great idea. Some comments: * We'll still need an integer !=0 associated with each peer for threshold blind...

I'm getting the feeling that maybe the web server shouldn't run inside this struct. The current architecture would lend itself to having a `GatewayAPI` trait that contains all the functions...

Some ideas to improve debugability: * CLN config flag for log level * API call to set log level on the fly (needs to be protected somehow, so maybe as...

Braindump: * Add a hop to the route hint so that the route becomes `[gateway, federation, user]` where the user key is randomly generated by the user and the federation...

Sounds good, do you know if the [current CI failure](https://github.com/fedimint/fedimint/actions/runs/3305068342/attempts/1) is related to the PR or just general flakyness?

Re-run fixed it, but GH complains that the branch is out of date, could you rebase on master please?

I'm getting some advice not to use BIP39, I don't have a strong opinion on the encoding of our input key material, so I'm open to other ideas. Current contenders...