Difference between revisions of "Op-node"
Jump to navigation
Jump to search
(→Logs) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | {{lc}}<code>op-node</code> is the reference implementation of the [[rollup-node]] spec. | + | {{lc}}<code>op-node</code> 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 | * https://github.com/ethereum-optimism/optimism/tree/develop/op-node | ||
| Line 23: | Line 23: | ||
* [[SingularBatch]] | * [[SingularBatch]] | ||
* [[Running an OP Mainnet Node from Source]] | * [[Running an OP Mainnet Node from Source]] | ||
| + | * [[OP NODE P2P PEERSTORE PATH]] | ||
== See also == | == See also == | ||
Latest revision as of 08:08, 2 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
--p2p.static
Contents
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]
no peers ready to handle block requests for more P2P requests for L2 block historAdvancing bq origin- Error: Payload execution failed
Related[edit]
- Rollup Node Specification
op-gethop-proposerl2-gethp2p- Consensus Layer Configuration Options
- SingularBatch
- Running an OP Mainnet Node from Source
- OP NODE P2P PEERSTORE PATH
See also[edit]
op-node [ networks dump-rollup-config], 9003- 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, Snap Sync, op-conductor, op-dispute-mon
Advertising:
