From d6e098714683512ec12a1e709379a7089ec90c40 Mon Sep 17 00:00:00 2001
From: Richard Gregory <richardgrecoson@gmail.com>
Date: Wed, 20 Nov 2024 15:33:20 +0100
Subject: [PATCH] Update rollup operators under chain management

---
 .../chain-operators/management/_meta.json     |  2 +-
 .../chain-operators/management/operations.mdx | 35 +++++++++++++++++--
 2 files changed, 34 insertions(+), 3 deletions(-)

diff --git a/pages/builders/chain-operators/management/_meta.json b/pages/builders/chain-operators/management/_meta.json
index a33e1fbfb..dcfc4355a 100644
--- a/pages/builders/chain-operators/management/_meta.json
+++ b/pages/builders/chain-operators/management/_meta.json
@@ -1,7 +1,7 @@
 {
   "blobs": "Using blobs",
   "snap-sync": "Using Snap Sync",
-  "operations": "Node operations",
+  "operations": "Rollup operations",
   "key-management": "Key management",
   "troubleshooting": "Troubleshooting",
   "best-practices": "Best practices"
diff --git a/pages/builders/chain-operators/management/operations.mdx b/pages/builders/chain-operators/management/operations.mdx
index b85102f96..ee3d364c6 100644
--- a/pages/builders/chain-operators/management/operations.mdx
+++ b/pages/builders/chain-operators/management/operations.mdx
@@ -23,6 +23,17 @@ An orderly shutdown is done in the reverse order to the order in which component
     This way the batcher knows to save any data it has cached to L1.
     Wait until you see `Batch Submitter stopped` in batcher's output before you stop the process.
 
+### Stop `op-proposer`
+
+### Stop `op-proposer`
+
+To stop the proposer, terminate the process directly. This can be done by:
+
+*   Pressing **Ctrl+C** in the terminal running the process
+*   Using system commands like `kill -TERM <pid>` to stop the process gracefully
+
+Ensure that the proposer process has terminated completely before proceeding to stop other components.
+
 ### Stop `op-node`
     This component is stateless, so you can just stop the process.
 
@@ -44,6 +55,26 @@ To restart the blockchain, use the same order of components you did when you ini
     curl -d '{"id":0,"jsonrpc":"2.0","method":"admin_startBatcher","params":[]}' \
         -H "Content-Type: application/json" http://localhost:8548 | jq   
     ```
+### Start `op-proposer`
+
+Start the proposer using the appropriate command. Here's an example:
+
+  ```sh
+  ./bin/op-proposer \
+    --poll-interval=12s \
+    --rpc.port=8560 \
+    --rollup-rpc=http://localhost:8547 \
+    --l2oo-address=0xYourL2OutputOracleAddress \
+    --private-key=$PROPOSER_PRIVATE_KEY \
+    --l1-eth-rpc=$L1_RPC_URL
+  ```
+  | Parameter     | Description                                                    |
+  | ------------- | -------------------------------------------------------------- |
+  | poll-interval | How often to check for new output proposals (recommended: 12s) |
+  | rpc.port      | Local RPC port for the proposer service                        |
+  | l2oo-address  | The L2 Output Oracle contract address (0x-prefixed hex)        |
+  | private-key   | Private key for signing proposals                              |
+  | l1-eth-rpc    | L1 network RPC endpoint URL                                    |
 </Steps>
 <Callout type="info">
 Synchronization takes time
@@ -74,7 +105,7 @@ This script will NOT work for chain operators trying to generate this data in or
 You'll need to run this tool:
 
 ```
-./bin/op-node networks dump-rollup-config --network=sepolia   
+./bin/op-node networks dump-rollup-config --network=op-sepolia   
 {
   "genesis": {
     "l1": {
@@ -115,7 +146,7 @@ You'll need to run this tool:
 ```
 ### Check the flags
 Ensure that you are using the appropriate flag. 
-The `--network=sepolia` flag allows the tool to pick up the appropriate data from the registry, and uses the OPChains mapping under the hood.
+The `--network=op-sepolia` flag allows the tool to pick up the appropriate data from the registry, and uses the OPChains mapping under the hood.
 
 </Steps>