-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate supporting block validation #2
Comments
cc @mattsse, I think we would be open to including this upstream? of note @alextes there's an API example of how to extend node RPC w/o forking the node here:
This would allow maintaining this RPC w/o having to fork the codebase, in a nice clean way. LMK if this is helpful, and if the CLI extension API I linked above has all the necessary components to execcute on this |
Thank you for the suggestions / links. Very helpful indeed. Do let us know if you are open to including something along these lines upstream. |
@gakonst amazing, thanks for the heads up! |
Reimplemented the prototype using reth as library at: ultrasoundmoney/reth-payload-validator#1 For this to work in my current version I had to do some minor changes in the reth codebase for which I opened a PR here: |
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.
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!
The text was updated successfully, but these errors were encountered: