Difference between revisions of "OP Stack"
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 12: | Line 12: | ||
*** 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]], [[op-batcher]] | + | * <code>[[op-node]], [[op-batcher]], [[op-service]]</code> |
| Line 20: | Line 20: | ||
* [[OP Chain]] | * [[OP Chain]] | ||
* [[OP Architecture]] | * [[OP Architecture]] | ||
| + | * [[OP Contracts Manager (OPCM)]] | ||
== Related == | == Related == | ||
Latest revision as of 17:05, 30 October 2024
- https://hub.docker.com/u/ethereumoptimism (Not publishing since a year)
- May 2024 op-stack v1.7.6
- The L1 beacon client in the op-node now better detects missing blobs and falls back to the
l1.beacon-archiverendpoint, if configured
- The L1 beacon client in the op-node now better detects missing blobs and falls back to the
- May 2024 op-stack v1.7.6
Related[edit]
See also[edit]
- 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 - OP Stack,
op-, Superchain, Fault Proofs Explainer, Optimism monitorism - Optimism,
OP, OP Stack, OP Architecture,op-, Superchain, Optimism Bedrock, Proxyd, Crypto sequencer, rollup, Optimistic Rollup Protocol, Optimism Blobs, Optimism monitorism, fault-mon,eth-optimism/sdk,L2OutputOracle.sol, OptimismPortal.sol, OP Sepolia Testnet (11155420), OP Labs, Optimism Foundation, Fault Proof, Ecotone, Fjord, Rollup node, L2 Chain Derivation Specification, Fastnode.io, OP Contracts Manager (OPCM)
Advertising:
