---
description: As of August 2024
---

# Benchmarks

Abstract\



The Valida zk-VM will offer industry leading speed and efficiency in succinctly proving program executions. The preliminary benchmarks in this report provide evidence for this claim. The following table summarizes how many times faster Valida is compared to RISC Zero, SP1, and Jolt for the examples we studied:

#### Iterative Fibonacci (n=25)

<table><thead><tr><th width="306">Valida Advantage (X faster)</th><th>RISC0</th><th>SP1</th><th>Jolt</th></tr></thead><tbody><tr><td>CPU efficiency (single-core Valida)</td><td>1024</td><td>3461</td><td>66</td></tr><tr><td>CPU efficiency (Multi-core Valida)</td><td>205</td><td>1130</td><td>13</td></tr><tr><td>Wall clock time (single-core Valida)</td><td>37</td><td>349</td><td>15</td></tr><tr><td>Wall clock time (Multi-core Valida)</td><td>56</td><td>423</td><td>23</td></tr></tbody></table>

#### SHA-256

<table><thead><tr><th width="306">Valida Advantage (X faster)</th><th>RISC0</th><th>SP1</th><th>Jolt</th></tr></thead><tbody><tr><td>CPU efficiency (single-core Valida)</td><td>66</td><td>304</td><td>6.4</td></tr><tr><td>CPU efficiency (Multi-core Valida)</td><td>26.6</td><td>123</td><td>2.6</td></tr><tr><td>Wall clock time (single-core Valida)</td><td>2.5</td><td>12</td><td>1.2</td></tr><tr><td>Wall clock time (Multi-core Valida)</td><td>12</td><td>53.5</td><td>5.4</td></tr></tbody></table>



## Status of Valida and its compiler toolchain



The Valida ISA is a work in progress. The [working ISA spec](https://github.com/valida-xyz/valida-compiler/issues/2) forms the core of it. There are ongoing efforts to figure out what would be a sufficient set of extensions to the Valida ISA to support efficient execution of most programs. The working ISA spec does not include all instructions currently supported by the Valida zk-VM.



The Valida ISA has a modular architecture which allows for application developers to choose which subsets of the ISA (called “chips”) they require for their use case. There is a default selection of chips known as the basic Valida ISA, which is supposed to support efficient execution of most programs. Application developers can add specialized chips to support their particular use cases; e.g., specialized chips may compute hash permutations, elliptic curve group operations, or other expensive, frequently used functions.



[The Valida zk-VM implementation](https://github.com/valida-xyz/valida) is available to the public. There are some known issues with the Valida zk-VM implementation affecting correctness and completeness of the prover / verifier pair:



1. The memory argument is not fully sound.
2.  The following arithmetic operations are unconstrained or wrongly constrained:

    * DIV32 (32-bit unsigned division),
    * MULHU32 (32-bit unsigned multiply, high bits only), and
    * MULHS32 (32-bit signed multiply, high bits only).



All of the known non-working and missing constraints are in the process of being added or replaced, or they are planned to be added or replaced in the near future. None of these appear particularly risky, either from a timeline or performance standpoint, in that workable approaches are known for all of them and we as Lita Foundation expect some of these to be reasonably performant.



We as Lita Foundation are internally auditing the Valida zk-VM. We will report any issues we find, as we find them. We also plan to submit Valida for a third party external audit.



There is an LLVM-based compiler toolchain for Valida, which can compile some simple C and Rust programs into Valida programs. Broader language support is also planned for the Valida compiler toolchain, including Go. The alpha version of our C and Rust compiler has been released. See [here](https://lita.gitbook.io/lita-documentation/quick-start/tutorial-rust-via-docker) to get started!



Future directions\



Future studies should compare the performance of Valida using more example programs, against more provers, on more platforms, and with larger problem sizes.



Ongoing work on the Valida prover / verifier pair will address the known issues with its correctness and completeness, as well as further auditing and verifying Valida to flush out any unknown issues.



The Valida prover contains bottlenecks which result in inconsistent CPU utilization throughout the proving process. Better usage of the available parallelism may be able to get rid of these bottlenecks, resulting in better prover wall clock time. Reducing the memory footprint of the Valida prover could also be useful.



Ongoing work on the Valida LLVM backend will allow it to compile a wider variety of source programs in a wider variety of source languages. Future work on the Valida LLVM backend will also improve the efficiency of the generated code.



Future work should run the Valida prover in hardware accelerated settings, using coprocessors like GPUs or Fabric Cryptography’s VPUs. This may result in exponential improvements to the speed and efficiency of proving.



Other choices of proving algorithms may provide further breakthroughs in speed and efficiency of proving. The relevance of upcoming research in zero knowledge cryptography to Valida proving should be studied.

\
\
