solo: verify DB hash #2617
Merged
solo: verify DB hash #2617
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dessaya
force-pushed
the
statehash
branch
7 times, most recently
from
49ee89b
to
6bc6ed0
Compare
This is because `solc` does not produce a deterministic output: https://ethereum.stackexchange.com/questions/49806/solc-producing-different-contract-binary-depending-on-os
jorgemmsilva
approved these changes
Jun 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an attempt to address #2140 .
If a solo test is completely deterministic, then we can verify the DB hash at the end of the test. If we ever change the state contents (i.e. a breaking change), the hash will change, so the test will fail.