okjodom

## Data flows within the Gateway Data flows between discrete gateway components over messaging channels. There are three messaging scenarios as follows: - LnRpc [Plugin] Gateway Actor - Webserver --->...

> don't see the point of having multiple GatewayActor threads running concurrently. I think it would be better to just have one, but have it maintain a map of federation...

> Another question is what happens when the plugin is restarted. Will it remember the federations it was connected to or won't it? Currently it only knows which federations it's...

closed! After #869 , the major pieces of this design proposal are in, with some gaps for improvement :) 🥳

should you also remove the [in-gateway filtering of intercepted htlcs ](https://github.com/fedimint/fedimint/blob/af1f99ef2b56ee6253b2e981dd7f72eaddc50d25/gateway/ln-gateway/src/lib.rs#L555C18-L555C36) as part of this change

> @okjodom added versioning for the gateway API awhile back. @okjodom could you advise on how to modify `leave_federation` so it is backwards compatible? I suppose we can cherry pick...

This was a limitation of the old gateway architecture, from which we have fully migrated after #1718 The new gateway introduced to the test framework at #1717 supports multiple federations

> Do we have a test for this, yet? Reactivating, until we have automated tests

> @okjodom You seem to have the most pressing need for stable FedID From the Gateway's perspective, we are **assuming `FederationID` as presently defined is already stable**. We can build...

We only need to use the [CLN plugins logger](https://github.com/ElementsProject/lightning/blob/bc9333ac1e317a2baf3e595b2475963c86768b23/plugins/src/logging.rs#L40) which can be turned on via `CLN_PLUGIN_LOG` env variable