Closed dankostiuk closed 3 years ago
Hello @dankostiuk!
This issue is caused by the eth_estimateGas
you can see above.
What happens is that you try to estimateGas for a specific block, and to do that we need to simulate the transaction inside that block. To run the gas estimation simulation we need to know the coinbase accounts for the given block which we unmarshal from the IBFT extradata header field of the block.
It is this checking of the IBFT extradata headers that fails and panics, since the block eth_estimateGas
is ran on is the genesis block which contains no extradata headers containing the signature of the proposer.
This is symptomatic of the blockchain network not working, thus not producing blocks.
I would need you to check two things:
Run the peers list command: go run main.go peers list --grpc-address=...
and you should see 3 peers of the given node.
Although block production is visible in the main log output, it is much cleaner to run go run main.go monitor --grpc-address=...
and you should be able to see live events like this:
[BLOCK EVENT]
Event Type = ADD BLOCK
Block Number = 353
Block Hash = 0xed5cc60a9e57bb414cddd9ae1033d8e85db16c0940101d7d1004ce38e9a1b16
If there are no ADD BLOCK
events visible in the output of the monitor
command, then we can safely say that the block production is not working for some reason and we can troubleshoot further.
Thanks @lazartravica , I'll make sure to do this next time I see this error so I can provide more details.
Runtime error after dispatcher fails to dispatch
Description
Running locally, we've seen what appears to be a runtime error likely right after the error:
[ERROR] polygon.dispatcher: failed to dispatch: method=eth_getCode err="given root and slot not found in storage"
.Your environment
OSX 11.4
6906ed9
develop
Steps to reproduce
Tell us how to reproduce this issue
polygon-sdk server run
with IBFT consensus of 4 nodes running for about 12 hours.Where the issue is, if you know
Which commands triggered the issue, if any
polygon-sdk server run
..Expected behaviour
No runtime error.
Actual behaviour
Runtime error (see logs).
Logs
Proposed solution
If you have an idea of how to fix this issue, please write it down here, so we can begin discussing it