George Knee

> > Since we absorbed the ts client into this repo, we could also just reuse the existing create channels utility in docker ? > > We could, but this...

Solving this may involve our supporting `wss` and `https` (secure).

Useful resources: * https://besu.hyperledger.org/stable/public-networks/how-to/use-besu-api/authenticate * https://medium.com/@terawattled/protecting-ethereum-json-rpc-api-with-password-887f3591d221 We may want to protect different API methods in different ways. For example `GetAddress()` may require different credentials to `CreateLedgerChannel`. The second article suggests...

Idea 1a. Have the objective do the caching instead of the message service. Those cached messages can be garbage collected at the same time as the objective, although that does...

Idea 3: Having automatic retries when we don't get an acknowledgment from the message recipient.

Idea 2: Looking at the implementation, this seems tricky because we tend to not compute side effects (we record that we did it, so that we don't have to bother...

What do you think is the correct behaviour of `go-nitro` when the "user" requests to directly defund a "non-empty" ledger channel? Here's one suggestion: Option 1 --- 1. Add a...

Decision in standup today: For now we will generate an error when this happens (we don't expect it often but we can't rule it out). We will save the longer...

I imagine it wouldn't be too much work, so worth spending a bit of time on.

Another (possibly better) example: The rpc client may try to ask the nitro node to create a ledger channel with a counterparty when one already exists. Currently, this causes a...