[ZK Stack] - system-contracts are not compiled during init command

[thecodingshrimp]

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

Operating System

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

Issue Description

The following chain of commands don't work right out of the box.

1. zkstack ecosystem create --l1-network localhost --prover-mode no-proofs --wallet-creation localhost --l1-batch-commit-data-generator-mode validium --evm-emulator false --start-containers true --update-submodules true (options: clone zksync-era repo, base token = ETH)
2. zkstack ecosystem init --dev (options: when choosing the validium type i chose NoDa

Expected Behavior

zkstack ecosystem should be initialized with default settings.

Current Behavior

zkstack ecosystem init command fails.
system-contracts are not compiled during the init command execution. When trying to access artefacts, the command fails.

2025-02-04T10:10:01.288675Z  INFO NamedFuture{name=node_storage_initializer}: zksync_node_storage_init: Performing genesis initialization
thread 'tokio-runtime-worker' panicked at lib/contracts/src/lib.rs:379:13:
Can't find bytecode for 'proved_batch' yul contract at "./contracts/system-contracts/bootloader/build/artifacts"
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2025-02-04T10:10:01.323077Z ERROR zksync_node_framework::service: Task oneshot_runner failed: Oneshot task node_storage_initializer panicked: Can't find bytecode for 'proved_batch' yul contract at "./contracts/system-contracts/bootloader/build/artifacts"
2025-02-04T10:10:01.323164Z  INFO zksync_node_framework::service: One of the task has exited, shutting down the node
2025-02-04T10:10:01.323219Z  INFO zksync_node_framework::service: Exiting the service
Error: One or more tasks failed: ["Task oneshot_runner failed: Oneshot task node_storage_initializer panicked: Can't find bytecode for 'proved_batch' yul contract at \"./contracts/system-contracts/bootloader/build/artifacts\""]
│
■  Command failed to run
│
■    Status:
│      exit status: 1
│    Stdout:
│
│
│    Stderr:
│
│
■  Unable to perform genesis on the database
│
▲    0: Failed to start server
│    1: Command failed to run: cargo run --manifest-path ./core/Cargo.toml --release --bin zksync_server -- --genesis-path /dev/zkstack_test/chains/firstzkstackchain/configs/genesis.yaml --wallets-path /dev/zkstack_test/chains/firstzkstackchain/configs/wallets.yaml --config-path /dev/zkstack_test/chains/firstzkstackchain/configs/general.yaml --secrets-path /dev/zkstack_test/chains/firstzkstackchain/configs/secrets.yaml --contracts-config-path /dev/zkstack_test/chains/firstzkstackchain/configs/contracts.yaml --genesis
│
│    2: Command failed to run: cargo run --manifest-path ./core/Cargo.toml --release --bin zksync_server -- --genesis-path /dev/zkstack_test/chains/firstzkstackchain/configs/genesis.yaml --wallets-path /dev/zkstack_test/chains/firstzkstackchain/configs/wallets.yaml --config-path /dev/zkstack_test/chains/firstzkstackchain/configs/general.yaml --secrets-path /dev/zkstack_test/chains/firstzkstackchain/configs/secrets.yaml --contracts-config-path /dev/zkstack_test/chains/firstzkstackchain/configs/contracts.yaml --genesis
│
└  Failed to run command

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.

[bxpana]

Thanks for letting us know. Quick question, what version of foundry-zksync are you using? In the mean time I'll test this out and see if I can replicate.

[thecodingshrimp]

Thanks for getting back this quickly!

I assume that I get the version from e.g. the command forge?

$ forge --version
forge 0.0.4 (60a8f352 2025-01-31T10:37:41.570621000Z)

[thecodingshrimp]

When revisiting the Getting started with ZK Stack I noticed that there is a note that says to try to install the latest standard version of zksync-foundry when having issues with any of the zkstack commands. I upgraded it to 0.0.7 but still fails at the same point.

[bxpana]

Just a heads up I'm still looking into this and trying to figure out what's causing the issue.

[MexicanAce]

@thecodingshrimp I've followed the repro steps and unfortunately haven't been able to replicate the same issue (the Ecosystem initialized and genesis completed successfully). I wonder if your zkstack CLI tool might be out of date, can you run zkstackup --local and try again?

Alternatively, you can also try the following for a more "clean" environment before trying again:

• foundryup-zksync
• zkstackup --local
• zkstack dev clean all

[MexicanAce]

@thecodingshrimp I'm going to mark my last response as the answer for now (in case others come across this Discussion). Hopefully that will update your local tools to the latest version and it resolves your issue. If it does not fix the problem, please unmark my response as the answer, and we'll continue investigating.

[thecodingshrimp]

thanks for coming back to me!

I will try to install zkstack again and also the other commands that you suggested. Will only update if it didn't work.

Thanks again!