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
When running rosetta-cli for Ethereum Roopsten testnet or Mainnet, there was an reconciliation issue for 0x0000000000000000000000000000000000000000.
Error message:
Command Failed: reconciliation failure: inactive reconciliation error for 0x0000000000000000000000000000000000000000 at 10 (computed: 5000000000000000001ETH, live: 1ETH)
Cause
At the genesis block, there is a mining reward for 0x0000000000000000000000000000000000000000.
And that reward does not applied to on-chain balance of 0x0000000000000000000000000000000000000000.
But the problem is: Reconciler handles that genesis reward as +balance for 0x0000000000000000000000000000000000000000, so it triggers the error.
To Reproduce
Following this guide is enough to re-produce the problem.
Expected behavior
The first genesis block reward must not be calculated +balance for 0x0000000000000000000000000000000000000000 because it is not applied to on-chain state.
@aeharvlee you are right. We had this check before but somehow due to one another issue we changed it (coinbase/mesh-ethereum#73) . We will fix that soon. Thanks for raising the issue.
Describe the bug
When running rosetta-cli for Ethereum Roopsten testnet or Mainnet, there was an reconciliation issue for
0x0000000000000000000000000000000000000000
.Error message:
Command Failed: reconciliation failure: inactive reconciliation error for 0x0000000000000000000000000000000000000000 at 10 (computed: 5000000000000000001ETH, live: 1ETH)
Cause
0x0000000000000000000000000000000000000000
.0x0000000000000000000000000000000000000000
.0x0000000000000000000000000000000000000000
, so it triggers the error.To Reproduce
Expected behavior
0x0000000000000000000000000000000000000000
because it is not applied to on-chain state.Additional context
go1.17.7 darwin/arm64
The text was updated successfully, but these errors were encountered: