You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* feat: add emulated builder init
* fix: do not assumed reduced elements in div
* feat: add secp256k1 scalar field
* refactor: export Field
* refactor: export modular reduction method
* feat: allow select/lookup2 on non-reduced inputs
* chore: remove invalid comments
* perf: mod reduce after multiplication
* perf: update optimisation test
* refactor: hint helpers as field methods
* refactor: remove field params from element
* refactor: separate non-native field from api wrapper
* refactor: use nonnative elm pointers
* refactor: call EnforceWidth in PackLimbs
* refactor: add new element constructor
* feat: do not range-check in-circuit ops
* style: remove temp allocations
* feat: add MulMod nonnative op
* feat: add mutable variants of ops
* feat: add mul by const
* test: update circuit statistics
* test: update emulation constraint count
* feat: add bn254 fields and unify param names
* docs: update field emulation docs
* docs: add examples into documentation
* test: add test case for #348
* chore: remove dead code
* docs: fix method docs
Technically, the API encourages the use of
NewElement[T]
orAssign
which will build element with correct number of limbs.But since these limbs are unconstrained, there is no soundness guarantees at the proof system level.
The text was updated successfully, but these errors were encountered: