Learning new things!
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 stwoin Powdr, the proving function of Plonky3 is in function prove_with_key, in stark.rs
you can see the inputs for prove_with_key function has “air”, this is what used to define constraints, powdr gives “&circuit” to it, and it is a powdrcircuit, probably powdrcircuit applies the trait of AIR
so at this …
it is about this example in stwo
two parameters:
FIB_SEQUENCE_LENGTH specifies the rounds of fibo sequence
LOG_N_INSTANCES as stwo use SIMD, data parallel data struct, this number specify how many instances of fibo sequences are proved at the same time. The data are packed in LOG_N_LANES chunks, which is 16 …
following note1
packed31 is a vector of length 16
try to understand how the trace is generated
the bottom lines actually transfer the M31 values into circleDomain
from start:
N is log N instances
this code is to initialise the witness columns, later use to store the witness.
this code …