fuzzing

Using the same command from above:

$ cast tx 0xbedc92801b8a7128898f484006f9e9fb795630f1826f35dd3544db38c07594ab --rpc-url $ARBITRUM_RPC_URL

blockHash            0x918b0fbe7235f5a058890653f82c5e483ff0bbd1c84668e930e19b424e034540
blockNumber          9060440
from                 0x22222b7c879e6c09690d1e5eb10437e68987882c
gas                  0
gasPrice             0
hash             

When the computer is suspended during a fuzzing session, the time spent in suspended state is counted as a "run time" on a statistics screen. In case fuzzing was running for several hours and then the computer was suspended for several more hours, on one hand I would prefer not restarting the session, on the other hand, now it may be harder to tell how well a harness performs (corpus count vs. run

Hello everyone,
I think that the boofuzz documentation is good, but somehow not very useful for beginners.
In my opinion, the quickstart section is too short, leaving new users without any guidance on how to use this framework.
So I would suggest adding a whole section with detailed examples, covering at least the current examples,

I wonder if it was considered to add a rewrite step as a MSBuild target in the NuGet package. This way calling the tool coyote rewrite wouldn't be needed as that would be done automatically once the assembly is generated.

Could possibly be done if a specific property is provided like /p:CoyoteRewrite=true or be an opt-out when Configuration=Debug.