Op-node

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.

• https://github.com/ethereum-optimism/optimism/tree/develop/op-node

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

Changelog

• The L1 beacon client in the op-node now better detects missing blobs and falls back to the l1.beacon-archiver endpoint, if configured

logs

• no peers ready to handle block requests for more P2P requests for L2 block histor
• Advancing bq origin
• Error: Payload execution failed
• Initializing Rollup Node

Related

• Rollup Node Specification
• op-geth
• op-proposer
• l2-geth
• p2p
• 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