Difference between revisions of "Op-node"
Jump to navigation
Jump to search
(→Logs) |
|||
| (11 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
[[op-node networks dump-rollup-config]] --network=sepolia | [[op-node networks dump-rollup-config]] --network=sepolia | ||
| − | + | == Example == | |
./bin/op-node \ | ./bin/op-node \ | ||
--l1=ws://localhost:8546 \ | --l1=ws://localhost:8546 \ | ||
--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 | ||
| Line 20: | Line 20: | ||
* The L1 [[beacon client]] in the [[op-node]] now better detects [[missing blobs]] and falls back to the <code>[[l1.beacon-archiver]]</code> endpoint, if configured | * The L1 [[beacon client]] in the [[op-node]] now better detects [[missing blobs]] and falls back to the <code>[[l1.beacon-archiver]]</code> endpoint, if configured | ||
| − | == | + | == [[op-node logs|logs]] == |
| − | |||
| − | |||
| − | |||
== Related == | == Related == | ||
* [[Rollup Node Specification]] | * [[Rollup Node Specification]] | ||
| − | * <code>[[op-geth]]</code> | + | * <code>[[op-geth]]</code>, <code>[[l2-geth]]</code> |
* <code>[[op-proposer]]</code> | * <code>[[op-proposer]]</code> | ||
| − | * <code>[[ | + | * <code>[[p2p]]</code> [[9003]] |
| − | |||
* [[Consensus Layer Configuration Options]] | * [[Consensus Layer Configuration Options]] | ||
* [[SingularBatch]] | * [[SingularBatch]] | ||
* [[Running an OP Mainnet Node from Source]] | * [[Running an OP Mainnet Node from Source]] | ||
| − | * [[ | + | * <code>[[OP_NODE_P2P_PEERSTORE_PATH]]</code> |
| + | * <code>[[OP_NODE_SEQUENCER_ENABLED]]</code> | ||
| + | |||
| + | * [[8545]] | ||
| + | * [[Consensus layer configuration options (op-node)]] | ||
== See also == | == See also == | ||
Latest revision as of 12:16, 25 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
Contents
Example[edit]
./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[edit]
- The L1 beacon client in the op-node now better detects missing blobs and falls back to the
l1.beacon-archiverendpoint, if configured
logs[edit]
Related[edit]
- Rollup Node Specification
op-geth,l2-gethop-proposerp2p9003- Consensus Layer Configuration Options
- SingularBatch
- Running an OP Mainnet Node from Source
OP_NODE_P2P_PEERSTORE_PATHOP_NODE_SEQUENCER_ENABLED
See also[edit]
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:
