-
Notifications
You must be signed in to change notification settings - Fork 1
Questions about PRIME_BITLEN and round number #4
Comments
No, you cannot. As specified in the comments (see below), Plonk-Prototype/src/poseidon/round_numbers.rs Lines 3 to 6 in bae3f95
Yes. For example, if you run "python2 calc_round_numbers.py 762 3 128 1 1", you will have (R_F, R_P) = (8, 55). This matches hardcoded tests: Plonk-Prototype/src/poseidon/round_numbers.rs Line 101 in bae3f95
|
Thanks for your reply.
|
It is indeed more complex than that. The properties used to compute round numbers also change from the current implementation. You may also need to update alpha. Please check the paper for properly selecting round numbers for other curves. |
ty, I'll check it. |
Plonk-Prototype/src/poseidon/round_numbers.rs
Line 7 in bae3f95
Can we always use
PRIME_BITLEN=256
to compute round number for different fields?Another question about round number
Does the round number generated in the repo(rust) still have the same result with reference from the python script here?
I don't know why I could not get the same result.
Btw, for generate_parameters_grain_deterministic.sage and poseidonperm_bls381_width3.sage, I can get the same result with rust code even for different fields.
The text was updated successfully, but these errors were encountered: