You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(code: -32000, message: mismatch in expected state root computed 0xc8bc7e46bfebb0ece517dd5d253db7a7b09a0c5067c2704c8d96e1083b60cdc3 vs 0x14ebc27fa2bca4e46349de42693ea1f61576b032f6d42adcd3a6178ce1e0fc4c indicates bug in proof implementation, data: None)
Steps to reproduce the behaviour
Point erigon.local to the integration 5 network and then run:
There's no backtrace. The full logs are extremely verbose for this call so I'm not including them But it ends with the same message that's returned via the RPC
[WARN] [06-24|19:02:50.167] Served conn=24.61.53.2:45698 method=eth_getProof reqid=1 t=1.927780285s err="mismatch in expected state root computed 0xc8bc7e46bfebb0ece517dd5d253db7a7b09a0c5067c2704c8d96e1083b60cdc3 vs 0x14ebc27fa2bca4e46349de42693ea1f61576b032f6d42adcd3a6178ce1e0fc4c indicates bug in proof implementation"
The text was updated successfully, but these errors were encountered:
System information
Erigon version:
cdk-erigon version 2.43.0-dev-3107569d
OS & Version: Debian GNU/Linux 12 (bookworm)
Commit hash: 3107569d
Erigon Command (with flags/config):
cdk-erigon --config /etc/erigon/config.yaml
Concensus Layer: N/A
Concensus Layer Command (with flags/config): N/A
Chain/Network: Sepolia Erigon Integration 5 (chain 8282)
Expected behaviour
returns
0x0000000000000000000000000000000000000000000000000000000000000001
Ideally I would be able to generate a storage proof with this call:
cast rpc --rpc-url http://erigon.local:8500 eth_getProof 0xb566BE17B22404BD46F389030ec5592F8ffAde12 '["0x0000000000000000000000000000000000000000000000000000000000000000"]' latest
Actual behaviour
This currently returns
Steps to reproduce the behaviour
Point
erigon.local
to the integration 5 network and then run:cast rpc --rpc-url http://erigon.local:8500 eth_getProof 0xb566BE17B22404BD46F389030ec5592F8ffAde12 '["0x0000000000000000000000000000000000000000000000000000000000000000"]' latest
Backtrace
There's no backtrace. The full logs are extremely verbose for this call so I'm not including them But it ends with the same message that's returned via the RPC
The text was updated successfully, but these errors were encountered: