diff --git a/packages/docs-site/src/content/config.ts b/packages/docs-site/src/content/config.ts
index 96cdce61ff5..3b3aa138f81 100644
--- a/packages/docs-site/src/content/config.ts
+++ b/packages/docs-site/src/content/config.ts
@@ -8,9 +8,9 @@ export const collections = {
description: z
.string()
.max(160, { message: "Must be 160 characters or less." }).optional(),
- // banner: z.object({ content: z.string() }).default({
- // content: '',
- // }),
+ banner: z.object({ content: z.string() }).default({
+ content: 'All Hekla Node Runners: Protocol upgrade on Feb 1st, upgrade needed. Please ensure your nodes are using the software tags listed in the announcement! Click here for more info',
+ }),
}),
}),
}),
diff --git a/packages/docs-site/src/content/docs/guides/node-operators/deploy-a-proverset.mdx b/packages/docs-site/src/content/docs/guides/node-operators/deploy-a-proverset.mdx
index dabf6a58b97..768917022eb 100644
--- a/packages/docs-site/src/content/docs/guides/node-operators/deploy-a-proverset.mdx
+++ b/packages/docs-site/src/content/docs/guides/node-operators/deploy-a-proverset.mdx
@@ -25,7 +25,7 @@ This guide outlines how to achieve this with separate EOAs running prover and pr
1. **Clone the Taiko monorepo**
- The [Taiko monorepo](https://github.com/taikoxyz/taiko-mono) contains the scripts for deploying your `ProverSet`. Checkout the latest stable release. (Use `protocol-v1.9.0` for Hekla!)
+ The [Taiko monorepo](https://github.com/taikoxyz/taiko-mono) contains the scripts for deploying your `ProverSet`. Checkout the latest stable release. (Use `taiko-alethia-protocol-v1.11.0` for Hekla!)
@@ -56,10 +56,6 @@ This guide outlines how to achieve this with separate EOAs running prover and pr
ROLLUP_ADDRESS_MANAGER={ADDRESS} PROVER_SET_ADMIN={ADDRESS} forge script --chain-id {CHAIN_ID} --rpc-url {YOUR_RPC_URL} --private-key {PRIVATE_KEY} --broadcast script/DeployProverSet.s.sol:DeployProverSet
```
-
-
The script should print your implementation and proxy address with the log:
```
@@ -93,7 +89,7 @@ This guide outlines how to achieve this with separate EOAs running prover and pr
5. **Configure the contract as necessary**
- Manage the contract's allowance with [approveAllowance()](https://github.com/taikoxyz/taiko-mono/blob/protocol-v1.9.0/packages/protocol/contracts/layer1/provers/ProverSet.sol#L64). TaikoL1's contract allowance is by default set to `UINT256.MAX` in the init function.
+ Manage the contract's allowance with [approveAllowance()](https://github.com/taikoxyz/taiko-mono/blob/taiko-alethia-protocol-v1.11.0/packages/protocol/contracts/layer1/provers/ProverSet.sol#L68). TaikoL1's contract allowance is by default set to `UINT256.MAX` in the init function.
6. **Deposit your tokens and run your proposer + prover as usual!**
@@ -106,7 +102,7 @@ This guide outlines how to achieve this with separate EOAs running prover and pr
Ensure that you have set up the EOAs correctly to avoid problems.
@@ -164,7 +160,7 @@ If you've already deployed a ProverSet but would like to upgrade it through the
If you've managed to propose and prove some blocks, it's likely you're wondering where your tokens went after.
- It's not missing, it's just been deposited as bond in the TaikoL1 contract; you can withdraw it to the ProverSet contract with [withdrawBond()](https://github.com/taikoxyz/taiko-mono/blob/protocol-v1.9.0/packages/protocol/contracts/layer1/provers/ProverSet.sol#L136) manually.
+ It's not missing, it's just been deposited as bond in the TaikoL1 contract; you can withdraw it to the ProverSet contract with [withdrawBond()](https://github.com/taikoxyz/taiko-mono/blob/taiko-alethia-protocol-v1.11.0/packages/protocol/contracts/layer1/provers/ProverSet.sol#L151) manually.
### How do I verify my ProverSet contract?
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
index 771c8623625..c82e67b1950 100644
--- 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
@@ -45,12 +45,14 @@ By enabling proof aggregation, you will be opening yourself up to more risk as y
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.
+We highly recommend you test the function **on Hekla**, not on Mainnet.
+
+Please note that you must use the [upgraded ProverSet contract](https://github.com/taikoxyz/taiko-mono/blob/taiko-alethia-protocol-v1.11.0/packages/protocol/contracts/layer1/provers/ProverSet.sol) to use this functionality.
-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)
+Batch proving has been enabled in release 0.43.1 of [the taiko alethia client!](https://github.com/taikoxyz/taiko-mono/releases/tag/taiko-alethia-client-v0.43.1)
-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.
+Please use [simple-taiko-node release 1.9.0](https://github.com/taikoxyz/simple-taiko-node/releases/tag/v1.9.0) 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.**
@@ -82,7 +84,7 @@ The following steps can be done through the [ProverSet contract](/guides/node-op
Please verify [contract addresses](/network-reference/mainnet-addresses) are correct before moving forward. You can check the respective ENS domains on Etherscan.
-4. Set the amount to at least the minimum bond amount of 125 TAIKO.
+4. Set the amount to at least the minimum bond amount of 150 TAIKO.
You will need 150 TAIKO for each bond you sign. After entering 150, you need to set the 18 decimals that the TAIKO contract takes, you can click the plus button and then select 10^18.
diff --git a/packages/docs-site/src/content/docs/taiko-protocol/bridging.md b/packages/docs-site/src/content/docs/taiko-protocol/bridging.md
index fe5926a6d67..e1229bdd854 100644
--- a/packages/docs-site/src/content/docs/taiko-protocol/bridging.md
+++ b/packages/docs-site/src/content/docs/taiko-protocol/bridging.md
@@ -22,10 +22,10 @@ Taiko deploys two smart contracts which store the hashes of the other chain:
- TaikoL1 stores the L2 world state root on L1 (deployed on Ethereum)
- TaikoL2 stores the L1 world state root on L2 (deployed on Taiko)
-Every time an L2 block is created on Taiko, the world state root of the enclosing block on L1 is stored in the [TaikoL2](https://github.com/taikoxyz/taiko-mono/blob/protocol-v1.9.0/packages/protocol/contracts/layer2/based/TaikoL2.sol#L145) contract using the `anchor` transaction. To ensure validity, it is part of the (previously the zk circuits, now SGX and ZK) proof data submitted with each block, so no fake L1 world state root can be synchronized to L2."
+Every time an L2 block is created on Taiko, the world state root of the enclosing block on L1 is stored in the [TaikoL2](https://github.com/taikoxyz/taiko-mono/blob/taiko-alethia-protocol-v1.11.0/packages/protocol/contracts/layer2/based/TaikoL2.sol#L155) contract using the `anchor` transaction. To ensure validity, it is part of the (previously the zk circuits, now SGX and ZK) proof data submitted with each block, so no fake L1 world state root can be synchronized to L2."
The L2 world state root is stored in the TaikoL1 contract using the `syncChainData` function call in
-[`LibVerifying`](https://github.com/taikoxyz/taiko-mono/blob/protocol-v1.9.0/packages/protocol/contracts/layer1/based/LibVerifying.sol#L179).
+[`LibVerifying`](https://github.com/taikoxyz/taiko-mono/blob/taiko-alethia-protocol-v1.11.0/packages/protocol/contracts/layer1/based/LibVerifying.sol#L165).
Taiko by default synchronizes the world state roots cross-chain with the above mechanism.