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

Update security estimator to take into account method of batching #361

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Al-Kindi-0
Copy link
Contributor

Updates the estimator to take into account the method of batching used in computing the DEEP polynomial.
Note also:

  • I have updated the error term $\epsilon_3$ as this was missed in the previous PR which updated the error of the protocol to be the round-by-round error.
  • I have updated the conjectured security formula to match exactly the one given in the ethSTARK paper. Moreover, and as far as I can see, the formula is independent of the type of batching used and hence the security estimator for conjectured security is unaffected.

Copy link
Collaborator

@irakliyk irakliyk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Thank you! I left one small question inline.

Also, could we add a few tests to sanity check security estimate results for algebraic batching?

Comment on lines 35 to +36
// compute max security we can get for a given field size
let field_size = base_field_bits * options.field_extension().degree();
let field_security = field_size - (trace_domain_size * options.blowup_factor()).ilog2();
let field_security = base_field_bits * options.field_extension().degree();
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes conjectured security estimate a bit less conservative, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed, the conjecture implies that the soundness of the protocol is not affected by the domain size or, as far as I can see, the batching used in either the computation of the quotient polynomials or the DEEP polynomial.

@Al-Kindi-0
Copy link
Contributor Author

Also, could we add a few tests to sanity check security estimate results for algebraic batching?

Added a couple of tests to check for that.

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

Successfully merging this pull request may close these issues.

3 participants