[Feature] Extend `Hardforks` to use variable parameters

alloy-rs / op-alloy

Transports, Middleware, and Networks for the OP Stack built on Alloy

https://alloy-rs.github.io/op-alloy/

Apache License 2.0

44 stars 36 forks source link

[Feature] Extend `Hardforks` to use variable parameters #280

Closed refcell closed 1 week ago

refcell commented 2 weeks ago

Component

consensus

Describe the feature you would like

Currently, the Hardforks type in op-alloy-consensus uses hardcoded addresses and variables in it's parameters. By default it should use the current hardcoded ones.

Additional context

No response

refcell commented 1 week ago

Closing this as it's simple to introduce custom hardfork txs separately from the Hardforks type. The cleanup refactoring hardforks into separate modules also does a lot of the intended cleanup here, moving consts into their Hardfork type so as to not be re-exported.