Linea Fusaka

[keithchew]

Hi

I am on v3.3.0 and with the Fusaka upgrade yesterday, Erigon stopped working with Linea. Logs below:

ARN[12-04|02:07:14.909] [4/6 Execution] Execution failed         block=26304571 txNum=342255593 header-hash=0x036ee771cbe9a70e4788c44e57549f2b92793589f8b2f733a77e5f6ba0a3050b err="invalid block, txnIdx=2, [EIP-7002] Syscall failure: Empty Code at WithdrawalRequestAddress=00000961ef480eb55e80d19ad83579a64c007002" inMem=false
INFO[12-04|02:07:14.910] [4/6 Execution] serial done              blk=26304571 blks=0 blk/s=0 txs=0 tx/s=0 gas/s=0 stepsInDB=0.04 step=219.0 alloc=2.6GB sys=2.7GB inMem=false
WARN[12-04|02:07:14.910] Cannot update chain head                 hash=0xff4f0fdd85826f93d0639c34c3a7575150ffa2a60da5cd9dc06b1a03df643c92 err="updateForkChoice: [4/6 Execution] invalid block, txnIdx=2, [EIP-7002] Syscall failure: Empty Code at WithdrawalRequestAddress=00000961ef480eb55e80d19ad83579a64c007002"

This sends an INVALID status to maru (their CL):

[WARN ] 2025-12-04 01:30:36.466 [ELSyncPoller] ELSyncService - Error with periodic polling service=ELSyncPoller: errorMessage=Unexpected payload status: INVALID
java.lang.IllegalStateException: Unexpected payload status: INVALID
        at maru.syncing.ELSyncService.action(ELSyncService.kt:134) ~[syncing.jar:?]
        at linea.timer.PeriodicPollingService.start$lambda$1(PeriodicPollingService.kt:35) ~[long-running-service-0.0.1-v20251114145306.jar:?]
        at linea.timer.JvmTimer$start$$inlined$timerTask$1.run(Timer.kt:149) [long-running-service-0.0.1-v20251114145306.jar:?]
        at java.base/java.util.TimerThread.mainLoop(Timer.java:566) [?:?]
        at java.base/java.util.TimerThread.run(Timer.java:516) [?:?]

Since maru worked with Geth after Fusaka, can someone please help confirm if the issue above is an Erigon bug?