Skip to content

fix: either commit to groth16 and do proper setup or change proof systems #110

@distractedm1nd

Description

@distractedm1nd

Not only do we not have a setup ceremony, but we create a new VerifyingKey for every single epoch. Moving them would require us to rewrite the circuits a bit, because the structure of them is not constant enough to reuse a VerifyingKey across batches.

If we stick with groth16 we need to rewrite the circuits anyways to have a reusable setup, as well as writing the setup ceremony code. Alternatively we can bite the bullet and switch to nova, which I am experimenting with in #109 (but have not gotten very far yet).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions