You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a worker starts, it only knows the coordinator url.
Then it fetches a task from the coordinator, {circuit_id, witness}. If it does not know about the circuit, then it fetches the circuit information from the coordinator ( req: circuit_id, resp: { r1cs_url, srs_monomial_form_url, srs_lagrange_form_url} ). Then the worker can save the circuit locally ( both memory and local file is ok ).
( url can be s3 url or http url )
worked_id is generated as uuid locally.
The text was updated successfully, but these errors were encountered:
We may need to prove different circuits in the future ( block / exit tree , of different size / n_tx ) . So fetching circuit details from master seems more flexible ?
lispc
changed the title
feat: make worker more stateless
feat: make worker more "stateless"
Jul 8, 2021
When a worker starts, it only knows the coordinator url.
Then it fetches a task from the coordinator, {circuit_id, witness}. If it does not know about the
circuit
, then it fetches the circuit information from the coordinator ( req: circuit_id, resp: { r1cs_url, srs_monomial_form_url, srs_lagrange_form_url} ). Then the worker can save the circuit locally ( both memory and local file is ok ).( url can be s3 url or http url )
worked_id is generated as uuid locally.
The text was updated successfully, but these errors were encountered: