Bad block with hash on op-reth 1.3.11 #15792
Description
Describe the bug
After upgrading to 1.3.11, the node reports bad blocks on devnet.
{"timestamp":"2025-04-17T14:19:54.540543Z","level":"WARN","fields":{"message":"Failed to invoke hook","err":"no state found for block 0xb423447bc7204c8e143079344870a7ee39ba95d6e38259aa48c808aec5c9b512"},"target":"engine::invalid_block_hooks::witness"}
{"timestamp":"2025-04-17T14:19:54.540614Z","level":"WARN","fields":{"message":"Invalid block error on new payload","invalid_hash":"0xb8e0d5e24558b178b61a0ad30d9981c2a51f1d6a08a5a5c0df5b0218c9ef5504","invalid_number":18118181,"validation_err":"failed to verify block post-execution: no state found for block 0xb423447bc7204c8e143079344870a7ee39ba95d6e38259aa48c808aec5c9b512"},"target":"engine::tree"}
{"timestamp":"2025-04-17T14:19:54.540645Z","level":"WARN","fields":{"message":"Bad block with hash","invalid_ancestor":"BlockWithParent { parent: 0xb423447bc7204c8e143079344870a7ee39ba95d6e38259aa48c808aec5c9b512, block: NumHash { number: 18118181, hash: 0xb8e0d5e24558b178b61a0ad30d9981c2a51f1d6a08a5a5c0df5b0218c9ef5504 } }"},"target":"consensus::engine"}
this does not happen consistently, sometimes gets resolved after a resync.
Steps to reproduce
Steps to reproduce:
- run op-reth with latest op-node with isthmus
Node logs
{"timestamp":"2025-04-17T14:19:54.540543Z","level":"WARN","fields":{"message":"Failed to invoke hook","err":"no state found for block 0xb423447bc7204c8e143079344870a7ee39ba95d6e38259aa48c808aec5c9b512"},"target":"engine::invalid_block_hooks::witness"}
{"timestamp":"2025-04-17T14:19:54.540614Z","level":"WARN","fields":{"message":"Invalid block error on new payload","invalid_hash":"0xb8e0d5e24558b178b61a0ad30d9981c2a51f1d6a08a5a5c0df5b0218c9ef5504","invalid_number":18118181,"validation_err":"failed to verify block post-execution: no state found for block 0xb423447bc7204c8e143079344870a7ee39ba95d6e38259aa48c808aec5c9b512"},"target":"engine::tree"}
{"timestamp":"2025-04-17T14:19:54.540645Z","level":"WARN","fields":{"message":"Bad block with hash","invalid_ancestor":"BlockWithParent { parent: 0xb423447bc7204c8e143079344870a7ee39ba95d6e38259aa48c808aec5c9b512, block: NumHash { number: 18118181, hash: 0xb8e0d5e24558b178b61a0ad30d9981c2a51f1d6a08a5a5c0df5b0218c9ef5504 } }"},"target":"consensus::engine"}
Platform(s)
Linux (x86)
Container Type
Not running in a container
What version/commit are you on?
v1.3.11
What database version are you on?
no sure, getting panic
2025-04-17T16:12:22.622765Z INFO Initialized tracing, debug log directory: /home/op-rbuilder/.cache/reth/logs/dev
thread 'main' panicked at crates/op-rbuilder/src/main.rs:81:10:
called `Result::unwrap()` on an `Err` value: Database does not exist: "/home/op-rbuilder/.local/share/reth/dev/db"
Location:
/home/op-rbuilder/.cargo/git/checkouts/reth-e231042ee7db3fb7/90c514c/crates/cli/commands/src/db/mod.rs:81:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Which chain / network are you on?
unichain
What type of node are you running?
Full via --full flag
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct
- I agree to follow the Code of Conduct