pipelining of users contributions

[ctrlc03]

Problem

Currently it is not possible to contribute to large circuits > 1M constrains on a browser due to memory restrictions. For that, we use a cli tool instead where we can use the full computing power of a machine.

Possible solution

Pipelining the contribution of a user.

Flow:

• Download n chunk -> process n chunk -> (upload n chunk)

By processing the computation on one chunk at a time, we can effectively reduce the memory consumption as we do not need to hold the whole file in memory at all times. This could possibly allow even larger contributions on a mobile phone's browser.

What we would need to change

We would need to first validate this is possible to do the computation on chunks rather than the whole zKey.

1. Amend the current backend step system. This is quite strict, there's certain actions which can only be done on when at a certain step (for instance cannot get an upload pre-signed url when not in the upload phase, etc.). (medium complexity)
2. This approach described above requires some changes on snarkjs' code.

[glamperd]

Not planned for now

[healthykim]

I was monitoring this issue because I wanted to contribute, but it suddenly got closed. Could you let me know why it was closed?

[glamperd]

I can reopen if you want to contribute.

[healthykim]

Thank you!
I found a similar issue in a repository named 'DefinitelySetup' (privacy-scaling-explorations/DefinitelySetup#97).
Should I work on DefinitelySetup since it involves on-browser contributions?

[glamperd]

This would need changes to the backend. They should happen in p0tion (backend package). Browser-based front-end changes will be in DefinitelySetup.