[Application Development] Deploying L1 contract by Using op-deployer and deploy failed #829
-
Did you check the documentation?
Documentation Feedback (Optional)No response What type of issue are you experiencing?
Issue DescriptionWhen i following this document step by step deploying my own op-stack chain. i put this code "op-deployer apply --workdir .deployer --l1-rpc-url xxxxxx --private-key my_own_private_key" into my client.latter i get these message Steps to Reproducejust following the document and run "op-deployer apply --workdir .deployer --l1-rpc-url xxxxxxxxxx --private-key xxxxxxxxx" Are you using a specific library or SDK?
Are you using the latest version of the library/SDK?
Environment DetailsNo response Troubleshooting AttemptsNo response What type of support do you need?
Additional InformationNo response FeedbackNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
|
please provide your intent.toml and op-deployer version here |
Beta Was this translation helpful? Give feedback.
-
|
We have not received reports of op-deployer being unavailable for the time being. So please try again as suggested. |
Beta Was this translation helpful? Give feedback.
You can switch the Optimism repo to the
op-deployer/v0.2.0tag and then compileop-deployer.If you want to deploy your own Superchain, change
configType = "standard-overrides"toconfigType = "custom".If you do not intend to modify the contract code, then do not use
"file:///root/optimism/optimism/packages/contracts-bedrock/forge-artifacts"(keep the default value).After deployment, you can refer to the command for starting the components in this discussion:
#17 (comment)
However, note that you should always use the latest versions of the components (
op-geth,op-node,proposer, etc.), not thedevelopbranch.