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

Brainstorming: support for getMappingSlotAt, getMappingLength and getMappingKeyAndParentOf #440

Open
bsamuels453 opened this issue Aug 12, 2024 · 1 comment

Comments

@bsamuels453
Copy link

We had to spend a ton of time re-creating the state machine for a recent invariant project because it held internal state that our fuzzing harness couldn't directly access.

I don't know which cheatcodes are used to allow these foundry functions to work, but I'm curious what the cost would be to add them to medusa:

  • getMappingSlotAt
  • getMappingLength
  • getMappingKeyAndParentOf

Basically a bunch of StdStorage.sol features would be incredible helpful for dealing with protocols with a lot of hidden internal state.

What would the cost of this support be?

@0xalpharush
Copy link
Contributor

For now, I would just use slither-read-storage and vm.load bc we may need to rethink how we're doing cheatcodes given how many issues we've had opened about them recently

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants