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
I suggest that we add another parameter to ALL querys, using which you can execute queries not automatically to the current blockheight but to a lower blockheight.
This needs an archive node, since most nodes only have 100 heights saved. Anyways, we can catch that error and it might be helpful.
Flags:
--height int Use a specific height to query state at (this can error if the node is pruning state)
The text was updated successfully, but these errors were encountered:
@webmaster128 Hey, I am looking for this same functionality as well. I'm not sure that I follow how #1250 allows for querying with a block height? Or is there still some implementation needed for us to be able to do any query with a block height?
I suggest that we add another parameter to ALL querys, using which you can execute queries not automatically to the current blockheight but to a lower blockheight.
This needs an archive node, since most nodes only have 100 heights saved. Anyways, we can catch that error and it might be helpful.
The text was updated successfully, but these errors were encountered: