Description

I was working on a project that is using zk-snark to proof some properties of a machine learning model, and I realized all the existing code does not simulate a real-world scenario. Therefore, I created this example to simulate the interactions between prover anda verifier.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How has this been tested?

• Instructions are in the readme.txt

How has this been benchmarked?

• Benchmark A, on Macbook air M1, 8GB RAM

Checklist:

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• I did not modify files generated from templates
• golangci-lint does not output errors locally
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules