Issues: Consensys/gnark-crypto
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Optimize Legendre symbol
good first issue
Good for newcomers
new feature
perf
#489
opened Feb 22, 2024 by
yelhousni
Docu: Merkle tree documentation outdated or hashing of nodes in is incorrect
#482
opened Jan 30, 2024 by
Engeloid
iop.Polynomial.Evaluate should work in Lagrange/Lagrange shifted form
#463
opened Oct 19, 2023 by
ThomasPiellard
feat: define and implement field hasher implement for snark-friendly hash functions
new feature
#448
opened Sep 15, 2023 by
ivokub
get rid of putInExpectedFormFromLagrangeRegular
cleanup
Suggestion to clean up the code
#440
opened Aug 29, 2023 by
ThomasPiellard
zka.lc branch is behind
consolidate
strengthen an existing feature
#432
opened Jul 20, 2023 by
tumberger
perf: encoder / decoder of points, elements, should use bufio
perf
zk-evm
#423
opened Jul 1, 2023 by
gbotrel
bug: SIS discrepancy between Sage and gnark-crypto
bug
Something isn't working
#418
opened Jun 28, 2023 by
gbotrel
GKR challenge generation fails with option Something isn't working
fiatshamir.WithHash(hash, string)
bug
#417
opened Jun 27, 2023 by
Tabaie
serialization: add explicit
Unsafe
and Safe
paths for decoder.
perf
zk-evm
#392
opened May 3, 2023 by
gbotrel
Find a way to label and maintain a "maturity" level for packages (experimental... -> audited)
cleanup
Suggestion to clean up the code
consolidate
strengthen an existing feature
tests: add invalid test cases for subgroup check tests
consolidate
strengthen an existing feature
sec
Issue related to a security flaw
#350
opened Mar 3, 2023 by
ivokub
benchmark: consider the use of GOMAXPROCS in place of numCPU
#339
opened Feb 11, 2023 by
weikengchen
doc: have a warning in signature packages that operations are not constant time
consolidate
strengthen an existing feature
sec
Issue related to a security flaw
feat: implement signature Sign operations in constant time
new feature
question
Further information is requested
sec
Issue related to a security flaw
#317
opened Jan 26, 2023 by
ivokub
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.