Closed Chomtana closed 8 months ago
@clabby does op-node support the
parentBeaconBlockRoot: DATA, 32 Bytes - Root of the parent beacon block.
https://github.com/ethereum/execution-apis/blob/main/src/engine/cancun.md#payloadattributesv3
looks like it does
@mattsse Yes, it does after Dencun activation (in the Ecotone hardfork, which has not been activated anywhere except for internal devnets just yet). https://specs.optimism.io/protocol/exec-engine.html#extended-payloadattributesv3
Starting at Ecotone, the parentBeaconBlockRoot must be set to the L1 origin parentBeaconBlockRoot, or a zero bytes32 if the Dencun functionality with parentBeaconBlockRoot is not active on L1.
@mattsse Yes, it does after Dencun activation (in the Ecotone hardfork, which has not been activated anywhere except for internal devnets just yet). https://specs.optimism.io/protocol/exec-engine.html#extended-payloadattributesv3
Starting at Ecotone, the parentBeaconBlockRoot must be set to the L1 origin parentBeaconBlockRoot, or a zero bytes32 if the Dencun functionality with parentBeaconBlockRoot is not active on L1.
@clabby Do you know why the above logs say that the engine_forkchoiceUpdatedV3
method was called then? V3 methods should only be called post-ecotone IIRC
@Rjected This is on our end, got to the bottom of it a few mins ago. Fix in review: https://github.com/ethereum-optimism/optimism/pull/9253
geth
has identical behavior to reth
in upstream (where it rejects V3 messages w/ a missing parentBeaconBlockRoot
), merged recently w/ https://github.com/ethereum/go-ethereum/pull/28230. We've pulled in the upstream PR, and an rc for v1.5.1 will be released once 9253 is merged.
@Chomtana For now, temporarily downgrading to v1.4.3
will do the trick.
@Rjected This is on our end, got to the bottom of it a few mins ago. Fix in review: ethereum-optimism/optimism#9253
geth
has identical behavior toreth
in upstream (where it rejects V3 messages w/ a missingparentBeaconBlockRoot
), merged recently w/ ethereum/go-ethereum#28230. We've pulled in the upstream PR, and an rc for v1.5.1 will be released once 9253 is merged.@Chomtana For now, temporarily downgrading to
v1.4.3
will do the trick.
awesome, that makes sense. I'll watch that PR, when it's merged + released, I'll close this issue with a recommendation to update op-node
The fix is now merged and available in a release candidate: https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.5.1-rc.1
closing this!
Describe the bug
Base mainnet op-reth stuck with "no parent beacon block root post-cancun" when using with op-node v1.5.0
Also, op-node is stuck with many "no peers ready to handle block requests for more P2P requests for L2 block history"
Please see the longer log at https://gist.github.com/Chomtana/ff1b6181e6b0f424ac1e0111c89696ff because GitHub says it's too long
Notice that op-node v1.5.0 uses engine_forkchoiceUpdatedV3 while v1.4.3 uses engine_forkchoiceUpdatedV2
Steps to reproduce
To fix this, I revert op-node to v1.4.3 and op-reth to v0.1.0-alpha.16 (Release)
Node logs
Platform(s)
Linux (x86)
What version/commit are you on?
commit 10f4434
What database version are you on?
Current database version: 1 Local database version: 1
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
make install-op
Code of Conduct