[Core Protocol] Is it same effect when rollup client call engine_forkchoiceUpdatedV1 or engine_forkchoiceUpdatedV2

[GrapeBaBa]

Issue Description

I am working on op-besu, I found the only difference between engine_forkchoiceUpdatedV1 and engine_forkchoiceUpdatedV2 is withdrawals field. If I understood correct, it is not used by OP stack PayloadAttributes so that we should implement engine_forkchoiceUpdatedV1 and engine_forkchoiceUpdatedV2 same logic, right?

Additional Information

No response

[sbvegan]

Hey @GrapeBaBa, yes you're right. The V1 is for pre-canyon upgrade and V2 will be after canyon. This is because Canyon brings in the Shanghai hardfork changes. Here's a couple specs you can use to reference:

• L2 Shapella (Shanghai + Capella) hardfork support optimism#6728
• https://github.com/ethereum-optimism/optimism/blob/develop/specs/superchain-upgrades.md#canyon

[github-actions[bot]]

Hey @GrapeBaBa, We hope your recent question was resolved to your satisfaction. Your feedback is invaluable and helps us improve our support services. Could you spare a moment to fill out a short feedback survey. Thank you for helping us improve our developer community.