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
So, if selector is switched on some last rows, where witnesses are not allocated, satisfiability check will be passed, but table may not satisfy constraints on these last rows.
The text was updated successfully, but these errors were encountered:
* Added basic zkevm circuit.
* Bytecode circuit constraints added #364 (#375)
Co-authored-by: e.tatuzova <e.tatuzova@nil.foundation>
* Added real opcode numbers assignment.
* Added the new tests to the flake.
* Allocated_rows increased according to enable_selector #389
* Multiprecision changes.
* Updated crypto3 in fix attempt.
* Changed crypto3 to see other tests.
* Fixes for multiprecision update.
* Added missing test.
* Fixed test reporting not running if some tests failed.
* Fixed path in verifier test.
---------
Co-authored-by: e.tatuzova <e.tatuzova@nil.foundation>
Satisfiability check runs on blueprint assignment table "allocated_rows":
https://github.com/NilFoundation/zkllvm-blueprint/blob/master/include/nil/blueprint/utils/satisfiability_check.hpp#L63
allocated_rows increases when witnesses or selectors are set, but they are not changed by enable_selector function:
https://github.com/NilFoundation/zkllvm-blueprint/blob/master/include/nil/blueprint/blueprint/plonk/assignment.hpp#L368
So, if selector is switched on some last rows, where witnesses are not allocated, satisfiability check will be passed, but table may not satisfy constraints on these last rows.
The text was updated successfully, but these errors were encountered: