frost/secp256k1-zkp
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc: Fix upper bounds + cleanup in field_5x52_impl.h comment

Browse Source
This commit is contained in:
Elliott Jin 2021-12-03 08:36:49 -08:00
parent 486205aa68
commit 58da5bd589
1 changed files with 12 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
src/field_5x52_impl.h
View File

@ -22,11 +22,18 @@
#endif #endif
/** Implements arithmetic modulo FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFE FFFFFC2F, /** Implements arithmetic modulo FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFE FFFFFC2F,
* represented as 5 uint64_t's in base 2^52. The values are allowed to contain >52 each. In particular, * represented as 5 uint64_t's in base 2^52, least significant first. Note that the limbs are allowed to
* each FieldElem has a 'magnitude' associated with it. Internally, a magnitude M means each element * contain >52 bits each.
* is at most M*(2^53-1), except the most significant one, which is limited to M*(2^49-1). All operations *
* accept any input with magnitude at most M, and have different rules for propagating magnitude to their * Each field element has a 'magnitude' associated with it. Internally, a magnitude M means:
* output. * - 2*M*(2^48-1) is the max (inclusive) of the most significant limb
* - 2*M*(2^52-1) is the max (inclusive) of the remaining limbs
*
* Operations have different rules for propagating magnitude to their outputs. If an operation takes a
* magnitude M as a parameter, that means the magnitude of input field elements can be at most M (inclusive).
*
* Each field element also has a 'normalized' flag. A field element is normalized if its magnitude is either
* 0 or 1, and its value is already reduced modulo the order of the field.
*/ */
#ifdef VERIFY #ifdef VERIFY