okjodom

> Ideally if a mint has multiple gateways, it should be possible for any of them to short-circuit the payment (is this the case? I don't know the details), which...

> If an invoice it wants to pay names one of these as a route hint do the following: Gets complicated if the same gateway serves multiple mints. But maybe...

> 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...

Seems the receiver should be optional as well seeing as the spawning of the sender-receiver channel server and the receiver are closely related, and a receiver is not useful until...

Running a webserver within `LnGateway::new()` is closely related to how we instantiate the `ln_client` which is currently just c-ln RPC. As part of removing this side-effect of instantiating the gateway,...

> It seem to me that these "not doing side effects in constructor" is a red herring. Great point. The real gap seems to be a need for gateway architecture...

> As a matter of fact in Rust I usually employ a pattern where "service/actor threads" are the thread. Inspiring pattern that I can adopt on what I prototyped as...

A sketch including our actor discussion above : 

Closed by the discussion and work that make up the entirety of #714

> 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 key...