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.

Sign up for GitHub

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

Jump to bottom

Hide PreparedVerifyingKey #430

Closed
Tracked by #347
th7nder opened this issue Oct 7, 2024 · 0 comments · Fixed by #440
Closed
Tracked by #347

Hide PreparedVerifyingKey #430

th7nder opened this issue Oct 7, 2024 · 0 comments · Fixed by #440
Milestone
Phase 2

Comments

@th7nder
Copy link
Contributor

th7nder commented Oct 7, 2024 

          I'm not sure whether we'll use `PreparedVerifyingKey` multiple times in the same context if we don't store it on-chain. I also don't think it'll ever be the case that on-chain we verify multiple SNARK proofs.

Right now I was only thinking about hiding the complexities of the API from the user

Originally posted by @th7nder in #413 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Phase 2
Development

Successfully merging a pull request may close this issue.

feat(pallet-proofs): expose the proof interface to other pallets eigerco/polka-storage
1 participant
@th7nder