Resultado de búsqueda
EIP-4788 introduces a "beacon block root" into the execution-layer block-header and EVM. This block root is an SSZ hash-tree-root of the consensus-layer contents of the previous consensus block. With the adoption of EIP-4399 in the Bedrock upgrade the OP-Stack already includes the PREVRANDAO of L1.
New L1 blocks may be finalized every L1 beacon epoch (approximately 6.4 minutes), and depending on these finality-signals and batch-inclusion, the derived L2 chain will become irreversible as well.
OP_NODE__L1_BEACON - Specify the beacon endpoint of Layer 1. You can use QuickNode for the beacon endpoint. For example: https://xxx-xxx-xxx.quiknode.pro/db55a3908ba7e4e5756319ffd71ec270b09a7dce; OP_NODE__RPC_TYPE - Specify the service provider for the RPC endpoint you've chosen in the previous step. The available options are: alchemy - Alchemy
Following the Ecotone upgrade node operators must set an L1 beacon value to retrieve blobs from a Beacon node.
This tutorial explains how to run an OP Mainnet node from source code for full nodes and archive nodes. Running an OP Mainnet node from source code is a flexible alternative to using pre-built Docker images.
All node operators must set an L1 beacon value in your op-node as soon as you update to the latest release. --l1.beacon value ($OP_NODE_L1_BEACON) HTTP endpoint Address of L1 Beacon-node. Either run your own L1 beacon node like Lighthouse.
14 de mar. de 2024 · You need l1 beacon api access for op-node and pass via --l1.beacon param (or OP_NODE_L1_BEACON env). Consider having full-archive blobs access. if you are on the superchain you don't have to pass any new parameter. General Tooling Next. Last updated 8 hours ago.