Using op-deployer to deploy an L3

[euler-singularity]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

We are implementing op-deployer to launch an L3 chain on top of Base Sepolia. We initially followed the standard tutorial, anticipating that redirecting deployment from Ethereum Sepolia to Base Sepolia would require minimal modifications to the existing process.

Currently, the primary issue is that we cannot utilize the existing op-deployer binaries due to their strict enforcement of Ethereum chain IDs. Therefore, we have been modifying and experimenting with the source code of multiple deployer versions, primarily v0.2.0, to accommodate our custom chain requirements. These are the challenges and issues we have encountered so far:

• Source code was modified to accept other chain IDs different from 1 and 11155111.
• We attempted to deploy using the existing artifacts in the Google Drive folder using:

op-deployer apply --workdir .deployer \
  --l1-rpc-url https://sepolia.base.org  \
  --private-key my-private-key

but encountered the following error:

Application failed: error in pipeline stage apply: error populating superchain state: error generating read superchain deployment script: failed to load script ReadSuperchainDeployment from ReadSuperchainDeployment.s.sol: failed to open artifact "ReadSuperchainDeployment.s.sol/ReadSuperchainDeployment.json": open ReadSuperchainDeployment.s.sol/ReadSuperchainDeployment.json: no such file or directory

• We found that the correct hash for the file is 5228e435ea2ab0b2b4d14fb8aabd69ed22045600c52b5dfde26dfafbabcd5bf9, however, we were unable to resolve the content hash verification issue. Our approach was to implement a custom tag with the following structure, but couldn't make it work:

ContractsCustomTag: {
		ArtifactsHash: common.HexToHash("5228e435ea2ab0b2b4d14fb8aabd69ed22045600c52b5dfde26dfafbabcd5bf9"),
		ContentHash:   common.HexToHash("couldn't calculate this one correctly"),
	},

• Since the remote option didn't work, we tried to set the contracts locators in the intent.toml file to a local file, following the documentation and help in the forum, we tried:

l1ContractsLocator = "file:///path/to/artifacts/file"
l2ContractsLocator = "file:///path/to/artifacts/file"

but it only accepts locators with the tag identifier and with some of the preconfigured tags, e.g.,

l1ContractsLocator = "tag://op-contracts/v3.0.0-rc.2"

• We unsuccessfully tried multiple approaches, the reason being that it calls the checkL1Prod() method to validate the version. This uses L1ContractsLocator.tag, and it gets a null value. If changed to L1ContractsLocator.URL, it will extract the URL, but it will fail the validation.Semver(c.L1ContractsLocator.URL) validation.

• At this point, we were advised to move the question to a new topic focusing on L3 deployment rather than the tutorial.

So, our question is:

Is there a public deployer version that has been used to deploy in L3, or at least less customized for Ethereum sepolia? If not, do you have any suggestions for the type of changes we should make to op-deployer and which version is the best to use as a base?

Logs

No response

Additional Information

We had a long discussion with @opfocus and @jsvisa on another thread, there are some logs and conversations that might be useful: #813

Feedback

No response

[opfocus]

#17 (comment) This link is from an earlier share, where the deployment was done using the forge script method. More importantly, it contains discussions on some issues. For reference only. After reading through this content, we can try to explore the possibility of deployment using op-deployer.

[Chomtana]

Your artifact files has to be zipped in tar.gz format

If not works, you might have to upload artifacts as a tar.gz file on a cloud such as AWS S3 and reference the locator to that publicly available link

https://github.com/ethpandaops/optimism-package/blob/68d71d7c2ca21a1541199ab34336fb03ae11d282/README.md?plain=1#L517

    l1_artifacts_locator: https://storage.googleapis.com/oplabs-contract-artifacts/artifacts-v1-c193a1863182092bc6cb723e523e8313a0f4b6e9c9636513927f1db74c047c15.tar.gz
    l2_artifacts_locator: https://storage.googleapis.com/oplabs-contract-artifacts/artifacts-v1-c193a1863182092bc6cb723e523e8313a0f4b6e9c9636513927f1db74c047c15.tar.gz

[euler-singularity]

Yes. The artifacts are compressed on a tar. The issue is with the op-deployer not accepting the file: tag. I will try to host it somewhere. Thanks!

[euler-singularity]

I successfully deployed the contracts. I am currently experiencing issues generating the Genesis file. However, since the contracts have been deployed, I will close this issue and open a new one for the problem with the Genesis file.

The solution included:

• Modify the standard.go file in the deployer to set the new chainIds. In my case, I changed Ethereum's with the base's chain IDs.
• Set these configurations in the intent.toml

configType = "custom"
l1ChainID = 84532
fundDevAccounts = false
useInterop = false
l1ContractsLocator = "tag://op-contracts/v3.0.0-rc.2"
l2ContractsLocator = "tag://op-contracts/v3.0.0-rc.2"