Skip to content
This repository has been archived by the owner on Jul 5, 2024. It is now read-only.

[proof-chunk] explore snark-verifier in root circuit to append custom protocols #1602

Closed
Tracked by #1498
hero78119 opened this issue Sep 14, 2023 · 3 comments
Closed
Tracked by #1498
Assignees

Comments

@hero78119
Copy link
Member

hero78119 commented Sep 14, 2023

Based on proof chunk design we need to add some custom protocols aside from original super-circuit protocol.

First there is requirement to using poseidon hash to compute permutation fingerprint challenge based on column commitment. and an optimise version is appending poseidon hash protocol (circuit) at the end of of supercircuit protocol once, giving there might be more supercircuit protocol for more than once chunk.

We can support fixed number of super circuit proof with empty proof padding. It will also be nice to leave door open to support dynamic number supercircuit proof.

There are also some custom protocols. In summary

  • poseidon hash to compute challange
  • constraint between super-circuit proofs, e.g. rwtable column consistency across proof via public input, challenge consistency across proof.
  • assure some flag toggle on at last supercircuit proof (via public input ?)
  • assure challenge equality with last chunk
@hero78119
Copy link
Member Author

Hey @han0110 do you have any input based on the proposol ?

@hero78119 hero78119 changed the title [proof-chunk] explore snark verifier to support poseidon hash protocol [proof-chunk] explore snark-verifier in root circuit to append custom protocols Sep 14, 2023
@han0110
Copy link
Collaborator

han0110 commented Sep 14, 2023

I feel we don't need to change snark-verifier to support these, snark-verifier could be seen as a tool to verify a plonk proof only, and later on you could reuse the commitments to do further checks, so perhaps Root circuit will be the target to update.

@hero78119
Copy link
Member Author

Updated

fingerprint equality on last chunk is done in super circuit #1674

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

4 participants