Francisco de Borja Aranda Castillejo

_Originally posted by @mkysel in https://github.com/xmtp/xmtpd/pull/411#discussion_r1932333578_ Read the quoted content for more context.

The client should be alerted when a reorg has been handled.

feat(indexer): extract indexer to its own process

1

Currently the indexer is an in-process service, dependant on xmtpd. By moving it to an external process some key features would be achieved, such as: - Improved fault tolerance. Potentially...

Currently the indexer sets a backfill limit of 1000 blocks. This value can be different for each RPC's. Discover dynamically the max backfill limit.

Test flakyness

1

There are multiple flaky tests after the latest Connect-RPC changes. Might be related or might be not. Probably the way we look for free ports to open can be improved.

At least the `gateway` service doesn't work pointing to an env. Pointing to a JSON config file works.

When a request to the server carries the proper JWT, the auth interceptor sets: `ctx = context.WithValue(ctx, constants.VerifiedNodeRequestCtxKey{}, true)` Afterwards, no handler actually checks the context value. This means: -...

Extracted from an @insipx comment: It might be nice to include a latency combinator, like `api::measured` or something that automatically runs the request w/ a timeout, then returns a struct...

Tower implements two services that might be interesting for the D14N client. [Steer](https://docs.rs/tower/latest/tower/steer/struct.Steer.html) manages a list of endpoints which manages the same service, sending the request to the chosen one....