[OP Stack Deployment] op-node-v1.7.2 Generate contract artifacts failed #329
-
Did you check the documentation?
Did you check for duplicate questions?
Issue DescriptionI'm stucked at step "Generate contract artifacts Logs[⠑] Compiling... [4767977] Deploy::setUp() [9079256848778947757] Deploy::run() == Logs == Additional InformationSo if I want to build my own spepolia L2 with OPStack in a stable way, what are the steps should I follow? What are the core codes that I must read to deploy and maintain it? FeedbackNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 20 replies
-
|
You need to set IMPL_SALT in .envrc to some random hex. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reply! I tried to run == Logs == Deploying DisputeGameFactory implementation Setting up 1 EVM.2024-04-01T04:47:05.640346Z ERROR forge_script::transaction: Failed to decode constructor arguments contract=Some("ResolvedDelegateProxy") signature=constructor(address,string) is_create2=false constructor_args=ffffff161480610509575033155b1561028e5761028b8161060c565b60006105417fb53127684a568b3173ae13b9f8a6016e243e63b6e8ee1178d6a717850b5d61035490565b73ffffffffffffffffffffffffffffffffffffffff163373ffffffffffffffffffffffffffffffffffffffff161480610578575033155b156104a557507fb53127684a568b3173ae13b9f8a6016e243e63b6e8ee1178d6a717850b5d61035490565b7f360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc81815560405173ffffffffffffffffffffffffffffffffffffffff8316907fbc7cd75a20ee27fd9adebab32041f755214dbc6bffa90cc0225b39da2e5c2d3b90600090a25050565b60006106367fb53127684a568b3173ae13b9f8a6016e243e63b6e8ee1178d6a717850b5d61035490565b7fb53127684a568b3173ae13b9f8a6016e243e63b6e8ee1178d6a717850b5d61038381556040805173ffffffffffffffffffffffffffffffffffffffff80851682528616602082015292935090917f7e644d79422f17c01e4894b5f4f588d331ebfa28653d42ae832dc59e38c9798f910160405180910390a1505050565b803573ffffffffffffffffffffffffffffffffffffffff811681146106d857600080fd5b919050565b6000602082840312156106ef57600080fd5b610412826106b4565b60008060006040848603121561070d57600080fd5b610716846106b4565b9250602084013567ffffffffffffffff8082111561073357600080fd5b818601915086601f83011261074757600080fd5b81358181111561075657600080fd5b87602082850101111561076857600080fd5b6020830194508093505050509250925092565b600060208083528351808285015260005b818110156107a85785810183015185820160400152820161078c565b818111156107ba576000604083870101525b50601f017fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffe016929092016040019392505050565b818382376000910190815291905056fea164736f6c634300080f000ab53127684a568b3173ae13b9f8a6016e243e63b6e8ee1178d6a717850b5d610300000000000000000000000090193c961a926261b756d1e5bb255e67ff9498a1 Context:
Any suggestions? |
Beta Was this translation helpful? Give feedback.
-
|
Were you able to fix it, I am having the same problem ? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Hey, I solved this problem by following their suggestions. OP has made changes in the codebase to generate the genesis and rollup. You may want to follow the discussion below to make it work. Two highlights: 1. uses https://github.com/ethereum-optimism/optimism/tree/op-contracts/v1.3.0 to deploy v1 contract 2.write your l1-deployment json file like https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/extra/addresses/sepolia/base.json |
Beta Was this translation helpful? Give feedback.
-
|
In the op-node v1.7.2, it is only used for the software codes. https://github.com/ethereum-optimism/optimism/tree/op-contracts/v1.3.0 use this repo for the contract deployment. and then use op-node v1.7.2 for creating the rollup. |
Beta Was this translation helpful? Give feedback.
-
|
I will also have errors from batcher and proposer: |
Beta Was this translation helpful? Give feedback.
-
|
Have you used to deploy chain and reset the datadir? You may try deploying a new chain using a new empty wallet and see if the issue is still there. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reply. I thought it was due to syncing. The 1st L1 block was few days before the node started to run. After the sync is up-to-date, there's no more error from batcher and proposer. However, I still see a few unauthorised submitter from time to time. It was the first time I deploy op-node with this wallet. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @roastedbill I hope you found your answer to the issues in this thread, please mark it as answered if you are able to run the chain now. Happy to help. |
Beta Was this translation helpful? Give feedback.
-
|
An unauthorized submitter is normal if multiple different chains are using the same batch inbox address. This often occurs in case you have used the default chain ID. You don't need to worry about this warning. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you guys for being so helpful! Now I'm going to learn more about OPStack codes. Do you guys want a new tutorial for this release branch? I can write up one according to my experience if needed. |
Beta Was this translation helpful? Give feedback.
-
|
hey @roastedbill thanks for the interest, but I guess there are docs available for the production release information. It would be great if you could release a tutorial for upgrading the op-stack chain to ecotone fork. because there are very less details available for it. I think there is a need for proper steps and commands for the ecotone chain upgrade. |
Beta Was this translation helpful? Give feedback.
-
|
It would be nice to update L2 deployment docs and tutorial code as soon as possible. many people want to deploy L2 chains but they are confused by the differences between deployment and execution version. |
Beta Was this translation helpful? Give feedback.
Hey @roastedbill I hope you found your answer to the issues in this thread, please mark it as answered if you are able to run the chain now. Happy to help.