improve DBHash in preparation for iota2.0 #3255
Merged
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
There are now 3 "db hash" variants to choose for a test: * `VerifyDBHash` works as before: calculates a hash of the low-level DB contents (including the whole trie, all states, blocks, etc). * `VerifyStateHash` calculates a hash of the whole chain state at the latest state index. * `VerifyContractStateHash` calculates a hash of the state of a single core contract, at the latest state index. An optional prefix can be supplied to verify just a subset of the keys in the state. There is also a new DB_DUMP environment variable that can be used to store a hex dump of the DB contents, and later compute a diff between two different branches.
jorgemmsilva
approved these changes
Feb 6, 2024
| chainIDs := lo.Keys(env.chains) | ||
| slices.SortFunc(chainIDs, func(a, b isc.ChainID) int { return bytes.Compare(a.Bytes(), b.Bytes()) }) | ||
| for _, chID := range chainIDs { | ||
| chID := chID // prevent loop variable aliasing |
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.
There are now 3 "db hash" variants to choose for a test:
VerifyDBHashworks as before: calculates a hash of the low-level DB contents (including the whole trie, all states, blocks, etc).VerifyStateHashcalculates a hash of the whole chain state at the latest state index.VerifyContractStateHashcalculates a hash of the state of a single core contract, at the latest state index. An optional prefix can be supplied to verify just a subset of the keys in the state.There is also a new
DB_DUMPenvironment variable that can be used to store a hex dump of the DB contents, and later compute a diff between two different branches.