[ZK Stack] - Error: Deployment on Sepolia trying to read from **/dry-run/...

[moneta]

Team or Project

No response

Module Affected

• System contracts (era-system-contracts)
• Smart contracts (era-contracts)
• zkEVM (era-zk_evm)
• Server (zksync-era)
• Prover (era-boojum)
• Fee withdrawer (era-fee-withdrawer)
• Block Explorer (clock-explorer)
• Portal - Wallet + Bridge (dapp-portal)
• Other (please specify below)

Rust Version

1.85.0

Operating System

• Ubuntu
• MacOS
• Windows
• Other (Please specify below)

Issue Description

I deployed a new zkChain on Sepolia testnet with zkstack ecosystem init and the deployer wallet ran out of ETH during the deployment process. So I topped it up and rerun with the --resume flag. Then it throws error:

Error: Deployment not found for chain `11155111`.

Context:
- failed to read from "/root/amplify/zksync-era/contracts/l1-contracts/broadcast/AcceptAdmin.s.sol/11155111/dry-run/83eddd19-latest.json": No such file or directory (os error 2)
│
■  Command failed to run
│  
■    Status:
│      exit status: 1
│    Stdout:
│      
│  
│    Stderr:
│      
│  
■  Command failed to run: forge script deploy-scripts/AcceptAdmin.s.sol --legacy --ffi --rpc-url=https://eth-sepolia.g.alchemy.com/v2/XXXXXX --broadcast --sig=83eddd1900000000000000000000000023ef66731ea541df66eb14f79d45cd3e0c0440ea000000000000000000000000249f36fb9720daf80922e918181de9d10da9ce2b --private-key=XXXXXXX --slow --isolate --resume
│  

I search the entire codebase and removed the /dry-run in the path but resuming the deployment still failed with the same error message.

Spent 3 hours on this... Any idea how to fix this? Thank you.

Expected Behavior

The resume deployment should work: zkstack ecosystem init

Current Behavior

It failed with error message

Error: Deployment not found for chain `11155111`.

Context:
- failed to read from "/root/amplify/zksync-era/contracts/l1-contracts/broadcast/AcceptAdmin.s.sol/11155111/dry-run/83eddd19-latest.json": No such file or directory (os error 2)
│
■  Command failed to run
│  
■    Status:
│      exit status: 1
│    Stdout:
│      
│  
│    Stderr:
│      
│  
■  Command failed to run: forge script deploy-scripts/AcceptAdmin.s.sol --legacy --ffi --rpc-url=https://eth-sepolia.g.alchemy.com/v2/XXXXXXXX --broadcast --sig=83eddd1900000000000000000000000023ef66731ea541df66eb14f79d45cd3e0c0440ea000000000000000000000000249f36fb9720daf80922e918181de9d10da9ce2b --private-key=XXXXXXX --slow --isolate --resume

Repository Link (if applicable)

No response

Additional Details

No response

Prior Research

• Yes, I searched for similar issues and did not find any matching ones.

[ly0va]

Hi @moneta, I forwarded your issue to the team, they are looking into it. Meanwhile, is restarting the init from scratch with a different chainID an option for you?

[moneta]

Looks like it works now for me. Here what I did:

diff --git a/zkstack_cli/crates/zkstack/src/commands/ecosystem/build_transactions.rs b/zkstack_cli/crates/zkstack/src/commands/ecosystem/build_transactions.rs
index 1cd76debb..6407960a6 100644
--- a/zkstack_cli/crates/zkstack/src/commands/ecosystem/build_transactions.rs
+++ b/zkstack_cli/crates/zkstack/src/commands/ecosystem/build_transactions.rs
@@ -16,7 +16,7 @@ use crate::messages::{
 };
 
 const DEPLOY_TRANSACTIONS_FILE_SRC: &str =
-    "contracts/l1-contracts/broadcast/DeployL1.s.sol/9/dry-run/run-latest.json";
+    "contracts/l1-contracts/broadcast/DeployL1.s.sol/9/run-latest.json";
 const DEPLOY_TRANSACTIONS_FILE_DST: &str = "deploy-l1-txns.json";
 
 const SCRIPT_CONFIG_FILE_SRC: &str = "contracts/l1-contracts/script-config/config-deploy-l1.toml";

Then I run zkstackup --local in the zksync-era folder to recompile it and resume deployment. However, it is weird that the first attempts failed with the same error.

A few hour later, I ran the resume again and it worked. It is absurd, but it seems like the file name from last successful run was saving to the blockchain with some timeout?

[ly0va]

Thank you for your feedback! While we look into this deeper, we're happy that your issue has resolved itself