Stats Analyzer Plugin

[SiddharthV1]

Closes # NethermindEth/IL-EVM#22

Changes

• Stats Analyzer:
  • Pattern Analyzer that serves JSON file traces of the stats of top patterns of 2-7 opcodes observed by the EVM during execution.
  • Call Analyzer that serves JSON file traces of the stats of top N contracts called over x blocks

What types of changes does your code introduce?

• [ ] Bugfix (a non-breaking change that fixes an issue)
• [x] New feature (a non-breaking change that adds functionality)
• [ ] Breaking change (a change that causes existing functionality not to work as expected)
• [ ] Optimization
• [ ] Refactoring
• [ ] Documentation update
• [ ] Build-related changes
• [ ] Other: Description

Testing

Requires testing

• [x] Yes
• [ ] No

If yes, did you write tests?

• [x] Yes
• [ ] No

Notes on testing

Documentation

Requires documentation update

• [ ] Yes
• [x] No

Requires explanation in Release Notes

• [ ] Yes
• [x] No

[MarekM25]

Is it better to have stats based on code_db or real execution? Of course, basing them on code_db is easier to implement.

[Scooletz]

Is it better to have stats based on code_db or real execution? Of course, basing them on code_db is easier to implement.

CodeDb has been already covered. This is to select TOP N in general and TOP N from the last block.