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
In the last stable release of node (2.0.0) I've faced up with the following issue: the eth_getLogs method returns wrong block hash in the logs response in a self-deployed node. Below are the examples with 1.6.0 release vs 2.0.0 (you can see that v1.6 node returns correct blockHash, while 2.0 - wrong):
In the last stable release of node (2.0.0) I've faced up with the following issue: the eth_getLogs method returns wrong block hash in the logs response in a self-deployed node. Below are the examples with 1.6.0 release vs 2.0.0 (you can see that v1.6 node returns correct blockHash, while 2.0 - wrong):
Command:
Node v2.0.0 Response:
Node v1.6.0 Response for the same request:
The text was updated successfully, but these errors were encountered: