-
Notifications
You must be signed in to change notification settings - Fork 2
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
Retry logic when "wheel" is not good enough #2
Commits on Sep 13, 2024
-
Add (failing) test for retry logic
* Also add manual serialisation of Proof + roundtrip test as it cannot be automatically derived anymore * Write a test that crashes because proof cannot be generated * Add a retryCount field for the Proof to implement the logic
Configuration menu - View commit details
-
Copy full SHA for 7166769 - Browse repository at this point
Copy the full SHA 7166769View commit details -
Configuration menu - View commit details
-
Copy full SHA for 507f83e - Browse repository at this point
Copy the full SHA 507f83eView commit details -
Retry proof an unbounded number of times
Property is a bit long to run as it now needs to repeat the whole proving process several times for a small set.
Configuration menu - View commit details
-
Copy full SHA for bf67953 - Browse repository at this point
Copy the full SHA bf67953View commit details -
Configuration menu - View commit details
-
Copy full SHA for 29d86bc - Browse repository at this point
Copy the full SHA 29d86bcView commit details -
Configuration menu - View commit details
-
Copy full SHA for b59ad3e - Browse repository at this point
Copy the full SHA b59ad3eView commit details -
Replace State monad with ST computation
Even without benchmark, it's obvious from running tests State monad will be unbearably slow
Configuration menu - View commit details
-
Copy full SHA for 12590e7 - Browse repository at this point
Copy the full SHA 12590e7View commit details -
Bound DFS with number of hashes in the "small" set case
This completely ditch ST or State monad based computation which are way too expensive.
Configuration menu - View commit details
-
Copy full SHA for e486559 - Browse repository at this point
Copy the full SHA e486559View commit details -
Use different bounds for nr. of hash depending on honest set size
Note the test case does not actually matches the expected theoretical values. The average and max number of proof run should be 1 when n_p is greater than λ³ but it's not the case.
Configuration menu - View commit details
-
Copy full SHA for ea49f26 - Browse repository at this point
Copy the full SHA ea49f26View commit details -
Configuration menu - View commit details
-
Copy full SHA for 35716c7 - Browse repository at this point
Copy the full SHA 35716c7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0db1d97 - Browse repository at this point
Copy the full SHA 0db1d97View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2fa1105 - Browse repository at this point
Copy the full SHA 2fa1105View commit details -
Also improve readability of benchmarks' label
Configuration menu - View commit details
-
Copy full SHA for 7e21883 - Browse repository at this point
Copy the full SHA 7e21883View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9f634d1 - Browse repository at this point
Copy the full SHA 9f634d1View commit details -
Configuration menu - View commit details
-
Copy full SHA for aa0ca13 - Browse repository at this point
Copy the full SHA aa0ca13View commit details -
Configuration menu - View commit details
-
Copy full SHA for 824418d - Browse repository at this point
Copy the full SHA 824418dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2dc09eb - Browse repository at this point
Copy the full SHA 2dc09ebView commit details -
Configuration menu - View commit details
-
Copy full SHA for c9240f2 - Browse repository at this point
Copy the full SHA c9240f2View commit details