-
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
fix(storage): dont skip consistency checks for op-mainnet
if using minimal bootstrap
#11099
Conversation
op-mainnet
op-mainnet
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.
this will fail for ovm chain
blocked by #9739 |
op-mainnet
op-mainnet
if using minimal bootstrap
if provider.chain_spec().chain() == Chain::optimism_mainnet() && | ||
provider | ||
.block_number(b256!( | ||
"bee7192e575af30420cae0c7776304ac196077ee72b048970549e4f08e875453" |
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.
please define as constant in reth_optimism_primitives::bedrock
// | ||
// If we detect an OVM import was done (block #1 <https://optimistic.etherscan.io/block/1>), skip it. | ||
// More on [#11099](https://github.com/paradigmxyz/reth/pull/11099). | ||
#[cfg(feature = "optimism")] |
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.
we can keep this cfg, but not strictly required because not expensive to check and only reachable by op mainnet
reverting #9737
Storage consistency ensures that:
Currently, OVM import of receipts seems to be broken (#10580, #9739) (#9725).
Any node that synced to the tip after #9737 may be inconsistent (from a historical storage pov), and disabling this skip entirely would break them. Static files are not a database, so a migration may be possible, but more complex.
For now, leaving this check disabled for nodes which imported the ovm historical data (use minimal bootstrap instead). But it's important to understand that a sudden crash of the node MAY break it.