zkllvm-blueprint

zkllvm-blueprint copied to clipboard

Good to have for all other components too, but this is vital for grinding.

Iluvmagick

We need asserts with readable error messages for: - [ ] not enough witness columns - [ ] not enough component constant columns - [ ] not enough lookup constant...

ETatuzova

Current status: - Update for all_vars created errors - keccak.hpp needs constraints and for keccak_round.hpp calls to be added - check keccak_round.cpp because the tests passed one by one but...

tshchelovek

ETatuzova

A mid-level task between the low-level comonents (Fp12 arithmetic and elliptic curve points operations) and the whole BLS12-381 component suite. Should include: - the Miller loop subcomponent; - the exponentiation...

ayashunsky

We need to implement components for BLS12-381 signature verification (hash-to-point, paring, is-in-group). The subcomponents for working with elliptic curves and extension fields are part of issue https://github.com/NilFoundation/zkllvm-blueprint/issues/281.

ayashunsky

We need to implement components for BLS12-381 signature verification. The basic set of low-level subcomponents needed for pairing computation includes components for working with G2 elliptic curve points and elements...

ayashunsky

For small n (e.g. 8 for now) we can do a range_check via lookup argument. Might be able to abuse other tables for that, although unsure how would a generic...

Iluvmagick

Component testing framework assumes all constants are placed in a single column.

1

https://github.com/NilFoundation/zkllvm-blueprint/blob/93b6463d8d6378e08994c3208fbed34f90b30fa7/test/test_plonk_component.hpp#L286C38-L286C38 The component tester assumes that all components use at most 1 column for constants. We have components that in some configurations where the component fits into a single row,...

dkales

Failing tests

2

This is a meta-issue for all the tests I've found failing on current master as of time of [this issue's] creation. Each of theses is likely to be fixed in...

Iluvmagick