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

New features wish list #15

Closed
7 of 12 tasks
zemse opened this issue May 18, 2022 · 5 comments
Closed
7 of 12 tasks

New features wish list #15

zemse opened this issue May 18, 2022 · 5 comments
Labels
enhancement New feature or request

Comments

@zemse
Copy link
Owner

zemse commented May 18, 2022

  • Include panic error msg string
  • Allow specifying extra opcodes via cli
  • Implement opcode parsing for common opcodes initially (like add, mul and few more)
  • Check if rpc supports debug_tt before doing a mainnet fork
  • Handle invalid opcode for old solidity contracts (ethereum/solidity#9824))
  • Allow decoding events as well in the decode task
  • Automatically detect network when input hash in trace task
  • Add ability to export the generated trace as json
  • Display storage diff
  • Display trace for failed estimate gas.
  • Precompiles
  • Handle Incorrect return data length
@zemse zemse added the enhancement New feature or request label May 18, 2022
@shahnami
Copy link

shahnami commented Jun 14, 2022

Hi @zemse, awesome extension!

Would be nice to have an -o (--output) flag to export the trace in JSON as well.
Also, perhaps a way to diff the storage (to track what changed, or have this as part of the output).

zemse added a commit that referenced this issue Jul 18, 2022
zemse added a commit that referenced this issue Jul 18, 2022
zemse added a commit that referenced this issue Jul 18, 2022
zemse added a commit that referenced this issue Jul 18, 2022
@zemse zemse pinned this issue Jul 18, 2022
@tonisives
Copy link

Thanks for the great extension! One interesting idea would be to output a mermaid.js sequence diagram of some sort. (maybe reduce the function variables a bit so it's more readable).

It would give you a more visual overview of the components and stacktrace.

One other feature would be merging proxies and their implementation. Currently they basically print out duplicate traces.

@zemse zemse unpinned this issue Feb 20, 2023
@zemse
Copy link
Owner Author

zemse commented Feb 20, 2023

Thanks! I'll check it out.

@HarryR
Copy link

HarryR commented Apr 26, 2023

Thanks for the useful extension, it's really helped me get on-top of storage access patterns to reduce unnecessary loads & stores. Although Solidity still adds some unnecessary ones in there for good measure 🤷

It would be really useful to know the source line numbers where SLOAD and SSTORE calls are being triggered from.

@zemse
Copy link
Owner Author

zemse commented Apr 26, 2023

I agree, source lines would be useful. Though I wonder how to fit that in the console display since it already prints a lot of stuff which makes it overwhelming sometimes. Maybe behind a flag/config option. I've created an issue for this.

Closing this issue since these pending ones in this issue are in my backlog for a long time and I don't think I can do these anytime soon. But feel free to open a new issue about any feature that can be useful.

@zemse zemse closed this as completed Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants