L1 Beacon API fails "cannot unmarshal hex number with leading zero digits into Go struct field"

[ErrorEater]

Here is the error output of base-node trying to connect to L1 Beacon node: json: cannot unmarshal hex number with leading zero digits into Go struct field StorageProofEntry.storageProof.value of type *hexutil.Big

How to solve?

node-1       | t=2024-07-31T17:09:57+0000 lvl=info msg="Rollup Config" l2_chain_id=8453 l2_network=Base l1_chain_id=1 l1_network=mainnet l2_start_time=1686789347 l2_block_hash=0xf712aa9241cc24369b143cf6dce85f0902a9731e70d66818a3a5845b296c73dd l2_block_number=0 l1_block_hash=0x5c13d307623a926cd31415036c8b7fa14572f9dac64528e857a470511fc30771 l1_block_number=17481768 regolith_time="@ genesis" canyon_time="@ 1704992401 ~ Thu Jan 11 17:00:01 UTC 2024" delta_time="@ 1708560000 ~ Thu Feb 22 00:00:00 UTC 2024" ecotone_time="@ 1710374401 ~ Thu Mar 14 00:00:01 UTC 2024" fjord_time="@ 1720627201 ~ Wed Jul 10 16:00:01 UTC 2024" interop_time="(not configured)" plasma_mode=false
node-1       | t=2024-07-31T17:09:57+0000 lvl=info msg="Initializing rollup node" version=v1.7.7-f8143c8c-1717593043
node-1       | t=2024-07-31T17:09:57+0000 lvl=info msg="Connected to L1 Beacon API, ready for EIP-4844 blobs retrieval." version="Prysm/v5.0.4 (windows amd64)"
node-1       | t=2024-07-31T17:09:57+0000 lvl=error msg="failed to fetch runtime config data" err="required-protocol-version value failed to load from L1 contract: failed to fetch proof of storage slot 0x4aaefe95bd84fd3f32700cf3b7566bc944b73138e41958b5785826df2aecace0 at block 0x2ebf1718f743bb41b1b6efadf1443fb70fc311be0b85fbc56a9e5d1bb49c9848: json: cannot unmarshal hex number with leading zero digits into Go struct field StorageProofEntry.storageProof.value of type *hexutil.Big"

[SaulMoonves]

I'm experiencing this too, I'm dead in the water please help.

[roberto-bayardo]

@SaulMoonves are you also using Prysm for your L1 beacon node? I wonder if there's an incompatibility that was recently introduced.

[SaulMoonves]

I am using Nethermind for my L1 execution and Nimbus for my beacon.

[roberto-bayardo]

Oh hmm, I think the key error may be this one which doesn't seem beacon node related since L1 contract data should be getting fetched from the execution client not the beacon node. This is the same error you get @SaulMoonves ?

node-1 | t=2024-07-31T17:09:57+0000 lvl=error msg="failed to fetch runtime config data" err="required-protocol-version value failed to load from L1 contract: failed to fetch proof of storage slot 0x4aaefe95bd84fd3f32700cf3b7566bc944b73138e41958b5785826df2aecace0 at block 0x2ebf1718f743bb41b1b6efadf1443fb70fc311be0b85fbc56a9e5d1bb49c9848: json: cannot unmarshal hex number with leading zero digits into Go struct field StorageProofEntry.storageProof.value of type *hexutil.Big"

[SaulMoonves]

I do believe I saw that error.

I switched to a different docker-compose provided to me by a coworker and got up and syncing (it might be out of date though), so I don't have this configuration anymore but here is a snippet of what I am using now that works:

geth:
    image: ghcr.io/base-org/node-geth:v0.10.2

node:
    image: ghcr.io/base-org/node-geth:v0.10.2
    depends_on:
      - geth

If this is dangerously out of date or something I can snapshot the data dir and try switching again to test things out if it's helpful.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue was closed because it has been inactive for 5 days since being marked as stale.