-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
refactor: move ethereum and op builder into separate crates #5876
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM as an initial split. Feel free to ticket out any further cleanups you have in mind to @refcell and I!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
sweet will do, this is prep for moving off op features, (soonish), feature by feature |
The motivation for this is to reduce the number of in code cfg optimism and have standalone components for different networks instead.
extracts the OP code from the basic-payload-builder and add
ethereum-payload-builder
optimimism-payload-builder
so we need less cfg optimism.
this needs a few cleanup task afterwards but should be fine for now.
Note that crates still have an optimism feature to make it easier to handle mutually exclusive payload builder crates, because clippy doesn't respect the exclude members setting from Cargo.toml
This is still a bit horrible, but at least separates the implementations.
~~blocked by #5869 ~~