chore: update docs (#1671)

succinctlabs · Oct 18, 2024 · 4f15994 · 4f15994
1 parent d3bdd4e
commit 4f15994
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 11 deletions.
diff --git a/book/generating-proofs/proof-types.md b/book/generating-proofs/proof-types.md
@@ -26,11 +26,9 @@ let client = ProverClient::new();
 client.prove(&pk, stdin).compressed().run().unwrap();
 ```
 
-## Groth16
+## Groth16 (Recommended)
 
-> WARNING: The Groth16 prover requires around 64GB of RAM and only has prebuilt circuit artifacts on official releases of SP1. We recommend using the prover network to generate these proofs.
-
-The Groth16 prover mode generate a SNARK proof that is ~260 bytes large and can be verified onchain for around ~270k gas. Groth16 proofs take about ~30s longer to generate over a compressed proof.
+The Groth16 prover mode generate a SNARK proof that is ~260 bytes large and can be verified onchain for around ~270k gas. 
 
 The trusted setup for the Groth16 circuit keys uses the [Aztec Ignition ceremony](https://github.com/AztecProtocol/ignition-verification) + entropy contributions from members of the Succinct team.
 
@@ -41,8 +39,6 @@ client.prove(&pk, stdin).groth16().run().unwrap();
 
 ## PLONK
 
-> WARNING: The PLONK prover requires around 64GB of RAM and only has prebuilt circuit artifacts on official releases of SP1. We recommend using the prover network to generate these proofs.
-
 The PLONK prover mode generate a SNARK proof that is ~868 bytes large and can also be verified onchain for around ~300k gas. Plonk proofs take about ~1m30s longer to generate over a compressed proof.
 
 PLONK does not require a trusted setup.

diff --git a/book/getting-started/hardware-requirements.md b/book/getting-started/hardware-requirements.md
@@ -15,9 +15,9 @@ If you want to generate SP1 proofs locally, this section has an overview of the
 
 |                | Mock / Network               | Core / Compress                    | Groth16 and PLONK (EVM) |
 | -------------- | ---------------------------- | ---------------------------------- | ----------------------- |
-| CPU            | 1+, single-core perf matters | 16+, more is better                | 32+, more is better     |
-| Memory         | 8GB+, more is better         | 32GB+, more if you have more cores | 64GB+, more is better   |
-| Disk           | 20GB+                        | 20GB+                              | 12GB+                   |
+| CPU            | 1+, single-core perf matters | 16+, more is better                | 16+, more is better     |
+| Memory         | 8GB+, more is better         | 16GB+, more if you have more cores | 16GB+, more is better   |
+| Disk           | 10GB+                        | 10GB+                              | 10GB+                   |
 | EVM Compatible | ✅                           | ❌                                 | ✅                      |
 
 ### CPU
@@ -31,8 +31,7 @@ which can be parallelized with multiple cores.
 Our prover requires keeping large matrices (i.e., traces) in memory to generate the proofs. Certain steps of the prover
 have a minimum memory requirement, meaning that if you have less than this amount of memory, the process will OOM.
 
-This effect is most noticeable when using the Groth16 or PLONK provers, which requires around 128GB
-of RAM to generate a proof.
+This effect is most noticeable when using the Groth16 or PLONK provers.
 
 ### Disk