You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #1228 it was agreed that precompiles should still be fuzzed as inputs for normal fuzz tests - that is cool.
However, I don't see the point in fuzzing the precompiles as the msg.sender when running invariant tests. Forge should by default exclude all precompiles, because in the real world a precompile can never be the msg.sender of any Ethereum transaction.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Component
Forge
Describe the feature you would like
In #1228 it was agreed that precompiles should still be fuzzed as inputs for normal fuzz tests - that is cool.
However, I don't see the point in fuzzing the precompiles as the
msg.sender
when running invariant tests. Forge should by default exclude all precompiles, because in the real world a precompile can never be themsg.sender
of any Ethereum transaction.Additional context
No response
The text was updated successfully, but these errors were encountered: