[ZK Stack] - zkstack ecosystem initialization fails during setup: crash report generated

[abooo96]

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 am developing under Windows with WSL 2.

When i run zkstack ecosystem init with my following setup, this step fails to complete.

Here is the full context:

$ zkstack ecosystem create

┌   ZK Stack CLI
│
◇  What do you want to name the ecosystem?
│  elastic-chain
│
◇  Select the origin of zksync-era repository
│  Clone for me (recommended)
│
◇  Select the L1 network
│  Sepolia
│
◇  What do you want to name the chain?
│  sepolia
│
◇  What's the chain id?
│  300
│
◇  Select how do you want to create the wallet
│  Empty
│
◇  Select the prover mode
│  NoProofs
│
◇  Select the commit data generator mode
│  Validium
│
◇  Select the base token to use
│  Eth
│
◇  Enable EVM emulator?
│  No
│
◇  Do you want to start containers after creating the ecosystem?
│  No
│
◇  Selected config ────────────────────────────────────────────────╮
│                                                                  │
│    ∙ chain_args:                                                 │
│      ∙ base_token:                                               │
│        ∙ address: "0x0000000000000000000000000000000000000001"   │
│        ∙ denominator: 1                                          │
│        ∙ nominator: 1                                            │
│      ∙ chain_id: 300                                             │
│      ∙ chain_name: "sepolia"                                     │
│      ∙ evm_emulator: false                                       │
│      ∙ l1_batch_commit_data_generator_mode: "Validium"           │
│      ∙ legacy_bridge: false                                      │
│      ∙ link_to_code: ""                                          │
│      ∙ prover_version: "NoProofs"                                │
│      ∙ set_as_default: true                                      │
│      ∙ update_submodules: null                                   │
│      ∙ wallet_creation: "Empty"                                  │
│      ∙ wallet_path: null                                         │
│    ∙ ecosystem_name: "elastic_chain"                             │
│    ∙ l1_network: "Sepolia"                                       │
│    ∙ link_to_code: ""                                            │
│    ∙ start_containers: false                                     │
│    ∙ update_submodules: null                                     │
│    ∙ wallet_creation: "Empty"                                    │
│    ∙ wallet_path: null                                           │
│                                                                  │
├──────────────────────────────────────────────────────────────────╯
│
●  Creating ecosystem
│
◇  Cloning zksync-era repository... done in 189.06921104 secs
│
◇  Creating initial configurations... done in 0.018428801 secs
│
◐  Creating default chain...                                                                              ◇  Cloning zksync-era repository... done in 170.758069425 secs
│
◇  Creating default chain... done in 170.777995421 secs
│
└  Ecosystem elastic_chain created successfully (All subsequent commands should be executed from ecosystem folder `cd elastic_chain`)
$ cd elastic_chain/
$ zkstack ecosystem init

┌   ZK Stack CLI
│
◇  Do you want to deploy some test ERC20s?
│  No
│
◇  Do you want to deploy ecosystem contracts? (Not needed if you already have an existing one)
│  No
│
◇  What is the RPC URL of the L1 network?
│  https://zksync-sepolia.infura.io/v3/xyz
│
◇  Do you want to setup observability? (Grafana)
│  No
│
●  Initializing ecosystem
│
◇  Installing and building dependencies... done in 1273.118810234 secs
│
◇  Provide the path to the ecosystem contracts or keep it empty and you will use ZKsync ecosystem config. For using this config, you need to have governance wallet
│
│
●  Initializing chain sepolia
│
◇  Do you want to deploy Paymaster contract?
│  No
│
◇  Select the Validium type
│  Avail
│
◇  Avail client type
│  FullClient
│
◇  Avail API node URL
│  https://turing-rpc.avail.so/rpc
│
◇  Avail app id
│  xyz
│
◇  Avail finality state
│  InBlock
│
◇  Attestation bridge API URL
│  https://turing-bridge-api.avail.so/
│
◇  Avail API timeout in milliseconds
│  3000
│
◇  Seed phrase
│  xyz
│
◇  Please provide server database url for chain sepolia
│  postgres://postgres:notsecurepassword@localhost:5432
│
◇  Please provide server database name for chain sepolia
│  zksync_server_sepolia
│
◐  Registering chain...  

Then following error appears in the console:

Well, this is embarrassing.

zkstack had a problem and crashed. To help us diagnose the problem you can send us a crash report.

We have generated a report file at "/tmp/report-031e2762-c16a-43b0-9450-d4a2eefc0fbc.toml". Submit an issue or email with the subject of "zkstack Crash Report" and include the report as an attachment.

- Homepage: https://zksync.io/
- Authors: The Matter Labs Team <hello@matterlabs.dev>

We take privacy seriously, and do not perform any automated error collection. In order to improve the software, we rely on people to submit reports.

Thank you kindly!

Expected Behavior

I expect it to correctly initialize the ecosystem because it was never deployed before.

Current Behavior

The initialization step doesn't finish properly.

This is the error message:

Well, this is embarrassing.

zkstack had a problem and crashed. To help us diagnose the problem you can send us a crash report.

We have generated a report file at "/tmp/report-5430b489-3e38-4c15-b448-0eb70ff862a6.toml". Submit an issue or email with the subject of "zkstack Crash Report" and include the report as an attachment.

- Homepage: https://zksync.io/
- Authors: The Matter Labs Team <hello@matterlabs.dev>

We take privacy seriously, and do not perform any automated error collection. In order to improve the software, we rely on people to submit reports.

Thank you kindly!

Now, when i open this crash-report it shows following:

name = "zkstack"
operating_system = "Ubuntu 24.4.0 (noble) [64-bit]"
crate_version = "0.1.2"
explanation = """
Panic occurred in file 'crates/config/src/forge_interface/register_chain/input.rs' at line 81
"""
cause = "force_deployment_data"
method = "Panic"
backtrace = """
   0:     0x55cf38e97ce4 - <unresolved>
   1:     0x55cf38e943c4 - <unresolved>
   2:     0x55cf38da5568 - <unresolved>
   3:     0x55cf39d0b2f3 - <unresolved>
   4:     0x55cf39d0afca - <unresolved>
   5:     0x55cf39d09619 - <unresolved>
   6:     0x55cf39d0ac5d - <unresolved>
   7:     0x55cf389cbc20 - <unresolved>
   8:     0x55cf389cbbfb - <unresolved>
   9:     0x55cf3957895e - <unresolved>
  10:     0x55cf389ff4bf - <unresolved>
  11:     0x55cf389fd26a - <unresolved>
  12:     0x55cf38a2ef8b - <unresolved>
  13:     0x55cf38a3fdd0 - <unresolved>
  14:     0x55cf389ebd83 - <unresolved>
  15:     0x55cf38bfecea - <unresolved>
  16:     0x55cf38d89589 - <unresolved>
  17:     0x55cf38e8739c - <unresolved>
  18:     0x55cf38d704d3 - <unresolved>
  19:     0x55cf38e3aa7d - <unresolved>
  20:     0x55cf39cf9c47 - <unresolved>
  21:     0x55cf38e87455 - <unresolved>
  22:     0x7f4d1460f1ca - <unresolved>
  23:     0x7f4d1460f28b - __libc_start_main
  24:     0x55cf389cc3a5 - <unresolved>
  25:                0x0 - <unresolved>
"""

This shows that the rust code panicked but i don't know why or what I could be doing wrong while setting up my Validium chain on Sepolia.
I have ETH funds ($42 should be enough i guess) on ZKSync Sepolia Testnet.

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.

[abooo96]

I have opened an issue instead of a discussion here:

#944