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
Similar to #520, we could keep a name for the addresses generated, and show the name instead of value in the cli output.
For example something like TestToken.transfer(address,uint256)(0x253a67858fb108833d28d9388cdb62c73851eafe, 16433339) (addr=0xA647ff3c36cFab592509E13860ab8c4F28781a66, value=0, sender=0x0000000000000000000000000000000000030000)
Could become: TestToken.transfer(address,uint256)(user1, 16433339) (addr=user0, value=0, sender=sender2)
We could define a couple of naming convention, like:
deployer (deployerAddress from the config)
sender0, sender1, ... (senderAddresses from the config file)
user0, user1, ... for the EOA used in the function parameter
File.sol:ContractName0 for the contracts deployed through the fuzzing
We would still need to show the mapping at the end to avoid confusion, but I think that would make the cli output much easier to follow
The text was updated successfully, but these errors were encountered:
Similar to #520, we could keep a name for the addresses generated, and show the name instead of value in the cli output.
For example something like
TestToken.transfer(address,uint256)(0x253a67858fb108833d28d9388cdb62c73851eafe, 16433339) (addr=0xA647ff3c36cFab592509E13860ab8c4F28781a66, value=0, sender=0x0000000000000000000000000000000000030000)
Could become:
TestToken.transfer(address,uint256)(user1, 16433339) (addr=user0, value=0, sender=sender2)
We could define a couple of naming convention, like:
deployer
(deployerAddress
from the config)sender0
,sender1
, ... (senderAddresses
from the config file)user0
,user1
, ... for the EOA used in the function parameterFile.sol:ContractName0
for the contracts deployed through the fuzzingWe would still need to show the mapping at the end to avoid confusion, but I think that would make the cli output much easier to follow
The text was updated successfully, but these errors were encountered: