plotchy
plotchy
Ityfuzz uses these standard mutations from libafl ```rust let mutations = tuple_list!( BitFlipMutator::new(), ByteInterestingMutator::new(), WordInterestingMutator::new(), DwordInterestingMutator::new(), ConstantHintedMutator::new(), ); ``` But using a more evm-specific mutator for incrementing or decrementing inputs...
While testing corpus additions on better comparisons I found that `CMP_MAP` is getting polluted by the contract deployers. Since `step` in the Host is used during contract setup and deployment,...
I've been looking to add in a middleware that does contract analysis whenever new code is discovered. I looked for similar ideas that already are in the codebase, but many...
Ityfuzz selects mutators on random chance. There are two hyperparameters that can affect overall mutation: - MAX_STACK_POW (used in libafl to determine how many times in a row to mutate...
Since the EVM is stateful, and all interesting things onchain occur during a stateful operation, what if we targeted those during the fuzz run? There is some research around targeting...