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

Use ZKSigma in stead of built in crypto.go #2

Merged
merged 5 commits into from
Mar 8, 2019

Commits on Feb 15, 2019

  1. Configuration menu
    Copy the full SHA
    77f0d78 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    87f7f09 View commit details
    Browse the repository at this point in the history
  3. Improved use of ZKSigma and related bugfixes

    This commit updates the using of ZKSigma in a couple ways:
    
    * It moves the ZKCurve into ZKLedger. This way ZKLedger drives the curve
    and G/H points in stead of ZKSigma dictating this.
    * Where appropriate, adopts the changed interfaces of making ZKSigma
    fully parameterized (passing in the curve where necessary)
    gertjaap committed Feb 15, 2019
    Configuration menu
    Copy the full SHA
    789a95a View commit details
    Browse the repository at this point in the history

Commits on Mar 1, 2019

  1. Configuration menu
    Copy the full SHA
    b507b83 View commit details
    Browse the repository at this point in the history

Commits on Mar 8, 2019

  1. Fixed comments

    gertjaap committed Mar 8, 2019
    Configuration menu
    Copy the full SHA
    ce11939 View commit details
    Browse the repository at this point in the history