Practical overview
When it fits
Use it when a security research workflow needs local proof generation for an EVM exploit demonstration or PoC.
Who it is for
- Security researchers creating EVM exploit proof-of-concepts.
- Developers who want a local proof-generation step alongside exploit demonstrations.
Documented uses
- Generate a zero-knowledge proof related to an EVM exploit using a supplied RPC URL, block number, deal value and path.
- Choose a documented Metal, CUDA or CPU execution path for the proof-generation command.
- Start from the repository’s recommended PoC demos after installing zkProver.
Requirements & limits
The public repository includes build-from-source instructions. The README states installation support for Linux and macOS with Apple Silicon; Windows appears in CUDA and CPU usage examples.
- The documented commands require an RPC URL, block number, deal value and path.
- The macOS Metal path requires Apple Silicon and a successful Xcode and Metal setup.
- The README warns CPU-only proof generation may be very slow.
- The README lists Rust and platform-specific build tools for source builds; CUDA is optional in its Linux build prerequisites.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Generate an EVM proof with a documented execution path
Run the README’s EVM proof-generation command with Metal, CUDA or CPU execution.
Before you start
- A source-built zkProver environment with Rust and the applicable platform build tools.
- An RPC URL, block number, deal value and path for the command.
- For macOS Metal: Apple Silicon, Xcode, installed Xcode command-line tools and successful
xcrun metalsetup.
Steps
Choose the command matching the environment: Metal for macOS, CUDA for Linux or Windows, or CPU-only for Linux, Windows or macOS.
Run the command below for the documented macOS Metal path.
cargo run -r -p zkProver -F metal -- evm -r -b -dFor CUDA, run the command below; for CPU-only, omit the feature flag as shown in the README.
cargo run -r -p zkProver -F cuda -- evm -r -b -d
Expected outcome
The command invokes zkProver’s EVM zero-knowledge proof-generation workflow using the selected execution path.
Guide limitations
- CPU-only generation is not recommended because it may be very slow.
- The README does not specify hardware requirements or expected performance.
- The Windows example is provided for CUDA and CPU usage; installation support is stated for Linux and macOS with Apple Silicon.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 17 October 2026
- Original website title
- SecurFi/zkProver · Official homepage title · retained in its source language

