lambdaworks icon indicating copy to clipboard operation
lambdaworks copied to clipboard

lambdaworks offers implementations for both SNARKs and STARKs provers, along with the flexibility to leverage their individual components for constructing customized SNARKs.

Results 137 lambdaworks issues
Sort by recently updated
recently updated
newest added
trafficstars

This issue involves: - Adding `as_conversions` lint as a warning at a workspace level. - Fixing the clippy warnings because of the above. For more context see [as_conversions](https://rust-lang.github.io/rust-clippy/master/#as_conversions).

good first issue

The canonical signed digit, or Non-Adjacent Form (NAF) is a unique way to represent a binary number with a lower absolute hamming weight, using `digit € {0,1,-1}` as coefficients instead...

I think that for the `Field` trait, rather than defining methods like `add`, `sub`, `mult`, `inv`, etc., they should leverage the `core::ops::Add` and others. If a trait for a method...

There is currently a naming convention on traits that they are supposed to start with something like `Is` or `Has`. We should get rid of it

Implement the `rand` traits for `ProjectivePoint` where `E: IsEllipticCurve`.

Building from the ground up with fuzzing in mind is always beneficial to libraries, especially ones that define their own types. Meaning the [Arbitrary trait](https://github.com/rust-fuzz/arbitrary) should be implemented for all...

# TITLE ## Description Description of the pull request changes and motivation. ## Type of change Please delete options that are not relevant. - [ ] New feature - [...

Adds the xgcd method for Polynomial to compute extended Euclidean algorithm

# Add Stark101 Prime Field ## Description I have been implementing the [Stark101 tutorial](https://starkware.co/stark-101/) using LambdaWorks (see [here](https://github.com/erhant/lambda-0b10/blob/main/snarks/stark101/)), and I had implemented the field used within the tutorial. The prime...