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
Copy file name to clipboardExpand all lines: docs/learn/type-1-prover/deploy-t1-prover.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
This document provides guidelines on how to run Polygon Type-1 prover, specifically for proving transactions, but with the option to test full blocks of less than 4M gas.
2
2
So, it is similar to [`eth-proof`](https://github.com/wborgeaud/eth-proof) but for transaction proofs.
3
3
4
-
## Quick Start
4
+
## Quick start
5
5
6
6
There are two ways to run this prover. The simplest way to get started is
7
7
to use the `in-memory` runtime of
@@ -52,7 +52,7 @@ is the _last_ transaction hash in the block.
52
52
Once you've successfully generated a witness, you're ready to start
53
53
proving either with the `in-memory` run time or the `amqp` runtime.
54
54
55
-
### In Memory Proving
55
+
### In-memory proving
56
56
57
57
Running the prover with the `in-memory` setup requires no setup. You
58
58
can attempt to generate a proof with a command like this.
@@ -78,7 +78,7 @@ state root of the preceding block. You can adjust the `--num-workers`
78
78
flag based on the number of available compute resources. As a rule of
79
79
thumb, you'd probably want at least 8 cores per worker.
80
80
81
-
### AMQP Proving
81
+
### AMQP proving
82
82
83
83
Proving in a distributed compute environment depends on an AMQP
84
84
server. We're not going to cover the setup of RabbitMQ, but assuming
0 commit comments