Difference between revisions of "Op-node"
Jump to navigation
Jump to search
(→Logs) |
|||
| Line 12: | Line 12: | ||
* <code>[[no peers ready to handle block requests for more P2P requests for L2 block histor]]</code> | * <code>[[no peers ready to handle block requests for more P2P requests for L2 block histor]]</code> | ||
* <code>[[Advancing bq origin]]</code> | * <code>[[Advancing bq origin]]</code> | ||
| + | * [[Error: Payload execution failed]] | ||
== Related == | == Related == | ||
Revision as of 19:03, 25 August 2024
op-node is the reference implementation of the rollup-node spec.
op-node networks dump-rollup-config --network=sepolia
--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
no peers ready to handle block requests for more P2P requests for L2 block historAdvancing bq origin- Error: Payload execution failed
Related
- Rollup Node Specification
op-gethop-proposerl2-gethp2p- Consensus Layer Configuration Options
- SingularBatch
- Running an OP Mainnet Node from Source
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:
