ultrasoundmoney / reth Goto Github PK

We run a lightly modified version of: https://github.com/flashbots/builder to validate payloads the relay receives. I do not have a good overview at the moment of which bits we heavily rely on and which bits we don't but certainly part of it can be found here.

• Create an overview of the code the relay depends on.
• Create an overview of how much Reth already supports and does not support.

Once #1 is confirmed, the above is done and the amount of work looks reasonable, we can create an issue for supporting block validation in Reth. At that point it would also be worth it to discuss with the Ultra Sound team how we want to handle contributing it back. It'd be nice to contribute any implementation upstream, at the same time, not doing so could make a significant difference for Ultra Sound's treasury. We can surely figure something out. Delayed upstreaming, contributing core bits but not performance bits, funding from paradigm, we'll find something!

It would be a shame to modify Reth to support our use-cases and find out its performance is not stable enough. Let's test:

• It syncs.
• We can fire a bunch of spec requests at it and it responds in timely fashion (I don't know these of the top of my head but guessing things like: what is the current head, get block 7152345 etc. would be good to craft something close to our real load). It looks like we don't send any requests except for block validation requests!

Maybe Reth provides metrics we could hook into Prometheus?