Learning new things!
the goal is to understand the extra cost (witness column) brought by using different field, in the bus part.
start with lookup_via_challenges_range_constraint.asm
use std::convert::fe;
use std::protocols::lookup::lookup;
use std::math::fp2::from_base;
use std::prover::challenge;
machine Main with degree: 8 {
// Prove a correct decomposition of x into 3-bit limbs
col fixed x = Trying to understand from this PR
understanding lookup.asm
let is_first: col = |i| if i == 0 { 1 } else { 0 };the above line, defines fix column, fix columns are columns known during circuit setup, independent of the what the witness will be. “i” represent the row …
The first place the challenger is called is in stark.rs prove function:
in circuit_builder.rs in plonky3, the ConstraintSystem has a field: challenges_by_stage, can check how this field is built.
in stark.rs, the constraintSystem is initialized from a pil file
Data struct has a challenges field, and has a get …
in backend/plonly3/stark.rs
there is a challenge test, to run it with trace logging, use the below command:
RUST_LOG=trace cargo test --features plonky3 --package powdr-backend --lib -- plonky3::stark::tests::challenge --exact --show-outputmore info comes out like:
to see a logging from a specific module add the module name in the …
need to get more detailed understanding of the concept of publics, isn’t it just some of the witness get revealed before the proving step?
following this …
Related type:
TraitsResolver helps to find the implementation for a given trait function and concrete type arguments.
TraitsResolver has a function resolve_trait_function_reference (see below) for a given polynomial reference, it resolves its trait
one of the input to this polynomialReference,
using fibo_no_public example, PolynomialReference looks like:
remove_trait_implsFiles structure:
In the context of programming, a prelude is generally a set of common imports or definitions that a module or program can use directly without needing to specify them every time. It acts like a convenience layer, making certain functions, traits, or types available by default.…
following the first post
got two tasks:
let’s talk about generate trace first.
in stwo, the trace is in this format as showed in last post
ColumnVec<CircleEvaluation<SimdBackend, BaseField, BitReversedOrder>>how powdr …
cargo run -r --features stwo pil test_data/pil/fibonacci.pil -o output -f --field m31 --prove-with stwo