Node not syncing, "Failed to turn execution payload into a block ref"

[surtling44]

I've been trying to run a Base node with Nethermind + OP Node for the last few days and it never syncs. I think the root cause is the L2 consensus node messages are of the wrong length and then the execution client is never finding a pivot block to work with. I'm not sure if it's complaining about not finding a pivot block from L1 consensus or L2. All logs are below.

My stack:

L1 Consensus - Prysm
L1 Execution - Reth
Base Consensus - OP Node (Geth)
Base Execution - Nethermind

All configuration settings are: main...surtling44:node:main

Logs:

execution-1  | 25 May 00:23:06 | No incoming messages from the consensus client that is required for sync. 
node-1       | {"t":"2025-05-25T00:23:07.918288814Z","lvl":"info","msg":"Received signed execution payload from p2p","id":"0x92c6965b8d9e9b3674ddf82e65b19940ffeef53488848c001eb678c0e83a0ed8:30671620","peer":"16Uiu2HAm5Tt3c8BPsraGUWonsFSxDmCAuJqb48XqajLg7nhLJKz5","txs":109}
node-1       | {"t":"2025-05-25T00:23:07.918381283Z","lvl":"info","msg":"Failed to turn execution payload into a block ref","id":"0x92c6965b8d9e9b3674ddf82e65b19940ffeef53488848c001eb678c0e83a0ed8:30671620","err":"failed to parse L1 info deposit tx from L2 block: data is unexpected length: 176"}
node-1       | {"t":"2025-05-25T00:23:09.939071858Z","lvl":"info","msg":"Received signed execution payload from p2p","id":"0x4663ddc46eca3d48516e033fbccf65cb2a61f69e97a89703e70ed7d02217794f:30671621","peer":"16Uiu2HAm5Tt3c8BPsraGUWonsFSxDmCAuJqb48XqajLg7nhLJKz5","txs":198}
node-1       | {"t":"2025-05-25T00:23:09.939160248Z","lvl":"info","msg":"Failed to turn execution payload into a block ref","id":"0x4663ddc46eca3d48516e033fbccf65cb2a61f69e97a89703e70ed7d02217794f:30671621","err":"failed to parse L1 info deposit tx from L2 block: data is unexpected length: 176"}
execution-1  | 25 May 00:23:11 | Waiting for Forkchoice message from Consensus Layer to set fresh pivot block [303900s] 
execution-1  | 25 May 00:23:11 | No incoming messages from the consensus client that is required for sync. 
node-1       | {"t":"2025-05-25T00:23:11.82267278Z","lvl":"info","msg":"Received signed execution payload from p2p","id":"0x70d507f21daef158245968a531585c4b8a301106f9c51cc55388bb2e63916da2:30671622","peer":"16Uiu2HAmBDorWpWvySqiLFY1MExnGV6exKYHv5KuHNf39H1RA2Qd","txs":80}
node-1       | {"t":"2025-05-25T00:23:11.822773241Z","lvl":"info","msg":"Failed to turn execution payload into a block ref","id":"0x70d507f21daef158245968a531585c4b8a301106f9c51cc55388bb2e63916da2:30671622","err":"failed to parse L1 info deposit tx from L2 block: data is unexpected length: 176"}
node-1       | {"t":"2025-05-25T00:23:13.885762082Z","lvl":"info","msg":"Received signed execution payload from p2p","id":"0x0ad61af5fc687494e587b1186eb60458d10fffcb84ab84e28fadbd97fac06a98:30671623","peer":"16Uiu2HAmReqjpYjVUsm1NvgHsutN66g8fsnCT1N5XKPgJs58d7fj","txs":150}
node-1       | {"t":"2025-05-25T00:23:13.885850988Z","lvl":"info","msg":"Failed to turn execution payload into a block ref","id":"0x0ad61af5fc687494e587b1186eb60458d10fffcb84ab84e28fadbd97fac06a98:30671623","err":"failed to parse L1 info deposit tx from L2 block: data is unexpected length: 176"}
node-1       | {"t":"2025-05-25T00:23:16.018908181Z","lvl":"info","msg":"Received signed execution payload from p2p","id":"0xd8af5b5bb2f0cc1614d371eef7fe373d6ccb7dda1e86c8d141839619b78a007d:30671624","peer":"16Uiu2HAm5Tt3c8BPsraGUWonsFSxDmCAuJqb48XqajLg7nhLJKz5","txs":205}
node-1       | {"t":"2025-05-25T00:23:16.018986351Z","lvl":"info","msg":"Failed to turn execution payload into a block ref","id":"0xd8af5b5bb2f0cc1614d371eef7fe373d6ccb7dda1e86c8d141839619b78a007d:30671624","err":"failed to parse L1 info deposit tx from L2 block: data is unexpected length: 176"}
execution-1  | 25 May 00:23:16 | No incoming messages from the consensus client that is required for sync. 
node-1       | {"t":"2025-05-25T00:23:17.923919552Z","lvl":"info","msg":"Received signed execution payload from p2p","id":"0xf9dd021444dafc83e2267af089b5a32702cdc52ad60c28f5d6b3de2a5f11b7fe:30671625","peer":"16Uiu2HAmBDorWpWvySqiLFY1MExnGV6exKYHv5KuHNf39H1RA2Qd","txs":147}
node-1       | {"t":"2025-05-25T00:23:17.923996188Z","lvl":"info","msg":"Failed to turn execution payload into a block ref","id":"0xf9dd021444dafc83e2267af089b5a32702cdc52ad60c28f5d6b3de2a5f11b7fe:30671625","err":"failed to parse L1 info deposit tx from L2 block: data is unexpected length: 176"}
node-1       | {"t":"2025-05-25T00:23:19.907329562Z","lvl":"info","msg":"Received signed execution payload from p2p","id":"0x047e41199641efb2b45e1953acb52f4b30d3f062695abccc469a955efd8eae87:30671626","peer":"16Uiu2HAmReqjpYjVUsm1NvgHsutN66g8fsnCT1N5XKPgJs58d7fj","txs":177}
node-1       | {"t":"2025-05-25T00:23:19.907396662Z","lvl":"info","msg":"Failed to turn execution payload into a block ref","id":"0x047e41199641efb2b45e1953acb52f4b30d3f062695abccc469a955efd8eae87:30671626","err":"failed to parse L1 info deposit tx from L2 block: data is unexpected length: 176"}
execution-1  | 25 May 00:23:21 | Waiting for Forkchoice message from Consensus Layer to set fresh pivot block [303910s] 
execution-1  | 25 May 00:23:21 | No incoming messages from the consensus client that is required for sync. 
node-1       | {"t":"2025-05-25T00:23:21.981585694Z","lvl":"info","msg":"Received signed execution payload from p2p","id":"0x8f96b6dcfa2ae1cc56342b553f5cfe13e4558f1ced6aabf5f71229afa6b964ba:30671627","peer":"16Uiu2HAm5Tt3c8BPsraGUWonsFSxDmCAuJqb48XqajLg7nhLJKz5","txs":139}
node-1       | {"t":"2025-05-25T00:23:21.981676608Z","lvl":"info","msg":"Failed to turn execution payload into a block ref","id":"0x8f96b6dcfa2ae1cc56342b553f5cfe13e4558f1ced6aabf5f71229afa6b964ba:30671627","err":"failed to parse L1 info deposit tx from L2 block: data is unexpected length: 176"}
node-1       | {"t":"2025-05-25T00:23:23.688619202Z","lvl":"info","msg":"Received signed execution payload from p2p","id":"0xd2eb0f5e19bbe67390c8c2aa6ed7331db8593f89a9bd15312343f429c6550adb:30671628","peer":"16Uiu2HAkwGPxAF9Ef7CTob6azjDvHH3CWJ1tcKNCZswrr5oWLqg6","txs":88}
node-1       | {"t":"2025-05-25T00:23:23.688738493Z","lvl":"info","msg":"Failed to turn execution payload into a block ref","id":"0xd2eb0f5e19bbe67390c8c2aa6ed7331db8593f89a9bd15312343f429c6550adb:30671628","err":"failed to parse L1 info deposit tx from L2 block: data is unexpected length: 176"}
node-1       | {"t":"2025-05-25T00:23:25.819103223Z","lvl":"info","msg":"Received signed execution payload from p2p","id":"0xadb7e13e9355727d68391b56b2b5adcdacbba4331f50ddb59c8daca10ec2a005:30671629","peer":"16Uiu2HAmBDorWpWvySqiLFY1MExnGV6exKYHv5KuHNf39H1RA2Qd","txs":94}
node-1       | {"t":"2025-05-25T00:23:25.819193165Z","lvl":"info","msg":"Failed to turn execution payload into a block ref","id":"0xadb7e13e9355727d68391b56b2b5adcdacbba4331f50ddb59c8daca10ec2a005:30671629","err":"failed to parse L1 info deposit tx from L2 block: data is unexpected length: 176"}

[surtling44]

Was because op-node was an old version that didn't support the Isthmus hard fork. Fixed with #470.