[OP Stack Deployment] Deploy chain with op-contracts/v1.8.0 op-deployer/v0.0.13

[alowe5579]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I am trying to deploy a test OP Stack chain using the tutorials/chain branch, all steps have been completed, but an error occurs when starting op-node: failed to init L1: failed to validate the L1 config: failed to get L1 genesis blockhash: failed to fetch header by num 8680115: failed to verify block hash: computed 0x7e47ed15fc7a9bdeb46fd3ccaa0cd672f86ddc947423a8b44924f657f3adb54f but RPC said 0x7ce15fe84d9d4f25213a4dc84073962e170103a7f2ff668ef1d75801febed2e4"
Here's the relevant part of my intent.toml file:

deploymentStrategy = "live"
configType = "standard-overrides"
l1ChainID = 11155111
fundDevAccounts = true
useInterop = false
l1ContractsLocator = "tag://op-contracts/v1.8.0-rc.4"
l2ContractsLocator = "tag://op-contracts/v1.7.0-beta.1+l2-contracts"

[superchainRoles]
  proxyAdminOwner = "0x1eb2ffc903729a0f03966b917003800b145f56e2"
  protocolVersionsOwner = "0x79add5713b383daa0a138d3c4780c7a1804a8090"
  guardian = "0x7a50f00e8d05b95f98fe38d8bee366a7324dcf7e"

[[chains]]
  id = "0x000000000000000000000000000000000000000000000000000000000000a455"
  baseFeeVaultRecipient = "0x805DAB4baB540b673DfEd34d7ffd10A4b2165fC1"
  l1FeeVaultRecipient = "0x805DAB4baB540b673DfEd34d7ffd10A4b2165fC1"
  sequencerFeeVaultRecipient = "0x805DAB4baB540b673DfEd34d7ffd10A4b2165fC1"
  eip1559DenominatorCanyon = 250
  eip1559Denominator = 50
  eip1559Elasticity = 6
  [chains.roles]
    l1ProxyAdminOwner = "0x805DAB4baB540b673DfEd34d7ffd10A4b2165fC1"
    l2ProxyAdminOwner = "0x805DAB4baB540b673DfEd34d7ffd10A4b2165fC1"
    systemConfigOwner = "0x805DAB4baB540b673DfEd34d7ffd10A4b2165fC1"
    unsafeBlockSigner = "0x757151ca138d4544B9A029AD8fac41237F7887aD"
    batcher = "0x98C55b69B8D244770c3e39afdb3b2f86F2c86c82"
    proposer = "0x1De239A0cb2c0169f2bC3Ee2dcEb47D19a8154F6"
    challenger = "0x805DAB4baB540b673DfEd34d7ffd10A4b2165fC1"

my rollup.json file:

{
  "genesis": {
    "l1": {
      "hash": "0x7ce15fe84d9d4f25213a4dc84073962e170103a7f2ff668ef1d75801febed2e4",
      "number": 8680115
    },
    "l2": {
      "hash": "0x1778bac441f60b3f437fd6c728941b18a046421b6f51025bb1e753f3e1262820",
      "number": 0
    },
    "l2_time": 1751507916,
    "system_config": {
      "batcherAddr": "0x98c55b69b8d244770c3e39afdb3b2f86f2c86c82",
      "overhead": "0x0000000000000000000000000000000000000000000000000000000000000834",
      "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": 42069,
  "regolith_time": 0,
  "canyon_time": 0,
  "delta_time": 0,
  "fjord_time": 0,
  "granite_time": 0,
  "holocene_time": 0,
  "batch_inbox_address": "0x00e9bfcadbfb1f294e9a66bc0573878525f5015c",
  "deposit_contract_address": "0x118d065a28c9a5c45e82f27c10878043a4aaf4c6",
  "l1_system_config_address": "0x7057c04c85e062631350df5ef007482d69adf796",
  "protocol_versions_address": "0x79add5713b383daa0a138d3c4780c7a1804a8090"
}

Logs

INFO [07-03|10:34:49.200] Not opted in to ProtocolVersions signal loading, disabling ProtocolVersions contract now.
INFO [07-03|10:34:49.201] No persisted sequencer state loaded
INFO [07-03|10:34:49.201] Rollup Config l2_chain_id=42069 l2_network="unknown L2" l1_chain_id=11,155,111 l1_network=sepolia l2_start_time=1,751,507,916 l2_block_hash=0x1778bac441f60b3f437fd6c728941b18a046421b6f51025bb1e753f3e1262820 l2_block_number=0 l1_block_hash=0x7ce15fe84d9d4f25213a4dc84073962e170103a7f2ff668ef1d75801febed2e4 l1_block_number=8,680,115 regolith_time="@ genesis" canyon_time="@ genesis" delta_time="@ genesis" ecotone_time="(not configured)" fjord_time="@ genesis" interop_time="(not configured)"
INFO [07-03|10:34:49.201] Initializing rollup node version=v0.0.0-a06cae81-1705510057
ERROR[07-03|10:34:51.003] Error initializing the rollup node err="failed to init L1: failed to validate the L1 config: failed to get L1 genesis blockhash: failed to fetch header by num 8680115: failed to verify block hash: computed 0x7e47ed15fc7a9bdeb46fd3ccaa0cd672f86ddc947423a8b44924f657f3adb54f but RPC said 0x7ce15fe84d9d4f25213a4dc84073962e170103a7f2ff668ef1d75801febed2e4"
CRIT [07-03|10:34:51.003] Application failed message="failed to setup: unable to create the rollup node: failed to init L1: failed to validate the L1 config: failed to get L1 genesis blockhash: failed to fetch header by num 8680115: failed to verify block hash: computed 0x7e47ed15fc7a9bdeb46fd3ccaa0cd672f86ddc947423a8b44924f657f3adb54f but RPC said 0x7ce15fe84d9d4f25213a4dc84073962e170103a7f2ff668ef1d75801febed2e4"

Questions

1. Can the tutorials/chain branch still be used to deploy a local test chain?
2. If using the tutorials/chain branch, which component versions need to be upgraded to ensure successful deployment?
3. Can other branch versions be used to deploy a local test chain?
4. Which branch version should be used for the pre-production test chain and the production chain?

Feedback

Clear deployment documentation is required. The current documentation at https://docs.optimism.io/operators/chain-operators/tutorials/create-l2-rollup still uses the tutorials/chain branch as an example, and the versions of the various components used are very confusing. We hope you can take some time to update the documentation so that developers can spend less time dealing with this confusing documentation.

[opfocus]

CRIT [07-03|10:34:51.003] Application failed message="failed to setup: unable to create the rollup node: failed to init L1: failed to validate the L1 config: failed to get L1 genesis blockhash: failed to fetch header by num 8680115: failed to verify block hash: computed 0x7e47ed15fc7a9bdeb46fd3ccaa0cd672f86ddc947423a8b44924f657f3adb54f but RPC said 0x7ce15fe84d9d4f25213a4dc84073962e170103a7f2ff668ef1d75801febed2e4"
I'm very sorry, I don't have time to examine this issue in detail right now. I'll provide a brief answer based on my experience. We can discuss it more thoroughly when I return.
Please try modifying the rollup.json by replacing the relevant hash with the value computed via RPC, as indicated in the logs—that is, replace the original hash with 0x7ce15fe84d9d4f25213a4dc84073962e170103a7f2ff668ef1d75801febed2e4.

[alowe5579]

Currently, the L1 hash in rollup.json is “0x7ce15fe84d9d4f25213a4dc84073962e170103a7f2ff668ef1d75801febed2e4”. This is the hash that should be generated normally, but when starting op-geth, an error still occurs indicating that the hash does not match.

[opfocus]

Can the tutorials/chain branch still be used to deploy a local test chain?
No. Since we use op-deployer, we should switch to the branch tag corresponding to the release version.
If using the tutorials/chain branch, which component versions need to be upgraded to ensure successful deployment?
In addition to op-deployer(you can choose the appropriate version). For other components such as op-geth, you should always choose the latest release version.
Can other branch versions be used to deploy a local test chain? Sure
Which branch version should be used for the pre-production test chain and the production chain?
This depends on the op-contracts version used in op-deployer. For specific situations you should know whether the contract has been audited, or more simply, which contracts are used in the mainnet
You can learn about the mainnet upgrade contract through docs: https://docs.optimism.io/notices/upgrade-16

Since the Ethereum mainnet has undergone a hard fork, it may cause problems if you use an earlier op-node version.
My suggestion is to use a suitable version of op-deployer (there are many versions available, it is recommended to choose version 0.2.0 or above)
...
deploymentStrategy = "live"
configType = "standard-overrides" // modify "coustom"
l1ChainID = 11155111
fundDevAccounts = true
useInterop = false
l1ContractsLocator = "tag://op-contracts/v1.8.0-rc.4" // use default value
l2ContractsLocator = "tag://op-contracts/v1.7.0-beta.1+l2-contracts" // use defaut value

[superchainRoles] // delete
proxyAdminOwner = "0x1eb2ffc903729a0f03966b917003800b145f56e2" // delete
protocolVersionsOwner = "0x79add5713b383daa0a138d3c4780c7a1804a8090" // delete
guardian = "0x7a50f00e8d05b95f98fe38d8bee366a7324dcf7e" // delete
...

You can refer to the following examples for limited reference #17 (comment)

[alowe5579]

1. op-geth has always used the optimism branch and not the version branch in the tag. Is that okay?
2. op-deployer/v0.0.13 corresponds to tag://op-contracts/v1.8.0-rc.4, which can be used to deploy the v1.8.0-rc.4 contract normally. If it is recommended to use op-deployer version 0.2.0 or above, is it best to choose op-deployer/v0.3.3 corresponding to tag://op-contracts/v3.0.0?
3. If I choose op-deployer/v0.3.3, which release version should I choose from the branch tag to deploy the local test chain?What versions should be selected for op-node, op-batcher, and op-proposer? Is op-challenger required, and if so, what version should be selected?
4. The op-node version in the tutorials/chain branch is definitely an early one. Could this be the reason for the hash mismatch when starting the op-node?

[opfocus]

op-geth has always used the optimism branch and not the version branch in the tag. Is that okay?
Yes, the optimism branch is the latest stable for op-geth

op-deployer/v0.0.13 corresponds to tag://op-contracts/v1.8.0-rc.4, which can be used to deploy the v1.8.0-rc.4 contract normally.
Version 0.2.0 or above is recommended because it fixes a logic problem in the deployment script (not every chain wants to join the super chain, we can also deploy our own super chain)
If I choose op-deployer/v0.3.3, which release version should I choose from the branch tag to deploy the local test chain?
The key is the supported op-contracts version. For example, some versions support alt-da, and some versions support interop. Some versions are currently in use on the mainnet. If you go to the production environment, please initiate a special consultation
So, you can use any supported contract version
The op-node version in the tutorials/chain branch is definitely an early one. Could this be the reason for the hash mismatch when starting the op-node?
Anyway the branch is no longer available because an upgrade occurred https://docs.optimism.io/notices/pectra-changes
When building the release versions of op-node, op-batcher, and op-proposer corresponding to the branch tag, pnpm is no longer used. How can these components be built and used normally?
Please see the example I mentioned above

[opfocus]

For running components（op-geth,op-node...）, always choose the latest released version, and if you encounter problems running it, please let us know
The op-challenger is necessary, but it will make a lot of requests to the L1-rpc, and I have not found any known free rpc that can satisfy this. If you are only testing a certain withdrawal, you can do it manually. Related content is under discussion #767 (reply in thread)

[alowe5579]

What is the difference between the version with rc and the version without rc? Should I use the version with rc?

[opfocus]

I will consult with others, but the OP team is currently on a team holiday, so it may take a few days to get a response.
If your issue has been temporarily resolved, please close this discussion. When you encounter a new issue, feel free to open a new one.

[alowe5579]

cd ~/optimism/op-proposer
export OP_PROPOSER_WAIT_NODE_SYNC=true
export OP_PROPOSER_GAME_FACTORY_ADDRESS=$(cat ~/op-deployer/l1-contracts.json | jq -r .opChainDeployment.disputeGameFactoryProxyAddress)
export OP_PROPOSER_PROPOSAL_INTERVAL=4m
export GS_PROPOSER_PRIVATE_KEY=0x
export L1_RPC_URL=https://eth-sepolia.g.alchemy.com/v2/xxx
export OP_PROPOSER_GAME_TYPE=1
./bin/op-proposer
--poll-interval=12s
--rpc.port=8560
--rollup-rpc=http://localhost:9545
--private-key=$GS_PROPOSER_PRIVATE_KEY
--l1-eth-rpc=$L1_RPC_URL

I've reached the final step, but I can't start op-proposer. Some export parameters like OP_PROPOSER_WAIT_NODE_SYNC are not used in the command, so why are they written here? What is the correct startup command?Thanks!

[opfocus]

OP_PROPOSER_WAIT_NODE_SYNC and so on are my environment variables under ubuntu. If you look at op-proposer --help you will see the corresponding flags and explanations

If there are any error messages in the log, please provide