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

OPTIMISATION: separate merkle commitments to L1 and merkle proofs generations as a separate job. #223

Open
matiwinnetou opened this issue Sep 14, 2023 · 0 comments
Open

OPTIMISATION: separate merkle commitments to L1 and merkle proofs generations as a separate job. #223

matiwinnetou opened this issue Sep 14, 2023 · 0 comments
Labels
Scalability

Comments

@matiwinnetou
Copy link
Contributor

Memory requirements and processing requirements for this are high, we could run this as a periodic job.

This design would also mean that voting-app could only focus on handling incoming votes without any danger for abusing it's operation due to loading votes, creation merkle tree and generation of merkle proofs.
@matiwinnetou matiwinnetou changed the title Separate merkle commitments to L1 and merkle proofs generations as a separate job. Optimisation: separate merkle commitments to L1 and merkle proofs generations as a separate job. Sep 14, 2023
@matiwinnetou matiwinnetou changed the title Optimisation: separate merkle commitments to L1 and merkle proofs generations as a separate job. OPTIMISATION: separate merkle commitments to L1 and merkle proofs generations as a separate job. Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Scalability
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@matiwinnetou