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
The field totalDifficulty was removed from the official Ethereum JSON RPC Block schema in ethereum/execution-apis#570.
It seems some clients did already remove it (Erigon), but others chose not to (Nethermind), leading to inconsistent answers between providers when calling the EVM RPC canister with eth_getBlockByNumber.
Example with a recent block:
Ankr when queried for the block 0x1312d00 returns a value containing the field totalDifficulty, while the same query for PublicNode does not:
As explained in #311, the field `totalDifficulty` was removed from the
official Ethereum JSON RPC Block schema in
ethereum/execution-apis#570, leading to
inconsistent answers between providers when calling the EVM RPC canister
with `eth_getBlockByNumber`. This seems to affect all blocks and not
only post-merge blocks.
As a workaround, the EVM RPC canister no longer deserializes the field
`totalDifficulty` in the provider's JSON response and set the Candid
returned value for `evm_rpc_types::Block::totalDifficulty` always to
`None` to be backwards-compatible.
The field
totalDifficulty
was removed from the official Ethereum JSON RPCBlock
schema in ethereum/execution-apis#570.It seems some clients did already remove it (Erigon), but others chose not to (Nethermind), leading to inconsistent answers between providers when calling the EVM RPC canister with
eth_getBlockByNumber
.Example with a recent block:
Ankr
when queried for the block0x1312d00
returns a value containing the fieldtotalDifficulty
, while the same query forPublicNode
does not:Example with an old block:
The field
totalDifficulty
is not only removed from blocks post-merge, but also pre-existing blocks are affected.Ankr
when queried for the block0x0
returns a value containing the fieldtotalDifficulty
, while the same query forPublicNode
does not:The text was updated successfully, but these errors were encountered: