[ZK Stack] - Ecosystem Initialization Failed

[bitorotony]

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.80.0

Operating System

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

Issue Description

https://docs.zksync.io/zk-stack/running-a-zk-chain/locally#setup-ecosystem
I'm trying to create a new chain locally within the Elastic Chain Ecosystem.
When I attempt to initialize the ecosystem by following step 3 (using the zk_inception ecosystem init command), I encounter an error.
The error message is as follows:

■  Command failed to run: forge script deploy-scripts/DeployL1.s.sol --legacy --ffi --rpc-url=http://127.0.0.1:8545 --broadcast --slow --private-key=7726827caac94a7f9e1b160f7ea819f172f7b6f9d2a97f992c38edeab82d4110
│
│
▲    0: Command failed to run: forge script deploy-scripts/DeployL1.s.sol --legacy --ffi --rpc-url=http://127.0.0.1:8545 --broadcast --slow --private-key=7726827caac94a7f9e1b160f7ea819f172f7b6f9d2a97f992c38edeab82d4110
│
└  Failed to run command

Please let me know how I can resolve this issue easily.

Expected Behavior

Ecosystem Initialization Success

Current Behavior

Contract Deployments Failed when initializing the ecosystem

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.

[gleenai[bot]]

It seems like you are encountering an issue with the forge script command during the initialization of your ZKsync ecosystem. The error message indicates a failure in running the command with specific parameters.

Here are a few steps you can take to troubleshoot and potentially resolve this issue:

1. Check RPC Server: Ensure that your local RPC server at http://127.0.0.1:8545 is running and accessible. This error might occur if the RPC server is not running or not responding.

2. Verify Script and Parameters: Double-check the deploy-scripts/DeployL1.s.sol script for any errors or issues. Also, ensure that the --private-key provided is correct and corresponds to a valid account with sufficient permissions and balance for deployment.

3. Legacy and FFI Flags: The --legacy and --ffi flags in your command suggest specific configurations. Verify whether these flags are necessary for your deployment and if they are correctly supported by your current setup.

4. Update Forge: If you are using an outdated version of Forge, consider updating it. Sometimes, compatibility issues or bugs in older versions can cause such errors.

5. Consult Documentation: Review the ZKsync documentation on setting up a local chain to ensure all prerequisites and steps are correctly followed.

If these steps do not resolve the issue, you might want to provide more details about the script and the context in which it is run, or consider reaching out for more specific support through the ZKsync community or support channels.

Your feedback helps us serve you better. If this fully addresses your question, please give it a thumbs up. If it doesn't, please give it a thumbs down. This will inform the community and team so we can improve our support.

[sarahschwartz]

Hi @bitorotony , can you try reinstalling the latest version of foundry? (the regular version of foundry, not zksync-foundry)