[OP Stack Deployment] Need help with deploy custom L2 network on custom L1

[chiphamskymavis]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I got stuck when deploying L2 on my L1

stage=deploy-superchain

Steps to Reproduce

I followed this document:
https://docs.optimism.io/operators/chain-operators/tutorials/create-l2-rollup#step-2-generate-your-l2-genesis-file-and-rollup-file

At step: Deploy the L1 contracts, I try to run op-deployer apply and got stuck in there

Expected behavior

Can deploy my contracts to L1

Environment Information:

op-deployer: v0.2.0-rc.1

Configurations

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

[superchainDeployment]

[superchainRoles]
  proxyAdminOwner = "0x53A1EEa21df7927EB0fECDDa8C2E73A1608F326c"
  protocolVersionsOwner = "0x53A1EEa21df7927EB0fECDDa8C2E73A1608F326c"
  guardian = "0x53A1EEa21df7927EB0fECDDa8C2E73A1608F326c"

[[chains]]
  id = "0x0000000000000000000000000000000000000000000000000000000001346935"
  baseFeeVaultRecipient = "0x53A1EEa21df7927EB0fECDDa8C2E73A1608F326c"
  l1FeeVaultRecipient = "0x53A1EEa21df7927EB0fECDDa8C2E73A1608F326c"
  sequencerFeeVaultRecipient = "0x53A1EEa21df7927EB0fECDDa8C2E73A1608F326c"
  eip1559DenominatorCanyon = 250
  eip1559Denominator = 50
  eip1559Elasticity = 6
  [chains.roles]
    l1ProxyAdminOwner = "0x53A1EEa21df7927EB0fECDDa8C2E73A1608F326c"
    l2ProxyAdminOwner = "0x53A1EEa21df7927EB0fECDDa8C2E73A1608F326c"
    systemConfigOwner = "0x53A1EEa21df7927EB0fECDDa8C2E73A1608F326c"
    unsafeBlockSigner = "0x21e73120AB1daf03a034cEe4c16Cf788fCf1677c"
    batcher = "0x21F8e9C123887c07933C3b9CeA9FE8347c7E4194"
    proposer = "0x9558B8B2831Db3606857cF480B76344df629885b"
    challenger = "0x53A1EEa21df7927EB0fECDDa8C2E73A1608F326c"

Logs

./op-deployer apply --workdir .deployer --l1-rpc-url https://saigon-testnet.roninchain.com/rpc --private-key $GS_ADMIN_PRIVATE_KEY
INFO [03-12|10:23:29.936] Initialized path database readonly=true cache=0.00B buffer=0.00B history=0
INFO [03-12|10:23:29.936] initializing pipeline stage=init strategy=live
INFO [03-12|10:23:30.022] deploying superchain stage=deploy-superchain

Additional Information

No response

Feedback

No response

[opfocus]

tag://op-contracts/v2.0.0-rc.1" why did you chose this realease,
Do you need to use the experimental features?

[opfocus]

https://github.com/ethereum-optimism/optimism/releases/tag/op-deployer%2Fv0.2.0-rc.1 are you follow this?

[dzung-rise]

Hi, any update on this issue? I've used the same contract's tag and op-deployer version, and I got the tx execution reverted errors at stage=deploy-implementations

INFO [03-24|00:54:29.901] Initialized path database                readonly=true cache=0.00B buffer=0.00B history=0
INFO [03-24|00:54:29.901] initializing pipeline                    stage=init strategy=live
INFO [03-24|00:54:30.150] superchain deployment not needed         stage=deploy-superchain
INFO [03-24|00:54:30.151] deploying implementations                stage=deploy-implementations
WARN [03-24|00:54:43.494] Failed to create a transaction, will retry service=transactor err="failed to call: execution reverted, reason: <nil>"
WARN [03-24|00:54:45.794] Failed to create a transaction, will retry service=transactor err="failed to call: execution reverted, reason: <nil>"

[opfocus]

op-deployer currently only supports deployment on sepola and mainnet.
The team has plans to add support for other L1 chains

[psx180]

The release notes you linked say "You can now bootstrap implementations on chains other than Ethereum mainnet and Sepolia". Is this not the case?

Also, it seems if we want to deploy on a different EVM L1, we'd need a beacon RPC since batches are now stored as blobs? Is there any way around this, like using calldata instead of blobs?

[opfocus]

Versions of op-deployer above v0.2.0 have fixed an initialization logic issue and will now prioritize deploying the new OPCM, which should resolve problems encountered when deploying on other chains. Additionally, please refer to the documentation for instructions on using op-deployer: https://docs.optimism.io/operators/chain-operators/tools/op-deployer.

[opfocus]

https://docs.optimism.io/operators/chain-operators/management/blobs#switch-back-to-using-calldata switch to call data