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

Should we have a system fuzzer? #1545

Closed
ludamad opened this issue Aug 11, 2023 · 0 comments
Closed

Should we have a system fuzzer? #1545

ludamad opened this issue Aug 11, 2023 · 0 comments
Labels
T-question Type: Someone is asking a questions about something

Comments

@ludamad
Copy link
Collaborator

ludamad commented Aug 11, 2023

Idea is to have modules for generating random samples of any conceivable part of a valid transaction (contract, contract calls with inputs that refer to existing notes, etc) and have a long (but seeded randomness) fuzzing process kick off every night, running some amount of time proportional to how much variability there is in the fuzzer.

Would require ability to create random examples of Noir contracts. This might be useful either way, and can be done incrementally. Or we could settle for calling a variety of them.

No priority in mind, but seems good to smoke test for stability (e.g. no new shallow race conditions) before updating a test-net.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-question Type: Someone is asking a questions about something
Projects
Archived in project
Development

No branches or pull requests

1 participant