-
Team or ProjectGlitchD Labs ZK chainMy own chain EnvironmentTestnet L2 block numberNo response zkSolc VersionI use this locked version cargo install --git https://github.com/matter-labs/zksync-era/ --locked zkstack --force --rev 3e9fc0a5f6abffdae994e4f22ab21eac95c7ac08 zksync-ethers VersionI use this locked version cargo install --git https://github.com/matter-labs/zksync-era/ --locked zkstack --force --rev 3e9fc0a5f6abffdae994e4f22ab21eac95c7ac08 Minimal Reproducible Code or Repo LinkIt's hard to reproduce the problem. Sometimes deployment is working fine, and sometimes it is not. Does this work on other EVMs? (If yes, please list at least 1 of them)not applicable Description of What Your Contract DoesIt's a script to automate zkstack ecosystem deployment. Additional DetailsDuring the deployment ecosystem init phase, For successful deployment, we need 68 deployer transactions, 25 governor transactions, and 6 chain governor transactions. Sometimes it's just a couple of deployer transactions (sometimes 11, sometimes 50, etc.) and no governor or chain governor transactions.
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
│ Transactions saved to:
Successful transactions on Holesky: Deployer address: 0x2a579e8387d55d4e362e43119849c406f64c8c74 [25 of 68] Governor address: 0x924bf64a7523ab37ee589159fb211091b4760a8a [8 of 25 transactions] Chain Governor address: 0x25328aa7ea195fcad1985619f5b1a059bd61f2e2 [0 of 6 transactions] |
Beta Was this translation helpful? Give feedback.
-
Hello @mikiw! The variable number of The "nonce too low" error may stem from the fact that you might have re-initiated the
To fix, do either of:
Hope this helps, feel free to unmark this discussion as answered if you have further questions |
Beta Was this translation helpful? Give feedback.
-
Hi @ly0va, Sometimes the errors are different, for example:
|
Beta Was this translation helpful? Give feedback.
Hello @mikiw! The variable number of
deployer
transactions is explained by the fact that the deployment is performed via CREATE2, which makes it easy to check if a certain contract has already been deployed by thedeployer
, and if so, does not redeploy it, and thus does not create separate transaction on chain.The "nonce too low" error may stem from the fact that you might have re-initiated the
zkstack ecosystem init
process before waiting for all the transactions from the previous invocation to be settled on chain. This would have resulted in a race condition, where: