chore(docs-site): update network config and add batch proof guide (#1…

…8776)
taikoxyz · Jan 15, 2025 · 8710cd8 · 8710cd8
1 parent b359be0
commit 8710cd8
Show file tree

Hide file tree

Showing 3 changed files with 41 additions and 3 deletions.
diff --git a/packages/docs-site/src/assets/content/docs/network-reference/proof-tier-config-hekla.webp b/packages/docs-site/src/assets/content/docs/network-reference/proof-tier-config-hekla.webp
diff --git a/packages/docs-site/src/content/docs/guides/node-operators/enable-a-prover.mdx b/packages/docs-site/src/content/docs/guides/node-operators/enable-a-prover.mdx
@@ -34,12 +34,38 @@ These are the bare minimum required settings along with a functional Taiko node
 
 </Steps>
 
+Please find all relevant bond, cooldown, and proving window information [here](/network-reference/network-configuration/#cooldown-window-proving-window-and-bonds).
+
+## Enabling batch proving/proof aggregation (optional)
+
+<Aside type="danger">
+We don't recommend users utilize this function unless they already run a fairly active and successful proposer.
+
+By enabling proof aggregation, you will be opening yourself up to more risk as you will be putting up more TAIKO as bond at one time.
+
+The recommended value for SGX_BATCH_SIZE is 10+ as you will see the most gas saved at this value and above. We will NOT refund any lost bonds due to misconfiguration, please evaluate and use this function at your own risk.
+
+We highly recommend you test the function on Hekla before enabling it for mainnet.
+</Aside>
+
+Batch proving has been enabled in release 0.43.0 of [the taiko alethia client!](https://github.com/taikoxyz/taiko-mono/releases/tag/taiko-alethia-client-v0.43.0)
+
+Please use [simple-taiko-node release 1.8.2](https://github.com/taikoxyz/simple-taiko-node/releases/tag/v1.8.2) or above to enable this functionality.
+
+**This functionality can be enabled simply by setting `SGX_BATCH_SIZE` in your `.env` file to a number greater than 1.**
+
+If it is set to 1 or unset your prover will submit proofs upon assignment (standard function).
+When enabled, your prover will submit a batch of proofs when x number of blocks are assigned, x being `SGX_BATCH_SIZE`.
+
+As provers are given a proof window for every assigned proof, it can become the case that while waiting for a batch size to be fulfilled the already assigned proofs exit their proof window and become unassigned.
+To prevent this, we have introduced another flag `FORCE_BATCH_PROVING_INTERVAL`. This flag will only be functional if batch proving is enabled.
+
+This flag will force the prover to submit a batch of proofs every x minutes, regardless of the batch size being fulfilled. We don't recommend this value be set > 45 minutes, as the provingWindow is 60 minutes and any closer will put you at risk of having proof assignments expire. It is by default set to 30 minutes.
+
 <Aside>
 The following steps can be done through the [ProverSet contract](/guides/node-operators/deploy-a-proverset/#deploying-a-proverset) if you have deployed one. We highly recommend this for a stable setup.
 </Aside>
 
-Please find all relevant bond, cooldown, and proving window information [here](/network-reference/network-configuration/#cooldown-window-proving-window-and-bonds).
-
 ### Approve TaikoL1 as TAIKO spender (mainnet)
 
 <Steps>

diff --git a/packages/docs-site/src/content/docs/network-reference/network-configuration.mdx b/packages/docs-site/src/content/docs/network-reference/network-configuration.mdx
@@ -13,7 +13,7 @@ The cooldown window describes how long after the proof has been provided that th
 
 The proving window describes how long a prover has to provide a proof for a block after they have been assigned the block (i.e. a block has been proposed with them as the assigned prover).
 
-You can find all the corresponding values below in the [deployed TierProviderBase contract](https://etherscan.io/address/0x394E30d83d020469a1F8b16E89D7fD5FdB1935b0#code#F3#L1)!
+You can find all the corresponding values below for Mainnet in the [deployed TierProviderBase contract](https://etherscan.io/address/0x394E30d83d020469a1F8b16E89D7fD5FdB1935b0#code#F3#L1)!
 
 | Tier              | Cooldown Window | Proving Window | Bond      |
 | ----------------- | --------------- | -------------- | --------- |
@@ -24,6 +24,18 @@ You can find all the corresponding values below in the [deployed TierProviderBas
 | Guardian Minority | 240 minutes     | 240 minutes    | 225 TAIKO |
 | Guardian          | 240 minutes     | 240 minutes    | 0 TAIKO   |
 
+You can find all the corresponding values below for Hekla in the [most recent protocol release](https://github.com/taikoxyz/taiko-mono/blob/taiko-alethia-protocol-v1.11.0/packages/protocol/contracts/layer1/tiers/TierProviderBase.sol)
+
+| Tier              | Cooldown Window | Proving Window | Bond      |
+| ----------------- | --------------- | -------------- | --------- |
+| Optimistic        | 1440 minutes    | 60 minutes     | 75 TAIKO  |
+| SGX               | 240 minutes     | 60 minutes     | 150 TAIKO |
+| TDX               | 240 minutes     | 60 minutes     | 150 TAIKO |
+| ZK SP1            | 240 minutes     | 120 minutes    | 225 TAIKO |
+| ZK R0             | 240 minutes     | 120 minutes    | 225 TAIKO |
+| Guardian Minority | 240 minutes     | 120 minutes    | 300 TAIKO |
+| Guardian          | 480 minutes     | 0 minutes      | 0 TAIKO   |
+
 ## Tier configuration (Mainnet)
 
 You can view the full `MainnetTierRouter` tier configuration [here](https://etherscan.io/address/0x8a4c692F12d3a9750E744A4CE24a1d351bE52E66#code):