Utilise hardhat's debug_traceTransaction
zemse opened this issue · 1 comments
zemse commented
Interesting things that could be traced:
- Message call tree with decoded arguments and return data, including those calls that fail, along with decoding revert reason if possible.
- Counting occurrences of SLOADs and SSTOREs (or even allowing input of any valid opcode) in every message call.
- Storage Diff before and after.