[OP Stack Deployment] L2 Hash mismatch wen running op-geth after op-deployer apply

[iujiban]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I'm running into an issue while trying to bring up an L2 chain using op-deployer (v0.2.0) with configType = "standard" and an L1 chain (Sepolia, chain ID 11155111) + L2 chain ID 11155420

Set up Steps:

1. Initialize deployer state:

./bin/op-deployer init --l1-chain-id 11155111 --l2-chain-ids 11155420 --workdir .deployer

2. Modify .deployer/intent.toml with the following contents:
   https://docs.optimism.io/stack/smart-contracts

configType = "standard"
l1ChainID = 11155111
fundDevAccounts = false
useInterop = false
l1ContractsLocator = "tag://op-contracts/v2.0.0"
l2ContractsLocator = "tag://op-contracts/v1.7.0-beta.1+l2-contracts"

[superchainRoles]
  proxyAdminOwner = "0x1Eb2fFc903729a0F03966B917003800b145F56E2"
  protocolVersionsOwner = "0xfd1D2e729aE8eEe2E146c033bf4400fE75284301"
  guardian = "0x7a50f00e8D05b95F98fE38d8BeE366a7324dCf7E"

[[chains]]
  id = "0x0000000000000000000000000000000000000000000000000000000000aa37dc"
  baseFeeVaultRecipient = "0x4200000000000000000000000000000000000019"
  l1FeeVaultRecipient = "0x420000000000000000000000000000000000001A"
  sequencerFeeVaultRecipient = "0x4200000000000000000000000000000000000011"
  eip1559DenominatorCanyon = 250
  eip1559Denominator = 50
  eip1559Elasticity = 6
  [chains.roles]
    l1ProxyAdminOwner = "0x1eb2ffc903729a0f03966b917003800b145f56e2"
    l2ProxyAdminOwner = "0x2fc3ffc903729a0f03966b917003800b145f67f3"
    systemConfigOwner = "0xfd1D2e729aE8eEe2E146c033bf4400fE75284301"
    unsafeBlockSigner = "0x57CACBB0d30b01eb2462e5dC940c161aff3230D3"
    batcher = "0x8F23BB38F531600e5d8FDDaAEC41F13FaB46E98c"
    proposer = "0x49277EE36A024120Ee218127354c4a3591dc90A9"
    challenger = "0xfd1D2e729aE8eEe2E146c033bf4400fE75284301"

3. Apply deployment:

./bin/op-deployer apply --workdir .deployer \
  --l1-rpc-url $L1_RPC_URL \ -- alchemy rpc using
  --private-key myPrivateKey

4. copy genesis.json from op-deployer genesis file and run it by this command:

mkdir datadir
./build/bin/geth init --state.scheme=hash --datadir=datadir genesis.json

./build/bin/geth \
  --datadir ./datadir \
  --http \
  --http.corsdomain="*" \
  --http.vhosts="*" \
  --http.addr=0.0.0.0 \
  --http.api=web3,debug,eth,txpool,net,engine,miner \
  --ws \
  --http.port=8545 \
  --ws.addr=0.0.0.0 \
  --ws.port=8546 \
  --ws.origins="*" \
  --ws.api=debug,eth,txpool,net,engine,miner \
  --syncmode=full \
  --gcmode=archive \
  --nodiscover \
  --maxpeers=0 \
  --authrpc.vhosts="*" \
  --authrpc.addr=0.0.0.0 \
  --authrpc.port=8551 \
  --authrpc.jwtsecret=./jwt.txt \
  --rollup.disabletxpoolgossip=true \
  --networkid=$L2_CHAIN_ID \
  --op-network=op-sepolia \
  --verbosity=3 \

🛑 Problem
geth fails to start with the following error:

INFO [05-27|07:14:02.916] Starting geth on an OP network...        network=op-sepolia
INFO [05-27|07:14:02.918] Maximum peer count                       ETH=0 total=0
INFO [05-27|07:14:02.919] Smartcard socket not found, disabling    err="stat /run/pcscd/pcscd.comm: no such file or directory"
INFO [05-27|07:14:02.923] Enabling recording of key preimages since archive mode is used
WARN [05-27|07:14:02.924] Disabled transaction unindexing for archive node
WARN [05-27|07:14:02.924] Forcing hash state-scheme for archive mode
INFO [05-27|07:14:02.924] Set global gas cap                       cap=50,000,000
INFO [05-27|07:14:03.373] Initializing the KZG library             backend=gokzg
INFO [05-27|07:14:03.375] Allocated trie memory caches             clean=307.00MiB dirty=0.00B
INFO [05-27|07:14:03.376] Using pebble as the backing database
INFO [05-27|07:14:03.376] Allocated cache and file handles         database=/home/dev/op-geth/datadir/geth/chaindata cache=512.00MiB handles=524,288
INFO [05-27|07:14:03.416] Opened ancient database                  database=/home/dev/op-geth/datadir/geth/chaindata/ancient/chain readonly=false
INFO [05-27|07:14:03.428] State scheme set by user                 scheme=hash
INFO [05-27|07:14:03.475] Genesis hash                             hash=ea5397..55320a
Fatal: Failed to register the Ethereum service: database contains incompatible genesis (have ea539732ba328fcac627e0d519fa4cc8ace160ba913405eca1c242500e55320a, new 102de6ffb001480cc9b8b548fd05c34cd4f46ae4aa91759393db90ea0409887d)

The new genesis hash 102d... appears to come from the op-network=op-sepolia configuration. But the generated genesis.json via op-deployer apply has a different hash: ea53.... This results in a database mismatch when trying to start op-geth.

so I searched the 102de6ffb001480cc9b8b548fd05c34cd4f46ae4aa91759393db90ea0409887d) from the code that is coming from superchain.config L2 hash [op.toml]

Questions
Does --op-network=op-sepolia override or expect a specific genesis.json hash?

Could this mismatch be caused by an outdated or inconsistent state in the L1 RPC (Alchemy)?

Is there anything misconfigured in my intent.toml, or should I be deriving genesis.json differently for custom deployments?

Should I not be using --op-network=op-sepolia if I’m using intent.toml-based genesis?

Thanks in advance for any guidance on this.

Logs

No response

Additional Information

The version I used op-deployer is op-deployer/v0.2.0 and op-geth is latest version which is v1.101511.0

Feedback

No response

[opfocus]

https://docs.optimism.io/operators/chain-operators/tools/op-deployer#inspect-generate-genesis-files-and-chain-information refer this command to generate your genesis.json

[opfocus]

#17 (comment)
Please refer to here for the startup command of the component, but you should use the latest component version

[iujiban]

@opfocus Hi,
I already made genesis.json which you refer one.
Here is my setting steps.

1. Go to ~/op-deploy/optimism/op-deployer and do following:

./bin/op-deployer init --l1-chain-id 11155111 --l2-chain-ids 11155420 --workdir .deployer

2. Customized an intent file in a created .deployer file which is same as op-sepolia superchain config

configType = "standard"
l1ChainID = 11155111
fundDevAccounts = false
useInterop = false
l1ContractsLocator = "tag://op-contracts/v2.0.0"
l2ContractsLocator = "tag://op-contracts/v1.7.0-beta.1+l2-contracts"

[superchainRoles]
  proxyAdminOwner = "0x1Eb2fFc903729a0F03966B917003800b145F56E2"
  protocolVersionsOwner = "0xfd1D2e729aE8eEe2E146c033bf4400fE75284301"
  guardian = "0x7a50f00e8D05b95F98fE38d8BeE366a7324dCf7E"

[[chains]]
  id = "0x0000000000000000000000000000000000000000000000000000000000aa37dc"
  baseFeeVaultRecipient = "0x4200000000000000000000000000000000000019"
  l1FeeVaultRecipient = "0x420000000000000000000000000000000000001A"
  sequencerFeeVaultRecipient = "0x4200000000000000000000000000000000000011"
  eip1559DenominatorCanyon = 250
  eip1559Denominator = 50
  eip1559Elasticity = 6
  [chains.roles]
    l1ProxyAdminOwner = "0x1eb2ffc903729a0f03966b917003800b145f56e2"
    l2ProxyAdminOwner = "0x2fc3ffc903729a0f03966b917003800b145f67f3"
    systemConfigOwner = "0xfd1D2e729aE8eEe2E146c033bf4400fE75284301"
    unsafeBlockSigner = "0x57CACBB0d30b01eb2462e5dC940c161aff3230D3"
    batcher = "0x8F23BB38F531600e5d8FDDaAEC41F13FaB46E98c"
    proposer = "0x49277EE36A024120Ee218127354c4a3591dc90A9"
    challenger = "0xfd1D2e729aE8eEe2E146c033bf4400fE75284301"

3. Deploy chain to L1

./bin/op-deployer apply --workdir .deployer \
  --l1-rpc-url $L1_RPC_URL \ -- alchemy rpc using
  --private-key myPrivateKey

4. Generate L2 Genesis file and rollup file

./bin/op-deployer inspect genesis --workdir .deployer 11155420 > .deployer/genesis.json
./bin/op-deployer inspect rollup --workdir .deployer 11155420 > .deployer/rollup.json

From here, L2 Hash in the rollup.json has different from superchain config's L2 Hash which is started 102de6ffb001480cc9b8b548fd05c34cd4f46ae4aa91759393db90ea0409887d
Rollup.json:

{
  "genesis": {
    "l1": {
      "hash": "0x4617b4bb8c321fe038771d1062bb869833170079a367051ad2db272147a29951",
      "number": 8428027
    },
    "l2": {
      "hash": "0xddefa23499e637db980d35df8d74dab5deaededd1609a2f26ada951778d482b5",
      "number": 0
    },
    "l2_time": 1748474616,
    "system_config": {
      "batcherAddr": "0x8f23bb38f531600e5d8fddaaec41f13fab46e98c",
      "overhead": "0x0000000000000000000000000000000000000000000000000000000000000000",
      "scalar": "0x010000000000000000000000000000000000000000000000000c5fc500000558",
      "gasLimit": 60000000,
      "eip1559Params": "0x0000000000000000"
    }
  },
  "block_time": 2,
  "max_sequencer_drift": 600,
  "seq_window_size": 3600,
  "channel_timeout": 300,
  "l1_chain_id": 11155111,
  "l2_chain_id": 11155420,
  "regolith_time": 0,
  "canyon_time": 0,
  "delta_time": 0,
  "ecotone_time": 0,
  "fjord_time": 0,
  "granite_time": 0,
  "holocene_time": 1732633200,
  "batch_inbox_address": "0x0002b8639730e2f4dc88dfd5bbd0352e5518a758",
  "deposit_contract_address": "0x6f2d6cc549bd193787dfb81cf11e85db70bd51c3",
  "l1_system_config_address": "0x3c7cad789e01976e9f9e2f8c99cae61685eb4680",
  "protocol_versions_address": "0x79add5713b383daa0a138d3c4780c7a1804a8090",
  "chain_op_config": {
    "eip1559Elasticity": 6,
    "eip1559Denominator": 50,
    "eip1559DenominatorCanyon": 250
  }
}

Command to operate the op-geth

./build/bin/geth \
  --datadir ./datadir \
  --http \
  --http.corsdomain="*" \
  --http.vhosts="*" \
  --http.addr=0.0.0.0 \
  --http.api=web3,debug,eth,txpool,net,engine,miner \
  --ws \
  --http.port=8545 \
  --ws.addr=0.0.0.0 \
  --ws.port=8546 \
  --ws.origins="*" \
  --ws.api=debug,eth,txpool,net,engine,miner \
  --syncmode=full \
  --gcmode=archive \
  --nodiscover \
  --maxpeers=0 \
  --authrpc.vhosts="*" \
  --authrpc.addr=0.0.0.0 \
  --authrpc.port=8551 \
  --authrpc.jwtsecret=./jwt.txt \
  --rollup.disabletxpoolgossip=true \
  --networkid=$L2_CHAIN_ID \
  --op-network=op-sepolia \
  --verbosity=3 \

Command to operate the op-node

./bin/op-node \
  --l2=http://localhost:8551 \
  --l2.jwt-secret=./jwt.txt \
  --sequencer.enabled \
  --sequencer.l1-confs=5 \
  --verifier.l1-confs=4 \
  --rollup.config=./rollup.json \
  --rpc.addr=0.0.0.0 \
  --p2p.disable \
  --rpc.enable-admin \
  --p2p.sequencer.key=$GS_SEQUENCER_PRIVATE_KEY \
  --l1=$L1_RPC_URL \
  --l1.rpckind=$L1_RPC_KIND \
  --l1.beacon=$L1_BEACON_URL \
  --network=op-sepolia \
  --l2.enginekind=geth 

If I am not using the network config from op-node, it comes out NewpayloadV3 error

ERROR[05-28|23:56:51.066] Engine failed temporarily, backing off sequencer err="failed to insert execution payload: failed to execute payload: Unsupported fork: map[err:newPayloadV3 must only be called for cancun payloads]"
INFO [05-28|23:56:51.066] Scheduled sequencer action               delta=999.98522ms
INFO [05-28|23:56:51.067] Advancing bq origin                      origin=0e1e9a..d9b31e:8428036 originBehind=false
INFO [05-28|23:56:51.814] Advancing bq origin                      origin=c2c9f9..8982a8:8428037 originBehind=false
INFO [05-28|23:56:52.438] Resuming sequencing with previously async-gossip confirmed payload payload=57f872..630ca1:1
ERROR[05-28|23:56:52.440] Payload execution failed                 block_hash=57f872..630ca1 err="Unsupported fork: map[err:newPayloadV3 must only be called for cancun payloads]"
WARN [05-28|23:56:52.440] Engine temporary error                   err="failed to insert execution payload: failed to execute payload: Unsupported fork: map[err:newPayloadV3 must only be called for cancun payloads]"
ERROR[05-28|23:56:52.440] Engine failed temporarily, backing off sequencer err="failed to insert execution payload: failed to execute payload: Unsupported fork: map[err:newPayloadV3 must only be called for cancun payloads]"
INFO [05-28|23:56:52.440] Advancing bq origin                      origin=0587e1..4166c9:8428038 originBehind=false
INFO [05-28|23:56:53.181] Received first L1 head signal            l1_head=04a905..e60497:8428193
INFO [05-28|23:56:53.181] Scheduled sequencer action               delta=258.296441ms
INFO [05-28|23:56:53.181] Advancing bq origin                      origin=8a3d9b..c898cf:8428039 originBehind=false
INFO [05-28|23:56:53.874] Resuming sequencing with previously async-gossip confirmed payload payload=57f872..630ca1:1
ERROR[05-28|23:56:53.875] Payload execution failed                 block_hash=57f872..630ca1 err="Unsupported fork: map[err:newPayloadV3 must only be called for cancun payloads]"

If I used the network config from op-sepolia, the error says to dismatch the L2 block at genesis block number 0:

INFO [05-28|23:57:29.039] Not opted in to ProtocolVersions signal loading, disabling ProtocolVersions contract now.
INFO [05-28|23:57:29.050] No persisted sequencer state loaded
INFO [05-28|23:57:29.050] Rollup Config                            l2_chain_id=11,155,420 l2_network=op l1_chain_id=11,155,111 l1_network=sepolia l2_start_time=1,691,802,540 l2_block_hash=0x102de6ffb001480cc9b8b548fd05c34cd4f46ae4aa91759393db90ea0409887d l2_block_number=0 l1_block_hash=0x48f520cf4ddaf34c8336e6e490632ea3cf1e5e93b0b2bc6e917557e31845371b l1_block_number=4,071,408 regolith_time="@ genesis" canyon_time="@ 1699981200 ~ Tue Nov 14 17:00:00 UTC 2023" delta_time="@ 1703203200 ~ Fri Dec 22 00:00:00 UTC 2023" ecotone_time="@ 1708534800 ~ Wed Feb 21 17:00:00 UTC 2024" fjord_time="@ 1716998400 ~ Wed May 29 16:00:00 UTC 2024" granite_time="@ 1723478400 ~ Mon Aug 12 16:00:00 UTC 2024" holocene_time="@ 1732633200 ~ Tue Nov 26 15:00:00 UTC 2024" pectra_blob_schedule_time="@ 1742486400 ~ Thu Mar 20 16:00:00 UTC 2025" isthmus_time="@ 1744905600 ~ Thu Apr 17 16:00:00 UTC 2025" jovian_time="(not configured)" interop_time="(not configured)"
INFO [05-28|23:57:29.050] Initializing rollup node                 version=v1.13.3-rc.1-b1e7c63b-1747318459
INFO [05-28|23:57:29.828] Connected to L1 Beacon API, ready for EIP-4844 blobs retrieval. version=teku/v25.4.1/linux-x86_64/-ubuntu-openjdk64bitservervm-java-21
ERROR[05-28|23:57:29.831] Error initializing the rollup node       err="failed to init L2: failed to get L2 genesis blockhash: expected L2 genesis hash to match L2 block at genesis block number 0: 0xddefa23499e637db980d35df8d74dab5deaededd1609a2f26ada951778d482b5 <> 0x102de6ffb001480cc9b8b548fd05c34cd4f46ae4aa91759393db90ea0409887d"
CRIT [05-28|23:57:29.831] Application failed                       message="failed to setup: unable to create the rollup node: failed to init L2: failed to get L2 genesis blockhash: expected L2 genesis hash to match L2 block at genesis block number 0: 0xddefa23499e637db980d35df8d74dab5deaededd1609a2f26ada951778d482b5 <> 0x102de6ffb001480cc9b8b548fd05c34cd4f46ae4aa91759393db90ea040988

0xddefa23499e637db980d35df8d74dab5deaededd1609a2f26ada951778d482b5 this hash is created by me and 0x102de6ffb001480cc9b8b548fd05c34cd4f46ae4aa91759393db90ea040988 this hash is created by op-sepolia.

Problem Summary
My rollup config (custom genesis) produces L2 genesis hash
0xddefa23499e637db980d35df8d74dab5deaededd1609a2f26ada951778d482b5.

But official op-sepolia rollup expects genesis hash:
0x102de6ffb001480cc9b8b548fd05c34cd4f46ae4aa91759393db90ea0409887d.

When I use my own rollup config, op-node fails at NewPayloadV3 with:

Unsupported fork: newPayloadV3 must only be called for cancun payloads
When I use --network=op-sepolia flag instead, it fetches official Superchain registry config and fails with:

expected L2 genesis hash to match genesis block: 
0xddefa234... <> 0x102de6ff...

How can I handle on this problem?
Thank you to answer my question everytimes

[iujiban]

I am setting up OP Stack L2 Chain using the Superchaing config (L2 ChainID 11155420, L1 Sepolia 11155111) and encountered a newPayloadV3 misusage error related to fork timings. The issue was discussed in ethereum/go-ethereum#29190, where newPayloadV3 must only be used for Cancun payloads. I set up all the hardforks time of superchain.config and operated the system. still have error on engine
Error from op-geth:

WARN [05-29|01:18:49.769] Served engine_newPayloadV3               conn=127.0.0.1:45748 reqid=9 duration="172.28µs" err="Unsupported fork" errdata="{\"err\":\"newPayloadV3 must only be called for cancun payloads\"}"
WARN [05-29|01:18:52.229] Served engine_newPayloadV3               conn=127.0.0.1:45748 reqid=10 duration="137.32µs" err="Unsupported fork" errdata="{\"err\":\"newPayloadV3 must only be called for cancun payloads\"}"
WARN [05-29|01:18:53.463] Served engine_newPayloadV3               conn=127.0.0.1:45748 reqid=11 duration="143.41µs" err="Unsupported fork" errdata="{\"err\":\"newPayloadV3 must only be called for cancun payloads\"}"
WARN [05-29|01:18:55.053] Served engine_newPayloadV3               conn=127.0.0.1:45748 reqid=12 duration="139.2µs" err="Unsupported fork" errdata="{\"err\":\"newPayloadV3 must only be called for cancun payloads\"}"
WARN [05-29|01:18:57.614] Served engine_newPayloadV3               conn=127.0.0.1:45748 reqid=13 duration="104.18µs" err="Unsupported fork" errdata="{\"err\":\"newPayloadV3 must only be called for cancun payloads\"}"

Error from op-node:

NFO [05-29|01:18:47.757] Confirming pipeline reset
INFO [05-29|01:18:47.757] Engine reset confirmed, sequencer may continue next=true
INFO [05-29|01:18:47.889] Scheduled sequencer action               delta=1.867345504s
INFO [05-29|01:18:49.758] Started sequencing new block             parent=bb80e1..91274e:0 l1Origin=c73d8d..bdf072:8428557
INFO [05-29|01:18:49.763] Scheduled sequencer action               delta="-7.34µs"
INFO [05-29|01:18:49.768] Sequencer sealed block                   payloadID=0x03d8a4fe16b84a54 block=92248e..640211:1 parent=bb80e1..91274e:0 txs=1 time=1,748,480,978
ERROR[05-29|01:18:49.770] Payload execution failed                 block_hash=92248e..640211 err="Unsupported fork: map[err:newPayloadV3 must only be called for cancun payloads]"
WARN [05-29|01:18:49.770] Engine temporary error                   err="failed to insert execution payload: failed to execute payload: Unsupported fork: map[err:newPayloadV3 must only be called for cancun payloads]"
ERROR[05-29|01:18:49.770] Engine failed temporarily, backing off sequencer err="failed to insert execution payload: failed to execute payload: Unsupported fork: map[err:newPayloadV3 must only be called for cancun payloads]"
INFO [05-29|01:18:49.770] Scheduled sequencer action               delta=999.98949ms
INFO [05-29|01:18:49.810] Rewinding derivation-pipeline L1 traversal to handle reset
INFO [05-29|01:18:49.810] completed reset of derivation pipeline   origin=c73d8d..bdf072:8428557
INFO [05-29|01:18:49.811] Reset of L1Retrieval done                origin=c73d8d..bdf072:8428557
INFO [05-29|01:18:49.811] ChannelMux: activating Holocene stage during reset origin=c73d8d..bdf072:8428557
INFO [05-29|01:18:49.811] BatchMux: activating Holocene stage during reset origin=c73d8d..bdf072:8428557
INFO [05-29|01:18:51.013] Advancing bq origin                      origin=a713fb..4a7012:8428558 originBehind=false
INFO [05-29|01:18:52.228] Resuming sequencing with previously async-gossip confirmed payload payload=92248e..640211:1
ERROR[05-29|01:18:52.230] Payload execution failed                 block_hash=92248e..640211 err="Unsupported fork: map[err:newPayloadV3 must only be called for cancun payloads]"
WARN [05-29|01:18:52.230] Engine temporary error                   err="failed to insert execution payload: failed to execute payload: Unsupported fork: map[err:newPayloadV3 must only be called for cancun payloads]"

This is what I operating the system
Setting up rollup.json

{
  "genesis": {
    "l1": {
      "hash": "0x4617b4bb8c321fe038771d1062bb869833170079a367051ad2db272147a29951",
      "number": 8428027
    },
    "l2": {
      "hash": "0xddefa23499e637db980d35df8d74dab5deaededd1609a2f26ada951778d482b5",
      "number": 0
    },
    "l2_time": 1748474616,
    "system_config": {
      "batcherAddr": "0x8f23bb38f531600e5d8fddaaec41f13fab46e98c",
      "overhead": "0x0000000000000000000000000000000000000000000000000000000000000000",
      "scalar": "0x010000000000000000000000000000000000000000000000000c5fc500000558",
      "gasLimit": 60000000,
      "eip1559Params": "0x0000000000000000"
    }
  },
  "block_time": 2,
  "max_sequencer_drift": 600,
  "seq_window_size": 3600,
  "channel_timeout": 300,
  "l1_chain_id": 11155111,
  "l2_chain_id": 11155420,
  "regolith_time": 0,
  "canyon_time": 0,
  "delta_time": 0,
  "ecotone_time": 0,
  "fjord_time": 0,
  "granite_time": 0,
  "holocene_time": 1732633200,
  "batch_inbox_address": "0x0002b8639730e2f4dc88dfd5bbd0352e5518a758",
  "deposit_contract_address": "0x6f2d6cc549bd193787dfb81cf11e85db70bd51c3",
  "l1_system_config_address": "0x3c7cad789e01976e9f9e2f8c99cae61685eb4680",
  "protocol_versions_address": "0x79add5713b383daa0a138d3c4780c7a1804a8090",
  "chain_op_config": {
    "eip1559Elasticity": 6,
    "eip1559Denominator": 50,
    "eip1559DenominatorCanyon": 250
  }
}

Operating the op-geth:

build/bin/geth init --state.scheme=hash --override.prague=1744905600 --datadir=datadir genesis.json

./build/bin/geth \
  --datadir ./datadir \
  --http \
  --http.corsdomain="*" \
  --http.vhosts="*" \
  --http.addr=0.0.0.0 \
  --http.api=web3,debug,eth,txpool,net,engine,miner \
  --ws \
  --http.port=8545 \
  --ws.addr=0.0.0.0 \
  --ws.port=8546 \
  --ws.origins="*" \
  --ws.api=debug,eth,txpool,net,engine,miner \
  --syncmode=full \
  --gcmode=archive \
  --nodiscover \
  --maxpeers=0 \
  --authrpc.vhosts="*" \
  --authrpc.addr=0.0.0.0 \
  --authrpc.port=8551 \
  --authrpc.jwtsecret=./jwt.txt \
  --rollup.disabletxpoolgossip=true \
  --networkid=$L2_CHAIN_ID \
  --verbosity=3 
  

Operating the op-node

./bin/op-node \
  --l2=http://localhost:8551 \
  --l2.jwt-secret=./jwt.txt \
  --sequencer.enabled \
  --sequencer.l1-confs=5 \
  --verifier.l1-confs=4 \
  --rollup.config=./rollup.json \
  --rpc.addr=0.0.0.0 \
  --rpc.enable-admin \
  --p2p.disable \
  --p2p.sequencer.key=$GS_SEQUENCER_PRIVATE_KEY \
  --l1=$L1_RPC_URL \
  --l1.rpckind=$L1_RPC_KIND \
  --l1.beacon=$L1_BEACON_URL \
  --override.canyon=1699981200 \
  --override.ecotone=1708534800 \
  --override.fjord=1716998400 \
  --override.granite=1723478400 \
  --override.delta=1703203200 \

Change to set up genesis.json

{
  "config": {
    "chainId": 11155420,
    "homesteadBlock": 0,
    "eip150Block": 0,
    "eip155Block": 0,
    "eip158Block": 0,
    "byzantiumBlock": 0,
    "constantinopleBlock": 0,
    "petersburgBlock": 0,
    "istanbulBlock": 0,
    "muirGlacierBlock": 0,
    "berlinBlock": 0,
    "londonBlock": 0,
    "arrowGlacierBlock": 0,
    "grayGlacierBlock": 0,
    "mergeNetsplitBlock": 0,
    "shanghaiTime": 1699981200,
    "cancunTime": 1708534800,
    "bedrockBlock": 0,
    "regolithTime": 0,
    "canyonTime": 1699981200,
    "ecotoneTime": 1708534800,
    "fjordTime": 1716998400,
    "graniteTime": 1723478400,
    "holoceneTime": 1732633200,
    "isthmusTime": 1744905600,
    "terminalTotalDifficulty": 0,
    "depositContractAddress": "0x0000000000000000000000000000000000000000",
    "optimism": {
      "eip1559Elasticity": 6,
      "eip1559Denominator": 50,
      "eip1559DenominatorCanyon": 250
    }
  },

I have no ideas to fix this one..... Do you have any ideas of handling this problem?

[opfocus]

--op-network=op-sepolia \ your chain is not op-sepolia, why you add this flag here

  --override.canyon=1699981200 \
  --override.ecotone=1708534800 \
  --override.fjord=1716998400 \
  --override.granite=1723478400 \
  --override.delta=1703203200 \   

no need add these , you r aready have them in rollup.json #17 (comment)
Please refer to here for the startup command of the component, but you should use the latest component version

[iujiban]

Thanks for the clarification. If I actually want to operate op-sepolia (L2) connected to L1 Sepolia, and run the full stack (op-geth, op-node, op-batcher, op-proposer) — should I only use --op-network=op-sepolia without custom rollup.json or overrides?

Also, after launching all components, I want to make the system perform safe block derivation, state commitment via op-proposer, and submit to DisputeGameFactory. Then I plan to monitor this via op-dispute-mon and eventually participate in the Fault Dispute Game with op-challenger.

Is this the right configuration flow for operating op-sepolia?
Or are there extra steps I should follow when using the Superchain Registry version?

Thanks again for your help!

[opfocus]

If I actually want to operate op-sepolia We can't do this because op-sepolia is run by optimism we can only run op-sepolia replica nodes
there extra steps I should follow when using the Superchain Registry version?
There is not about version selection, it just presents the config facts of the current superchain members.
If you use configType = "standard", you can more easily merge your chain information into the Superchain Registry repo if needed in the future.