-
Notifications
You must be signed in to change notification settings - Fork 793
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
Calling steem.api.getBlock for new block returns block which is not added to blockchain #3632
Comments
can you share the detailed commands? |
Some of the witnesses are reversing blocks (bad practice). |
it should be caused by various witnesses running different versions and this is causing microforks. a major version hard fork is on a discussion which would ensure all witnesses would be running the same version. we will keep monitoring this issue. |
Yes, that's exactly what I think I experience. Is there a way to ensure I read block which will not be reversed? |
Some of the witnesses blocking users funds (bad practice) |
Just use the |
This is true unless witness fork a chain from before last_irreversible_block_num. I believe this happens much on Steem last days creating mini-forks. |
If I call
steem.api.getBlock(blockNuber)
for a newly created block it returns sometimes block similar to this one (I removed part of block cause github doesn't allow such long messages):
If call:
steem.api.getBlock(blockNuber)
few seconds later I receive different block.
I think, it's critical bug, please fix this.
`
The text was updated successfully, but these errors were encountered: