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

Histogram of DispatchResults #11

Open
kianenigma opened this issue Jun 3, 2024 · 0 comments
Open

Histogram of DispatchResults #11

kianenigma opened this issue Jun 3, 2024 · 0 comments

Comments

@kianenigma
Copy link

The main question i would have about this fuzzer before making it general to be used with any runtime is:

  1. what percentage of the blocks/extrinsics generated actually end up executing and doing something useful? If you have access to it, what is the histogram of Ok(_) vs Err(_)
  2. Similarly, we need a metric of the size of the state. Is it growing? It should, and if not, I would argue that the above histogram would also be all Err(_) and the runtime is not doing anything.

For example, I would expect a good fuzzer, with the genesis state of a single account having the total issuance to end up spreading the total issuance over many accounts after many iterations. But, is that actually happening?

This is the type of question I am trying to answer here.

I am aware that this fuzzer has already been very useful catching bugs, so maybe my skepticism is not needed, idk. What type of bugs have been detected? is it mostly in the API/Encode/Decode level, or has it also detected a bug deep in the logic of a pallet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant