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

Add check to proof options to ensure they reach security level #71

Closed
diegokingston opened this issue Jun 13, 2023 · 0 comments · Fixed by #187
Closed

Add check to proof options to ensure they reach security level #71

diegokingston opened this issue Jun 13, 2023 · 0 comments · Fixed by #187
Labels

Comments

@diegokingston
Copy link
Contributor

diegokingston commented Jun 13, 2023

Taken from EthStark and paper

The conjectured security in this system is the minimum of three values:

log_n_cosets * n_queries + proof_of_work_bits (these are the parameters that appear in the parameter_file. Refer to the [Prover Inputs] section for details).
The collision resistance of the hash used by the protocol. This system employs Blake2s160 for the protocol, which is considered to provide 80 bits of security at the time of writing this project.
log(extension_field_size) - log(trace_length) (where the extension field is hardcoded to be of size 122 bits, and trace_length = (chain_length / 3) * 32 rounded up to nearest power of 2).

@gabrielbosio gabrielbosio linked a pull request Jul 18, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants