jleony/nanoreth
1
0
Fork 0
mirror of https://github.com/hl-archive-node/nanoreth.git synced 2025-12-06 10:59:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(docs): Remove op-node Rollup Config CLI Flag (#6813)

Browse Source
This commit is contained in:
refcell
2024-02-27 01:55:00 -07:00
committed by GitHub
parent 802819a4d7
commit 0931fe1973
1 changed files with 1 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
book/run/optimism.md
View File

@ -69,8 +69,6 @@ The `optimism` feature flag in `op-reth` adds several new CLI flags to the `reth
1. `--rollup.disable-tx-pool-gossip` - Disables gossiping of transactions in the mempool to peers. This can be ommitted for personal nodes, though providers should always opt to enable this flag. 1. `--rollup.disable-tx-pool-gossip` - Disables gossiping of transactions in the mempool to peers. This can be ommitted for personal nodes, though providers should always opt to enable this flag.
1. `--rollup.enable-genesis-walkback` - Disables setting the forkchoice status to tip on startup, making the `op-node` walk back to genesis and verify the integrity of the chain before starting to sync. This can be ommitted unless a corruption of local chainstate is suspected. 1. `--rollup.enable-genesis-walkback` - Disables setting the forkchoice status to tip on startup, making the `op-node` walk back to genesis and verify the integrity of the chain before starting to sync. This can be ommitted unless a corruption of local chainstate is suspected.
Base's `rollup.json` files, which contain various configuration fields for the rollup, can be found in their [node][base-node] repository, under the respective L1 settlement layer's directory (`mainnet`, `goerli`, & `sepolia`).
First, ensure that your L1 archival node is running and synced to tip. Then, start `op-reth` with the `--rollup.sequencer-http` flag set to the `Base Mainnet` sequencer endpoint: First, ensure that your L1 archival node is running and synced to tip. Then, start `op-reth` with the `--rollup.sequencer-http` flag set to the `Base Mainnet` sequencer endpoint:
```sh ```sh
op-reth node \ op-reth node \
@ -85,9 +83,9 @@ op-reth node \
Then, once `op-reth` has been started, start up the `op-node`: Then, once `op-reth` has been started, start up the `op-node`:
```sh ```sh
op-node \ op-node \
--network="base-mainnet" \
--l1=<your-L1-rpc> \ --l1=<your-L1-rpc> \
--l2=http://localhost:9551 \ --l2=http://localhost:9551 \
--rollup.config=/path/to/rollup.json \
--l2.jwt-secret=/path/to/jwt.hex \ --l2.jwt-secret=/path/to/jwt.hex \
--rpc.addr=0.0.0.0 \ --rpc.addr=0.0.0.0 \
--rpc.port=7000 \ --rpc.port=7000 \
@ -121,5 +119,3 @@ op-node \
[op-node]: https://github.com/ethereum-optimism/optimism/tree/develop/op-node [op-node]: https://github.com/ethereum-optimism/optimism/tree/develop/op-node
[magi]: https://github.com/a16z/magi [magi]: https://github.com/a16z/magi
[hildr]: https://github.com/optimism-java/hildr [hildr]: https://github.com/optimism-java/hildr
[base-node]: https://github.com/base-org/node/tree/main