Giters

zemse / hardhat-tracer

🕵️ allows you to see internal calls, events and storage operations in the console

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Utilise hardhat's debug_traceTransaction

zemse opened this issue · comments

commented

(Documentation)

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.
commented

It turned out using the debug_tt consumed a lot of memory. So in the next rewrite the plugin directly gets debug info from the low level VM in hardhat. This makes it comparatively very memory efficient. Please checkout the v2-beta branch for more info.