From 261de3dad994e4fb1442fc8f1e555fefea519198 Mon Sep 17 00:00:00 2001 From: Ho Date: Fri, 14 Nov 2025 14:30:42 +0900 Subject: [PATCH] readme --- tests/prover-e2e/README.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/tests/prover-e2e/README.md b/tests/prover-e2e/README.md index 44ee4097c..a6bb0444b 100644 --- a/tests/prover-e2e/README.md +++ b/tests/prover-e2e/README.md @@ -9,9 +9,8 @@ link the staff dir as "conf" from one of the dir with staff set, currently we ha Steps: 1. run `make all` under `tests/prover-e2e`, it would launch a postgreSql db in local docker container, which is ready to be used by coordinator (include some chunks/batches/bundles waiting to be proven) -2. download circuit assets with `download-release.sh` script in `zkvm-prover` -3. generate the verifier stuff corresponding to the downloaded assets by `make gen_verifier_stuff` in `zkvm-prover` -4. setup `config.json` and `genesis.json` for coordinator, copy the generated verifier stuff in step 3 to the directory which coordinator would load them -5. build and launch `coordinator_api` service locally -6. setup the `config.json` for zkvm prover to connect with the locally launched coordinator api -7. in `zkvm-prover`, launch `make test_e2e_run`, which would specific prover run locally, connect to the local coordinator api service according to the `config.json`, and prove all tasks being injected to db in step 1. \ No newline at end of file +2. setup assets by run `make coordinator_setup` +3. in `coordinator/build/bin/conf`, update necessary items in `config.template.json` and rename it as `config.json` +4. build and launch `coordinator_api` service locally +5. setup the `config.json` for zkvm prover to connect with the locally launched coordinator api +6. in `zkvm-prover`, launch `make test_e2e_run`, which would specific prover run locally, connect to the local coordinator api service according to the `config.json`, and prove all tasks being injected to db in step 1. \ No newline at end of file