[ZK Stack] - Getting Started is failing when Deploying L1 Contracts

[web3technologies]

Team or Project

Quasm

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

Operating System

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

Issue Description

When I follow the Getting Started with ZK Stack I am able to create the ecosystem successfully. When I run zkstack ecosystem init --dev I am getting an error for a missing value in the toml file.

Expected Behavior

I am expecting the zk stack walkthrough to allow me to deploy a local instance of a chain so I can run some tests

Current Behavior

Currently when deploying the L1 contracts the script is failing to a missing toml value.

Repository Link (if applicable)

No response

Additional Details

Prior Research

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

[dimazhornyk]

Hello, thanks for reporting the issue.
Try doing the following:

• foundryup-zksync
  • curl -L https://raw.githubusercontent.com/matter-labs/foundry-zksync/main/install-foundry-zksync | bash and foundryup-zksync again if it failed the first time
• rm -rf ./contracts
• git submodule update --init --recursive
• zkstack dev clean all
• zkstack containers
• zkstack ecosystem init --dev

And let us know if that helps!

[web3technologies]

Thanks for your response however I have tried this a couple different times and still receiving the same error, missing the support_l2_legacy_shared_bridge_test value in the toml file.

[dimazhornyk]

Got it, we will try reproducing it. Could you please share the commit you are currently on?

[MexicanAce]

I'm able to reproduce from the latest main commit: e32fee0. I'll take a closer look as to what's missing.

│      ├─ [0] VM::writeToml("<stringified TOML>",
│      "/Users/nick/github/matter-labs/zksync-era/contracts/l1-contracts/script-out/diamond-selectors.toml")
│      │ └─ ← [Return]
│      ├─ [0]
│      VM::readFile("/Users/nick/github/matter-labs/zksync-era/contracts/l1-contracts/script-config/config-deploy-l1.toml")
│      [staticcall]
│      │ └─ ← [Return] <file>
│      ├─ [0] VM::parseTomlUint("<stringified TOML>", "$.era_chain_id") [staticcall]
│      │ └─ ← [Return] 270
│      ├─ [0] VM::parseTomlAddress("<stringified TOML>", "$.owner_address") [staticcall]
│      │ └─ ← [Return] 0x8002cD98Cfb563492A6fB3E7C8243b7B9Ad4cc92
│      ├─ [0] VM::parseTomlBool("<stringified TOML>", "$.testnet_verifier") [staticcall]
│      │ └─ ← [Return] true
│      ├─ [0] VM::parseTomlBool("<stringified TOML>", "$.support_l2_legacy_shared_bridge_test") [staticcall]
│      │ └─ ← [Revert] vm.parseTomlBool: path "$.support_l2_legacy_shared_bridge_test" must return exactly one JSON
│      value
│      └─ ← [Revert] vm.parseTomlBool: path "$.support_l2_legacy_shared_bridge_test" must return exactly one JSON value
│      
│      
│      
│      == Logs ==
│      Deploying L1 contracts
│      
│  
│    Stderr:
│      Error: script failed: vm.parseTomlBool: path "$.support_l2_legacy_shared_bridge_test" must return exactly one JSON value

[MexicanAce]

@web3technologies Please try to run zkstackup --local and then try zkstack ecosystem init --dev again.

The addition of the support_l2_legacy_shared_bridge_test was added as some point, and so running zkstackup will update your zkstack cli tool to the latest version.

I've confirmed this fixed the issue on my local 👍

[web3technologies]

Works on my local thanks @MexicanAce !