Category: Prover Projects

step 1: get the most important 2 ingredients:

when create a component like this:

there are two important thing:

• FrameworkComponent

• eval that implement FrameworkEval

we can see the example actually use two types of Component, one is from FrameworkComponent (MleCoeffColumnComponent), one is from MleEvalProverComponent, which is defined specifically for MLE …

GKR circuit:

a layer in GKR : proversrccorelookupsgkr_prover.rslayer

they take Mle: multi-linear extension as “input”.

Mle: corelookupsmle.rs

stored its evaluations on boolean hypercube, which is enough to uniquely determined the MLE

come back to the GKR layer struct, search where LogUpGeneric is used.…

continue from this blog

Another thought: proving everying thing together and logup by stwo as extra.

Building LogUp trace

basic steps:

• logup trace generator, size is determined.

let mut logup_gen = LogupTraceGenerator::new(log_size);

• generate columns that is associated with this logup trace generator

let mut col_gen = logup_gen.new_col();

• write fraction, building

related to this PR

Test case

cargo install --path ./cli-rs

compile with the correct field

powdr-rs compile riscv/tests/riscv_data/keccak -o output --field bb

cargo run --features stwo pil  output/keccak.asm --linker-mode native  -o output --force --field m31  --prove-with stworesult.txt

This can give keccak_opt.pil file with lookup identity, it is native lookup, …

following the first post 1

test command

RUST_LOG=stwo=trace cargo test --package powdr-pipeline --test pil --features stwo -- witness_lookup --exact --show-outputresult.txt

Implementation notes

Witness to BaseColumn

witness needs to be transformed into BaseColumns and then use the combine function to get fraction.

in Plonk example, all the witness columns are …

The reason I write this is because I saw the verification sample ood points are related to InfoEvalator. InfoEvalator contains this mask or mask offset information which basically embedded the circuit information.

This mask points of MleEvalProverComponent

Start with component built

when a component is buit, it takes a location_allocator, …

Powdr side:

run test in pipeline (I changed the test so it can include stwo):

#[test]
fn witness_lookup() {
    let f = "pil/witness_lookup.pil";
    let inputs = [3, 5, 2, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7]
        .into_iter()
        .map(GoldilocksField::from)
        .collect::<Vec<_();
    let pipeline = make_prepared_pipeline(f,