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

how could I use this practically? #2

Closed
darkedges opened this issue Sep 5, 2021 · 0 comments
Closed

how could I use this practically? #2

darkedges opened this issue Sep 5, 2021 · 0 comments

Comments

@darkedges
Copy link

darkedges commented Sep 5, 2021

Reading throught the example it seems that I need to have access to the list of publickeys so that I can generate a proof of the signature.

So here is my thinking

  1. Generate KeyPair
  2. Submit public key to an endpoint that adds it to the list
  3. generate Signature and submit to an endpoint that generates the proof
  4. give the proof to the requester
  5. requester submits proof to an endpoint that validates the proof.

This now adds some complexity, as I need to keep the list of Public Keys in memory / data store and reference that list each time. So I would need a mechanism that would scale. Or am i wrong in that thinking and there is a short cut to keeping the generated proofs valid whilst not maintaining the list.

Please close if there is a better forum for this.

Regards
Nicholas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant