Skip to content

Consider moving verify_multi_opening outside of FK20 #255

@kevaundray

Description

@kevaundray

This has been taken from Benedikt Wagner's document.

There is a comment here re why its currently there:

/// Note: Although this method is on the `FK20Verifier` structure, it is possible to verify methods that are not

Related to #246

I'm still on the fence about it from a code organization perspective -- note that all of our "internal naive" provers have their own verifiers for simplicity. Though the complexity might just be an artifact of the current architecture. We could have a "provers" and "verifiers" folder for example, and the verifiers are just naive and optimized.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions