Add script to check block composition #131
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a script that checks how many swaps and transfer an average block has. This done through the collection of entrypoints executed during bechmarking a block-range. There are some patterns that pure transfers and swaps share with each other. This plus the fact that the
transfer
entrypoint seems to have the same hash across different contracts, may make us able to define what makes a transaction to be a transfer.I also had to organize differently the data about the entrypoint executed that is written in a .json file at the end of benchmark, since before it was just the entrypoints with no separation by block or group of entrypoints.
To be able to run the script first you need to collect some data:
Then you run the script: