Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use names for addresses #521

Open
montyly opened this issue Dec 15, 2024 · 0 comments
Open

Use names for addresses #521

montyly opened this issue Dec 15, 2024 · 0 comments
Labels
help wanted Extra attention is needed

Comments

@montyly
Copy link
Member

montyly commented Dec 15, 2024

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

@montyly montyly added the help wanted Extra attention is needed label Dec 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant