Replies: 2 comments 2 replies
-
Definitely a solid proposal and one that would get us across the finishing line as soon as possible, and love the focus around security. Have you considered how to parallelize proof generation? Given each time we process messages there will be batches, it could be more efficient to separate the processing that happens inside Poll.ts and the proof generation part. The first part needs to be sequential, however the proof generation part is usually slower and can happen in parallel as soon as we get the inputs for the first batch. |
Beta Was this translation helpful? Give feedback.
-
I have a question, how would we deal with the problem we mentioned before -> protecting user's keys? |
Beta Was this translation helpful? Give feedback.
-
Description
As a coordinator I'd like to run proof generation commands remotely without using cli, so there is an idea to create proof generation service.
Acceptance criteria
maci-cli
ormaci-contracts
flow to generate proofsmaci-cli#genProofs
commandArchitecture
This service is supposed to be a stateless service, so there are several components:
The flow will look like:
Tech stack
The idea is to use this boilerplate https://github.com/privacy-scaling-explorations/maci/tree/dev/coordinator with Typescript + NestJS, and keep as less dependencies as possible.
Nice to have
Beta Was this translation helpful? Give feedback.
All reactions