Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a verifier without the need of access to the registered parcipants #162

Closed
iquerejeta opened this issue Apr 28, 2022 · 0 comments · Fixed by #159
Closed

Create a verifier without the need of access to the registered parcipants #162

iquerejeta opened this issue Apr 28, 2022 · 0 comments · Fixed by #159
Assignees
Labels
D-easy Difficulty: easy P-high Priority: high T-design Type: discuss API design and/or research

Comments

@iquerejeta
Copy link
Contributor

Now, signatures can only be verified by an StmClerk

pub struct StmClerk<H, E>
where
    H: MTHashLeaf,
    E: ProverEnv,
{
    avk: Arc<MerkleTree<H>>,
    params: StmParameters,
    total_stake: Stake,
    proof_env: E,
    proof_key: E::ProvingKey,
    verif_key: E::VerificationKey,
}

The avk is represented as the full MerkleTree. However, for the proof verification, we only need the merkle commitment. To this end, we'll build a new entity, Verifier, which will only contain the minimal data needed to verify aggregated signatures.

@iquerejeta iquerejeta added P-high Priority: high D-easy Difficulty: easy T-design Type: discuss API design and/or research labels Apr 28, 2022
@iquerejeta iquerejeta self-assigned this Apr 28, 2022
@iquerejeta iquerejeta mentioned this issue May 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
D-easy Difficulty: easy P-high Priority: high T-design Type: discuss API design and/or research
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant