It seems latest jerigon is not able to parse sufficient data to prove every block.
Tested against John's node, on block 20278929, with jerigon commit 83e0f2fa8c8f6632370e20fef7bbc8a4991c73c8, and feat/cancun branch on zk-evm side, commit ddca6be.
Attached is the faulty block trace fetched from Jerigon. It is missing an account codehash, yielding an unexpected panic! which shouldn't happen with Jerigon but only one some situations with the native tracer.
It seems latest
jerigonis not able to parse sufficient data to prove every block.Tested against John's node, on block 20278929, with jerigon commit 83e0f2fa8c8f6632370e20fef7bbc8a4991c73c8, and
feat/cancunbranch onzk-evmside, commit ddca6be.Attached is the faulty block trace fetched from Jerigon. It is missing an account codehash, yielding an unexpected
panic!which shouldn't happen with Jerigon but only one some situations with the native tracer.20278929.json