-
Notifications
You must be signed in to change notification settings - Fork 277
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
fix: put CommittedTransaction::error
in block hash
#5095
Conversation
Signed-off-by: Shanin Roman <[email protected]>
in other words, it's important that we don't include |
i think by checking this error we can assure that peers are on the same page at least to some extent (they all agree on outcome of each transaction in the block) |
we can do this without making this value a part of the block hash. The same way we circulate some other messages between peers however, if leader will not categorize instructions (for performance reasons), what good is this to us since there is no value to be agreed upon? In the case of block sync, yes we can reject the block if the value is incorrect. But we still don't have to protect the value with a hash |
not sure i got your point but, if we don't somehow check result of block execution peers have a risk of silently diverge |
I'm talking in the context of #4967 where we don't categorize transactions ahead of time. I don't see how we can have both. |
Will update after merge of #4967 |
Context
Error in
CommittedTransaction
was not reflected in the block hash which allowed for this value to be tempered result in block false rejection.Closes #5001.
Solution
Include error in block hash calculation.