Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update rollup operators under chain management #1131

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update rollup operators under chain management #1131

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pages/builders/chain-operators/management/_meta.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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"
Expand Down
35 changes: 33 additions & 2 deletions pages/builders/chain-operators/management/operations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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
```
Comment on lines +58 to +70
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Add parameter descriptions and environment variable setup

The command example needs additional context:

  1. Add descriptions for critical parameters like poll-interval and rpc.port
  2. Explain the format expected for l2oo-address
  3. Document the required environment variables

Add a description table before the command:

| 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 |

| 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
Expand Down Expand Up @@ -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": {
Expand Down Expand Up @@ -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>

Expand Down
Loading