-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setting block number is not effecting the request #99
Comments
I had a similar issue with Arbitrum One or Arbitrum Nova, I'm not sure wich one exactly. Request was eth_getBalance. It always returned the latest block but also returned different result balances (i guessed based of the number of the block). I tested the closest block to check if it returned a valid result, and it did. What I did was to include the block from the request into the result table, along with its timestamp and everything else. If it's returning the correct data, you might want to implement a workaround like I did. |
How did you solve the issue? (apart from including the output in the result table) |
Hmm, i didn't actualy fix it in the libary and i dont know how to do that 2 be honest. I just create workaround. So basicaly if i need blockNumber or timeStamp of requested data i just call getBlock(121357248) method from web3 and get data for that block. I test balances in time 1 year ago, 1 month ago, 1 day ago and many more and for the latest he return correct data for the latest balance or closest block to them. For oldest data i dont find a way to compare them but i see difference between them and i workaround with theory that only blockNumber in 'response' is incorrect. in my case that solve a problem wich i had. |
The Problem
When I try to change the block number of the request, it doesn't effect the result at all
I were able to fix it by changing the way we feed the blocknumber in the contract call. (please take look at here
Can you check if I'm doing sth wrong or it's a bug with library. I can create a PR too if it's needed.
Code to replicate
The text was updated successfully, but these errors were encountered: