[ZK Stack] - zkstack ecosystem initialization fails during setup

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

Again, 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. The error message in the console as well as in the report file does not help me much to detect the root issue to be honest.

I have 0.235 ETH on my L1 (Sepolia) and 0.0183 ETH on my L2 (ZKSync Sepolia Testnet). I guess that should be enough..

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.

[cytadela8]

Hi, the issue comes from this answer:

◇  Do you want to deploy ecosystem contracts? (Not needed if you already have an existing one)
│  No

Looking at the source file causing the issue I see it indicates missing ecosytem contract configuration. You should answer Yes as you are not using an existing ecosystem. This will result in deployment of the ecosystem contracts and creation of the config file with addresses. (You need to deploy your own ecosystem as you cannot reuse existing Sepolia one, also it is not configured by default)

Also:

◇  Do you want to start containers after creating the ecosystem?
│  No

You need to answer Yes here as you need the Postgres DB started. You can also start now using zkstack up command.

Overall, I would recommend deploying your first chain on the local node instead of Sepolia to test the process.

[cytadela8]

As for the privacy concern, please note that the same data will be published on DA in Validium mode as Ethereum in Rollup mode.

[abooo96]

I exactly followed what you did. Containers are running as expected. I don't see anything different.

up21736@W504S09Z:/mnt/c/Users/up21736/Desktop/DEA$ 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
│  Localhost
│
◇  What do you want to name the chain?
│  validium
│
◇  What's the chain id?
│  271
│
◇  Select how do you want to create the wallet
│  Localhost
│
◇  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?
│  Yes
│
◇  Selected config ────────────────────────────────────────────────╮
│                                                                  │
│    ∙ chain_args:                                                 │
│      ∙ base_token:                                               │
│        ∙ address: "0x0000000000000000000000000000000000000001"   │
│        ∙ denominator: 1                                          │
│        ∙ nominator: 1                                            │
│      ∙ chain_id: 271                                             │
│      ∙ chain_name: "validium"                                    │
│      ∙ 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: "Localhost"                              │
│      ∙ wallet_path: null                                         │
│    ∙ ecosystem_name: "elastic_chain"                             │
│    ∙ l1_network: "Localhost"                                     │
│    ∙ link_to_code: ""                                            │
│    ∙ start_containers: true                                      │
│    ∙ update_submodules: null                                     │
│    ∙ wallet_creation: "Localhost"                                │
│    ∙ wallet_path: null                                           │
│                                                                  │
├──────────────────────────────────────────────────────────────────╯
│
●  Creating ecosystem
│
◇  Cloning zksync-era repository... done in 208.685310678 secs
│
◇  Creating initial configurations... done in 0.04471165 secs
│
◐  Creating default chain...                                                                                                                                                                                                          ◇  Cloning zksync-era repository... done in 218.312305626 secs
│
◇  Creating default chain... done in 218.348295362 secs
│
◇  Starting containers... done in 1.439891345 secs
│
└  Ecosystem elastic_chain created successfully (All subsequent commands should be executed from ecosystem folder `cd elastic_chain`)
up21736@W504S09Z:/mnt/c/Users/up21736/Desktop/DEA$ cd elastic_chain
up21736@W504S09Z:/mnt/c/Users/up21736/Desktop/DEA/elastic_chain$ docker ps
CONTAINER ID   IMAGE                             COMMAND                  CREATED          STATUS         PORTS                                                                NAMES
10e6f7ab13f2   postgres:14                       "docker-entrypoint.s…"   10 seconds ago   Up 9 seconds   127.0.0.1:5432->5432/tcp                                             elastic_chain-postgres-1
95f03fa1f6c8   ghcr.io/paradigmxyz/reth:v1.0.6   "/usr/local/bin/reth…"   10 seconds ago   Up 9 seconds   8546/tcp, 9001/tcp, 127.0.0.1:8545->8545/tcp, 30303/tcp, 30303/udp   elastic_chain-reth-1
up21736@W504S09Z:/mnt/c/Users/up21736/Desktop/DEA/elastic_chain$ docker logs elastic_chain-reth-1
2025-03-05T10:54:15.426994Z  INFO Initialized tracing, debug log directory: /root/.cache/reth/logs/9
2025-03-05T10:54:15.441133Z  INFO Starting reth version="1.0.6 (c228fe15)"
2025-03-05T10:54:15.442133Z  INFO Opening database path="/rethdata/db"
2025-03-05T10:54:15.472280Z  INFO Configuration loaded path="/rethdata/reth.toml"
2025-03-05T10:54:15.473839Z  INFO Verifying storage consistency.
2025-03-05T10:54:15.540147Z  INFO Database opened
2025-03-05T10:54:15.541326Z  INFO
Pre-merge hard forks (block based):
- Homestead                        @0
- Dao                              @0
- Tangerine                        @0
- SpuriousDragon                   @0
- Byzantium                        @0
- Constantinople                   @0
- Petersburg                       @0
- Istanbul                         @0
- MuirGlacier                      @0
- Berlin                           @0
- London                           @0
Merge hard forks:
- Paris                            @0 (network is known to be merged)
Post-merge hard forks (timestamp based):
- Shanghai                         @0
- Cancun                           @0
2025-03-05T10:54:15.543696Z  INFO Transaction pool initialized
2025-03-05T10:54:15.544263Z  INFO Loading saved peers file=/rethdata/known-peers.json
2025-03-05T10:54:15.547159Z  INFO StaticFileProducer initialized
2025-03-05T10:54:15.547266Z  INFO Starting Reth in dev mode
2025-03-05T10:54:15.547346Z  INFO Allocated Genesis Account: 00. 0x0000000000000000000000000000000000000000 (0.000000000000000001 ETH)
2025-03-05T10:54:15.547529Z  INFO Allocated Genesis Account: 01. 0x0D43eB5B8a47bA8900d84AA36656c92024e9772e (100000000000000000000.000000000000000000 ETH)
2025-03-05T10:54:15.547589Z  INFO Allocated Genesis Account: 02. 0x36615Cf349d7F6344891B1e7CA7C72883F5dc049 (100000000000000000000.000000000000000000 ETH)
2025-03-05T10:54:15.547601Z  INFO Allocated Genesis Account: 03. 0x4F9133D1d3F50011A6859807C837bdCB31Aaab13 (100000000000000000000.000000000000000000 ETH)
2025-03-05T10:54:15.547609Z  INFO Allocated Genesis Account: 04. 0x52312AD6f01657413b2eaE9287f6B9ADaD93D5FE (100000000000000000000.000000000000000000 ETH)
2025-03-05T10:54:15.547617Z  INFO Allocated Genesis Account: 05. 0x5711E991397FCa8F5651c9Bb6FA06b57e4a4DCC0 (100000000000000000000.000000000000000000 ETH)
2025-03-05T10:54:15.547624Z  INFO Allocated Genesis Account: 06. 0x78192aF4cE300352a7D44b17BC2B3A3DF545E200 (100000000000000000000.000000000000000000 ETH)
2025-03-05T10:54:15.547632Z  INFO Allocated Genesis Account: 07. 0x8002cD98Cfb563492A6fB3E7C8243b7B9Ad4cc92 (100000000000000000000.000000000000000000 ETH)
2025-03-05T10:54:15.547640Z  INFO Allocated Genesis Account: 08. 0x8A91DC2D28b689474298D91899f0c1baF62cB85b (100000000000000000000.000000000000000000 ETH)
2025-03-05T10:54:15.547738Z  INFO Allocated Genesis Account: 09. 0xA13c10C0D5bd6f79041B9835c63f91de35A15883 (100000000000000000000.000000000000000000 ETH)
2025-03-05T10:54:15.547827Z  INFO Allocated Genesis Account: 10. 0xa61464658AfeAf65CccaaFD3a512b69A83B77618 (100000000000000000000.000000000000000000 ETH)
2025-03-05T10:54:15.547885Z  INFO Allocated Genesis Account: 11. 0xbd29A1B981925B94eEc5c4F1125AF02a2Ec4d1cA (100000000000000000000.000000000000000000 ETH)
2025-03-05T10:54:15.547898Z  INFO Allocated Genesis Account: 12. 0xde03a0B5963f75f1C8485B355fF6D30f3093BDE7 (100000000000000000000.000000000000000000 ETH)
2025-03-05T10:54:15.547907Z  INFO Allocated Genesis Account: 13. 0xe706e60ab5Dc512C36A4646D719b889F398cbBcB (100000000000000000000.000000000000000000 ETH)
2025-03-05T10:54:15.547916Z  INFO Allocated Genesis Account: 14. 0xE90E12261CCb0F3F7976Ae611A29e84a6A85f424 (100000000000000000000.000000000000000000 ETH)
2025-03-05T10:54:15.547924Z  INFO Allocated Genesis Account: 15. 0xedB6F5B4aab3dD95C7806Af42881FF12BE7e9daa (100000000000000000000.000000000000000000 ETH)
2025-03-05T10:54:15.547958Z  INFO configuring dev mining mode mode=FixedBlockTime
2025-03-05T10:54:15.548908Z  INFO Pruner initialized prune_config=PruneConfig { block_interval: 5, segments: PruneModes { sender_recovery: None, transaction_lookup: None, receipts: None, account_history: None, storage_history: None, receipts_log_filter: ReceiptsLogPruneConfig({}) } }
2025-03-05T10:54:15.549109Z  INFO Consensus engine initialized
2025-03-05T10:54:15.549219Z  INFO Engine API handler initialized
2025-03-05T10:54:15.573474Z  INFO RPC auth server started url=127.0.0.1:8551
2025-03-05T10:54:15.574315Z  INFO RPC IPC server started path=/tmp/reth.ipc
2025-03-05T10:54:15.574364Z  INFO RPC HTTP server started url=0.0.0.0:8545
2025-03-05T10:54:15.575135Z  INFO Starting consensus engine
2025-03-05T10:54:15.851985Z  INFO Live sync in progress, downloading blocks remaining_blocks=1 target_block_hash=0x7c0575470aec0afc8c2199c5308d6b41229a2c3f479b1068a88e58f181d84c5e
2025-03-05T10:54:15.852034Z  INFO Received forkchoice updated message when syncing head_block_hash=0x7c0575470aec0afc8c2199c5308d6b41229a2c3f479b1068a88e58f181d84c5e safe_block_hash=0x7c0575470aec0afc8c2199c5308d6b41229a2c3f479b1068a88e58f181d84c5e finalized_block_hash=0x7c0575470aec0afc8c2199c5308d6b41229a2c3f479b1068a88e58f181d84c5e
2025-03-05T10:54:15.858702Z  INFO Canonical chain committed number=1010134 hash=0x7c0575470aec0afc8c2199c5308d6b41229a2c3f479b1068a88e58f181d84c5e elapsed=6.506435ms
2025-03-05T10:54:15.860764Z  INFO Block is already canonical, ignoring. block_hash=0x7c0575470aec0afc8c2199c5308d6b41229a2c3f479b1068a88e58f181d84c5e
2025-03-05T10:54:15.862545Z  INFO Pruner started tip_block_number=1010134
2025-03-05T10:54:15.862727Z  INFO Pruner finished tip_block_number=1010134 elapsed=126.969µs stats=[(Headers, 3, Finished)]
2025-03-05T10:54:15.863465Z  INFO Static File Producer started targets=StaticFileTargets { headers: Some(1010134..=1010134), receipts: Some(1010134..=1010134), transactions: Some(1010134..=1010134) }
2025-03-05T10:54:15.888685Z  INFO Static File Producer finished targets=StaticFileTargets { headers: Some(1010134..=1010134), receipts: Some(1010134..=1010134), transactions: Some(1010134..=1010134) } elapsed=25.102384ms
2025-03-05T10:54:16.151600Z  INFO Live sync in progress, downloading blocks remaining_blocks=1 target_block_hash=0x19e126f105c3c50f4f1728e86b9a350d576bc604168664b1ede2dd2ca352f318
2025-03-05T10:54:16.151638Z  INFO Received forkchoice updated message when syncing head_block_hash=0x19e126f105c3c50f4f1728e86b9a350d576bc604168664b1ede2dd2ca352f318 safe_block_hash=0x19e126f105c3c50f4f1728e86b9a350d576bc604168664b1ede2dd2ca352f318 finalized_block_hash=0x19e126f105c3c50f4f1728e86b9a350d576bc604168664b1ede2dd2ca352f318
2025-03-05T10:54:16.157813Z  INFO Canonical chain committed number=1010135 hash=0x19e126f105c3c50f4f1728e86b9a350d576bc604168664b1ede2dd2ca352f318 elapsed=4.636099ms
2025-03-05T10:54:16.160235Z  INFO Block is already canonical, ignoring. block_hash=0x19e126f105c3c50f4f1728e86b9a350d576bc604168664b1ede2dd2ca352f318
2025-03-05T10:54:16.160386Z  INFO Static File Producer started targets=StaticFileTargets { headers: Some(1010135..=1010135), receipts: Some(1010135..=1010135), transactions: Some(1010135..=1010135) }
2025-03-05T10:54:16.186462Z  INFO Static File Producer finished targets=StaticFileTargets { headers: Some(1010135..=1010135), receipts: Some(1010135..=1010135), transactions: Some(1010135..=1010135) } elapsed=25.937048ms
2025-03-05T10:54:16.451150Z  INFO Live sync in progress, downloading blocks remaining_blocks=1 target_block_hash=0x0c51e4fac2e83dfe879e372f85ae85bb0ca51a7a880c1bed3c909918cef859ec
2025-03-05T10:54:16.451182Z  INFO Received forkchoice updated message when syncing head_block_hash=0x0c51e4fac2e83dfe879e372f85ae85bb0ca51a7a880c1bed3c909918cef859ec safe_block_hash=0x0c51e4fac2e83dfe879e372f85ae85bb0ca51a7a880c1bed3c909918cef859ec finalized_block_hash=0x0c51e4fac2e83dfe879e372f85ae85bb0ca51a7a880c1bed3c909918cef859ec

Here is my ZkStack.yaml

name: elastic_chain
l1_network: Localhost
link_to_code: /mnt/c/Users/up21736/Desktop/DEA/elastic_chain/zksync-era
bellman_cuda_dir: null
chains: /mnt/c/Users/up21736/Desktop/DEA/elastic_chain/chains
config: /mnt/c/Users/up21736/Desktop/DEA/elastic_chain/./configs/
default_chain: validium
era_chain_id: 270
prover_version: NoProofs
wallet_creation: Localhost

Then, I run: zkstack ecosystem init --verbose

After this command, I get the same error as mentioned previously:

2025-03-05T12:37:45.019103Z ERROR zksync_node_framework::service: Task oneshot_runner failed: Oneshot task node_storage_initializer failed

Caused by:
    Root hash mismatched: From config: 0x7bdb3d822ad837a3611c436d3be457363a08d06d83b74469831482353a7d8277, Calculated 0xd8c9be7efb705e7dcf529c14fce7048ea99dea9eab6a6b4e5f8de1ebf4f2ebf2
2025-03-05T12:37:45.019150Z  INFO zksync_node_framework::service: One of the task has exited, shutting down the node
2025-03-05T12:37:45.019163Z  INFO zksync_node_framework::service: Exiting the service
Error: One or more tasks failed: ["Task oneshot_runner failed: Oneshot task node_storage_initializer failed: Root hash mismatched: From config: 0x7bdb3d822ad837a3611c436d3be457363a08d06d83b74469831482353a7d8277, Calculated 0xd8c9be7efb705e7dcf529c14fce7048ea99dea9eab6a6b4e5f8de1ebf4f2ebf2"]
│
■  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 /mnt/c/Users/up21736/Desktop/DEA/elastic_chain/chains/validium/configs/genesis.yaml --wallets-path /mnt/c/Users/up21736/Desktop/DEA/elastic_chain/chains/validium/configs/wallets.yaml --config-path /mnt/c/Users/up21736/Desktop/DEA/elastic_chain/chains/validium/configs/general.yaml --secrets-path /mnt/c/Users/up21736/Desktop/DEA/elastic_chain/chains/validium/configs/secrets.yaml --contracts-config-path /mnt/c/Users/up21736/Desktop/DEA/elastic_chain/chains/validium/configs/contracts.yaml --genesis
│
│    2: Command failed to run: cargo run --manifest-path ./core/Cargo.toml --release --bin zksync_server -- --genesis-path /mnt/c/Users/up21736/Desktop/DEA/elastic_chain/chains/validium/configs/genesis.yaml --wallets-path /mnt/c/Users/up21736/Desktop/DEA/elastic_chain/chains/validium/configs/wallets.yaml --config-path /mnt/c/Users/up21736/Desktop/DEA/elastic_chain/chains/validium/configs/general.yaml --secrets-path /mnt/c/Users/up21736/Desktop/DEA/elastic_chain/chains/validium/configs/secrets.yaml --contracts-config-path /mnt/c/Users/up21736/Desktop/DEA/elastic_chain/chains/validium/configs/contracts.yaml --genesis
│
└  Failed to run command

Dumb question but are you on Mac? Not sure if running this under WSL2 with Windows could cause problems or not. I am mounting my project into the WSL shell to access it and maybe this causes issues.

[cytadela8]

I'm not familiar with WSL. I'm running this on native Ubuntu 24.04 install. Root hash mismatch may happen due to some issue with contract compilation this command installs known good version of foundry foundryup-zksync -C 27360d4c8. To clear all artifacts the proven good way is to run something like rm -r contracts; git restore contracts; git submodule update --init --recursive.

But the issue with reth syncing with mainnet although it should be configured to launch a fork is a separate issue that does not happen for me :/

[cytadela8]

See also what you have in the ./etc/reth/chaindata reth should get the config from there. I would docker exec -it /bin/bash into the container to inspect whats going on inside. I would suspect that WSL docker somehow messes up this. docker-compose.yml that configures reth is in the zksync-era code root.

[abooo96]

Thanks so far. Lets see...