feat(transforms): mask hardcoded constants to defeat bytecode-grep detection and error selector randomization#144
Open
g4titanx wants to merge 6 commits into
Open
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
This PR hardens azoth against static constant detection by adding ConstantMask to the default transform pipeline. The new pass rewrites eligible runtime and deployment literals so sensitive constants no longer appear as raw bytecode, including ERC-20 selectors, event topics, timeout literals, custom-error selectors, addresses, and fixture constants.
It also moves revert-selector handling into StringObfuscate, fixes related transform/finalization edge cases, and adds an e2e audit over the real escrow bytecode.
Key Changes