Difference between revisions of "Op-node"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
--l1.beacon=http://localhost:4000 \ | --l1.beacon=http://localhost:4000 \ | ||
--l2=ws://localhost:9001 \ | --l2=ws://localhost:9001 \ | ||
| − | --rollup.config=./path-to-network-config/rollup.json \ | + | --rollup.config=./path-to-network-config/[[rollup.json]] \ |
--rpc.addr=127.0.0.1 \ | --rpc.addr=127.0.0.1 \ | ||
--rpc.port=7000 | --rpc.port=7000 | ||
Revision as of 10:58, 16 October 2024
op-node is the reference implementation of the rollup-node spec. It can be thought of like the consensus layer client of an OP Stack chain.
op-node networks dump-rollup-config --network=sepolia
./bin/op-node \ --l1=ws://localhost:8546 \ --l1.beacon=http://localhost:4000 \ --l2=ws://localhost:9001 \ --rollup.config=./path-to-network-config/rollup.json \ --rpc.addr=127.0.0.1 \ --rpc.port=7000
--p2p.static
Contents
Changelog
- The L1 beacon client in the op-node now better detects missing blobs and falls back to the
l1.beacon-archiverendpoint, if configured
logs
Related
- Rollup Node Specification
op-geth,l2-gethop-proposerp2p- Consensus Layer Configuration Options
- SingularBatch
- Running an OP Mainnet Node from Source
OP_NODE_P2P_PEERSTORE_PATH
See also
op-node [ networks dump-rollup-config ], 9003, rollup.json, op-node logs- L2: Rollup, execution layer, Optimistic Rollups (ORs), Optimistic Rollup Protocol, ZK rollup,
op-node, Rollup node, Replica, Rollup Node Specification, Fuel.network - OP Stack:
op-, op-geth, op-node, op-proposer, op-batcher, op-contracts, op-challenger, op-heartbeat, op-ufm, op-service, op-deployer, Snap Sync, op-conductor, op-dispute-mon
Advertising:
