Skip to content

Commit db5a2b0

Browse files
committed
docs: update readme instructions
1 parent 9f94d11 commit db5a2b0

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

aggregation-mode/readme.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -18,27 +18,27 @@ make anvil_start_with_block_time
1818
make start_batcher_local
1919
```
2020

21-
4. Start proof aggregator:
21+
4. Send SP1 proofs:
22+
```shell
23+
make batcher_send_sp1_burst
24+
```
25+
26+
5. Start proof aggregator:
2227
```shell
2328
# This will not run a real prover but a mocked one see below to run a real prover
2429
make start_proof_aggregator_local
2530
```
2631
Note: it might take a while to compile as it uses more aggressive optimization levels.
2732

28-
5. Send SP1 proofs:
29-
```shell
30-
make batcher_send_sp1_burst
31-
```
32-
33-
You should see that after the timer set in `config-proof-aggregator.yaml`, it will fetch the batches and aggregate the compressed SP1 proofs from them.
33+
You should it will fetch the new batch logs from the BatcherService and aggregate the compressed SP1 proofs from them.
3434

3535
### Run it with proving
3636

3737
By default, on dev environments, the proving is mocked and the ProofAggregationService contract skips verification as proves are mocked. To run the service with proving you need to run change the commands on step `1.` and `4.`:
3838

3939
1. Start anvil with verification activated:
4040
```shell
41-
make anvil_start_with_block_time_and_proving
41+
make anvil_start_with_verification
4242
```
4343

4444
4. Start proof aggregator with proving:

0 commit comments

Comments
 (0)