feat(docs-site): update docs for based preconfs, node running, removal of proverset (#19928)

Author: RogerLamTd

packages/docs-site/astro.config.ts

@@ -84,7 +84,7 @@ export default defineConfig({
                   link: "/taiko-alethia-protocol/protocol-design/inception-layers/",
                 },
                 {
-                  label: "Pacaya fork Taiko Alethia",
+                  label: "Pacaya Fork Taiko Alethia",
                   link: "/taiko-alethia-protocol/protocol-design/pacaya-fork-taiko-alethia/",
                 },
                 {
@@ -227,10 +227,6 @@ export default defineConfig({
                   label: "Enable a prover",
                   link: "/guides/node-operators/enable-a-prover/",
                 },
-                {
-                  label: "Deploy a ProverSet",
-                  link: "guides/node-operators/deploy-a-proverset/",
-                },
                 {
                   label: "Node troubleshooting",
                   link: "/guides/node-operators/node-troubleshooting/",

packages/docs-site/src/content/docs/guides/node-operators/deploy-a-proverset.mdx

@@ -24,13 +24,11 @@ These are the bare minimum required settings along with a functional Taiko node
 
 3. Set the `L1_PROVER_PRIVATE_KEY` to an L1 account's private key which will send the Prove Block transactions.
 
-4. You may optionally [deploy a `ProverSet` contract](/guides/node-operators/deploy-a-proverset) to run your prover. If you are working with a third party prover, you will have to follow the guide with them to negotiate allowance and deposit of TAIKO/TTKOh. A ProverSet is recommended for a longer term stable setup to avoid nonce issues. For testing purposes, you may not feel the need to deploy a ProverSet.
+4. Finally set `ENABLE_PROVER` to `true` in simple-taiko-node `.env`.
 
-5. Finally set `ENABLE_PROVER` to `true` in simple-taiko-node `.env`.
+5. Set `COMPOSE_PROFILES=prover` or add prover to the list.
 
-6. Set `COMPOSE_PROFILES=prover` or add prover to the list.
-
-7. You can then run your prover with `docker compose up -d`! Please use `docker compose -f docker-compose-hekla.yml up -d` if you are running on Taiko Hekla.
+6. You can then run your prover with `docker compose up -d`! Please use `docker compose -f docker-compose-hekla.yml up -d` if you are running on Taiko Hekla.
 
 </Steps>
 
@@ -47,8 +45,6 @@ The recommended value for SGX_BATCH_SIZE is 10+ as you will see the most gas sav
 
 We highly recommend you test the function **on Taiko Hekla**, not on Taiko Alethia.
 
-Please note that you must use the [upgraded ProverSet contract](https://github.com/taikoxyz/taiko-mono/blob/taiko-alethia-protocol-v2.3.0/packages/protocol/contracts/layer1/provers/ProverSet.sol) to use this functionality.
-
 Please also note that you should NOT enable revert protection without a PBS service that has revert protection support, as it will interfere with your batch proving on Taiko Hekla.
 </Aside>
 
@@ -68,10 +64,6 @@ To prevent this, we have introduced another flag `FORCE_BATCH_PROVING_INTERVAL`.
 
 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>
-
 ### Approve TaikoInbox as TAIKO spender (Taiko Alethia)
 
 <Steps>
@@ -92,7 +84,7 @@ The following steps can be done through the [ProverSet contract](/guides/node-op
 
    You will need at least 125 TAIKO for the `livenessBond`. After entering 125, you need to set the 18 decimals that the TAIKO contract takes, you can click the plus button and then select 10^18.
 
-   If you have bonded TAIKO in the TaikoInbox contract, it will be used first before more is taken from your ProverSet.
+   If you have bonded TAIKO in the TaikoInbox contract, it will be used first before more is taken from your allowance.
 
    For an explanation on bonds, please refer to the terminology section [here](/resources/terminology).
 
@@ -118,7 +110,7 @@ You will need TTKOh deposited on the TaikoInbox contract to secure the bond for
 
    You will need at least 125 TTKOh for the `livenessBond`. After entering 125, you need to set the 18 decimals that the TAIKO contract takes, you can click the plus button and then select 10^18.
 
-   If you have bonded TTKOh in the TaikoInbox contract, it will be used first before more is taken from your ProverSet.
+   If you have bonded TTKOh in the TaikoInbox contract, it will be used first before more is taken from your allowance.
 
    For an explanation of the difference between these bonds, please refer to the terminology section [here](/resources/terminology).
 

packages/docs-site/src/content/docs/guides/node-operators/enable-a-proposer.mdx

@@ -126,6 +126,12 @@ If you aren't, you can configure the ports and addresses so that the services ca
 
     This command assumes you've run the `taiko-geth` command as is, if you've changed ports please change them accordingly.
 
+    <Aside type="tip">
+    If you wish to enable a node without joining the preconfirmations p2p network, simply **remove all `p2p` and `preconfirmation` flags with the exception of `--p2p.sync` and `--p2p.checkPointSyncUrl`.**
+
+    Please note that your node's chainhead will not be up-to-date with the preconfed blocks if you do not join the p2p network.
+    </Aside>
+
     ```bash
         ./bin/taiko-client driver \
             --l1.ws ${L1_WS} \

packages/docs-site/src/content/docs/guides/node-operators/enable-a-prover.mdx

@@ -126,6 +126,12 @@ If you aren't, you can configure the ports and addresses so that the services ca
 
     This command assumes you've run the `taiko-geth` command as is, if you've changed ports please change them accordingly.
 
+    <Aside type="tip">
+    If you wish to enable a node without joining the preconfirmations p2p network, simply **remove all `p2p` and `preconfirmation` flags with the exception of `--p2p.sync` and `--p2p.checkPointSyncUrl`.**
+
+    Please note that your node's chainhead will not be up-to-date with the preconfed blocks if you do not join the p2p network.
+    </Aside>
+
     ```bash
         ./bin/taiko-client driver \
             --l1.ws ${L1_ENDPOINT_WS} \