lazovicff

# Overview We want to extend our suite of protococl implementations to one using PLONK as the zkSNARK backend. This requires rewriting our gadgets in the language of PLONK gates,...

Since plonk crates are excluded from the workspace, the CI wont run the coverage analysis on them. Instead we should run them manually for each crate that is not in...

[TASK] Sync the order of public inputs for R1CS and PLONK

1

For Mixer: 1. nullifier_hash 2. root 3. arbitrary data For Anchor: 1. chain_id 2. nullifier_hash 3. arbitrary_data 4. roots[] For VAnchor: 1. public_amount 2. public_chain_id 3. arbitrary_data 4. in_nullifier_hashes[] 5....

[TASK] Inline documentation

1

- Inline code documentation for all crates - Update readme to explain how the circuits work in more detail

# Overview A trusted setup ceremony is a multi-party computation conducted in order to generate initial randomized parameters for generating circuit-specific (in our case) proving and verifying keys. The trusted...

Instead of creating a circuit for each test case for our PLONK gadgets, we should use the following function: https://github.com/ZK-Garage/plonk/blob/master/plonk-core/src/constraint_system/composer.rs#L541 The benefits: - We could debug in more detail which...

Since we are using AccountId([u8; 32]) as out account ids, we should not use `truncate_and_pad` which will replace last 12 bytes with zeros, leaving for potential to collisions, which can...

TBA