Mitigate accepted V12 audit findings - #14
Merged
Merged
Conversation
This file contains hidden or 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
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.
Summary
Each accepted mitigation is isolated in one commit and labeled with its V12 finding ID. Findings addressed by one shared mechanism are grouped in that mechanism's commit.
Audit mapping
The #227435 engine change is implemented in Deepstate-Protocol/deepstate-contracts#33 and pinned here at
59e5bb25a023d96a50a78fb1bd8504b5aa8e14ad.Validation
forge fmt --checkforge build --sizes --threads 0