[ZK Stack] - <zkstack prover setup-keys>

[L0GYKAL]

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

I am running zkstack prover setup-keys to generate the keys locally and the command fails:

┌   ZK Stack CLI 
│
◇  Do you want to download the setup keys or generate them?
│  Generate 
│
◐  Generating setup keys...                                                                                                                                            │
■  Command failed to run
│  
■    Status:
│      exit status: 101
│    Stdout:
│      
│  
│    Stderr:
│      Compiling zerocopy v0.7.35
│      Compiling impl-serde v0.4.0
│      Compiling zksync_ff v0.30.13
│      Compiling smallvec v1.13.2
│      Compiling rayon v1.10.0
│      Compiling itertools v0.10.5
│      Compiling bincode v1.3.3
│      Compiling bit-vec v0.6.3
│      Compiling zksync-gpu-ffi v0.152.11
│      Compiling futures-locks v0.7.1
│      Compiling heck v0.3.3
│      Compiling strsim v0.8.0
│      Compiling vec_map v0.8.2
│      Compiling bitflags v1.3.2
│      Compiling ansi_term v0.12.1
│      Compiling itertools v0.13.0
│      Compiling env_filter v0.1.2
│      Compiling humantime v2.1.0
│      The following warnings were emitted during compilation:
│      
│      warning: zksync-gpu-ffi@0.152.11: CUDA Toolkit version V12.0.140 detected. This crate is only tested with CUDA Toolkit
│      version 12.*.
│      
│      error: failed to run custom build command for `zksync-gpu-ffi v0.152.11`
│      
│      Caused by:
│      process didn't exit successfully:
│      `/home/ubuntu/benchomarko/zksync-era/prover/target/release/build/zksync-gpu-ffi-b32b24a0bceef640/build-script-build`
│      (exit status: 101)
│      --- stdout
│      cargo::rustc-check-cfg=cfg(no_cuda)
│      cargo::warning=CUDA Toolkit version V12.0.140 detected. This crate is only tested with CUDA Toolkit version 12.*.
│      
│      --- stderr
│      thread 'main' panicked at
│      /home/ubuntu/.cargo/registry/src/index.crates.io-6f17d22bba15001f/zksync-gpu-ffi-0.152.11/build.rs:17:56:
│      called `Result::unwrap()` on an `Err` value: NotPresent
│      note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
│      warning: build failed, waiting for other jobs to finish...
│      
│  
■  Command failed to run: cargo run --features gpu --release --bin key_generator -- generate-sk-gpu all --recompute-if-missing --setup-path=data/keys --path=/home/ubuntu/benchomarko/zksync-era/prover/data/keys
│     Compiling zerocopy v0.7.35
│     Compiling impl-serde v0.4.0
│     Compiling zksync_ff v0.30.13
│     Compiling smallvec v1.13.2
│     Compiling rayon v1.10.0
│     Compiling itertools v0.10.5
│     Compiling bincode v1.3.3
│     Compiling bit-vec v0.6.3
│     Compiling zksync-gpu-ffi v0.152.11
│     Compiling futures-locks v0.7.1
│     Compiling heck v0.3.3
│     Compiling strsim v0.8.0
│     Compiling vec_map v0.8.2
│     Compiling bitflags v1.3.2
│     Compiling ansi_term v0.12.1
│     Compiling itertools v0.13.0
│     Compiling env_filter v0.1.2
│     Compiling humantime v2.1.0
│  The following warnings were emitted during compilation:
│  
│  warning: zksync-gpu-ffi@0.152.11: CUDA Toolkit version V12.0.140 detected. This crate is only tested with CUDA Toolkit version 12.*.
│  
│  error: failed to run custom build command for `zksync-gpu-ffi v0.152.11`
│  
│  Caused by:
│    process didn't exit successfully: `/home/ubuntu/benchomarko/zksync-era/prover/target/release/build/zksync-gpu-ffi-b32b24a0bceef640/build-script-build` (exit status: 101)
│    --- stdout
│    cargo::rustc-check-cfg=cfg(no_cuda)
│    cargo::warning=CUDA Toolkit version V12.0.140 detected. This crate is only tested with CUDA Toolkit version 12.*.
│  
│    --- stderr
│    thread 'main' panicked at /home/ubuntu/.cargo/registry/src/index.crates.io-6f17d22bba15001f/zksync-gpu-ffi-0.152.11/build.rs:17:56:
│    called `Result::unwrap()` on an `Err` value: NotPresent
│    note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
│  warning: build failed, waiting for other jobs to finish...
│  
│  
▲    0: Command failed to run: cargo run --features gpu --release --bin key_generator -- generate-sk-gpu all --recompute-if-missing --setup-path=data/keys --path=/home/ubuntu/benchomarko/zksync-era/prover/data/keys
│  
└  Failed to run command

Expected Behavior

The command should generate the keys without compilation errors

Current Behavior

It is impossible to generate the setup-keys

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]

Going to look into this and see if I can replicate. Will get back to you after

[bxpana]

Ok, let me see what else could be causing this.

[bxpana]

Can you check your BELLMAN_CUDA_DIR env variable is set to where you have the directory? If it's not, https://github.com/matter-labs/era-bellman-cuda/ needs to be cloned somewhere and the BELLMAN_CUDA_DIR needs to point to that location

[MexicanAce]

@L0GYKAL Wanting to check back in and see if updating this env variable and cloning the era-bellman-cuda repo helped resolve the issue?

[MexicanAce]

@L0GYKAL Alternatively, I believe you should be able to run zkstack prover init-bellman-cuda --clone to complete that setup prior to running zkstack prover setup-keys.

[MexicanAce]

@L0GYKAL I'm marking my above response as the answer in case others come across this Discussion. If this did not resolve your issues, feel free to unmark it as the answer and we can continue the investigation.