chore(release): v1.4.0 (#2110)

Author: jonathanpwang

CHANGELOG.md

@@ -5,11 +5,12 @@ All notable changes to OpenVM will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project follows a versioning principles documented in [VERSIONING.md](./VERSIONING.md).
 
-## v1.4.0-rc (Unreleased)
+## v1.4.0 (2025-09-01)
 
 ### Added
 - (Verifier) An `AggVerifyingKey` struct is introduced so that verifying the final STARK proof does not require the proving key.
 - (Config) Added `addr_spaces` vector of `AddressSpaceHostConfig` to `MemoryConfig`.
+- (Prover) Nvidia GPU trace generation and STARK backend proving support.
 
 ### Changed
 - (Verifier) The `MultiStarkVerifyingKey`s for all existing App and Agg configs remain unchanged. However the serialized binary for the `AppVerifyingKey` has changed due to the removal of `as_offset` from `MemoryDimensions` (see below).

Cargo.toml

@@ -1,5 +1,5 @@
 [workspace.package]
-version = "1.4.0-rc.10"
+version = "1.4.0"
 edition = "2021"
 rust-version = "1.86.0"
 authors = ["OpenVM Authors"]
@@ -113,11 +113,11 @@ lto = "thin"
 
 [workspace.dependencies]
 # Stark Backend
-openvm-stark-backend = { git = "https://github.com/openvm-org/stark-backend.git", tag = "v1.2.0-rc.7", default-features = false }
-openvm-stark-sdk = { git = "https://github.com/openvm-org/stark-backend.git", tag = "v1.2.0-rc.7", default-features = false }
-openvm-cuda-backend = { git = "https://github.com/openvm-org/stark-backend.git", tag = "v1.2.0-rc.7", default-features = false }
-openvm-cuda-builder = { git = "https://github.com/openvm-org/stark-backend.git", tag = "v1.2.0-rc.7", default-features = false }
-openvm-cuda-common = { git = "https://github.com/openvm-org/stark-backend.git", tag = "v1.2.0-rc.7", default-features = false }
+openvm-stark-backend = { git = "https://github.com/openvm-org/stark-backend.git", tag = "v1.2.0", default-features = false }
+openvm-stark-sdk = { git = "https://github.com/openvm-org/stark-backend.git", tag = "v1.2.0", default-features = false }
+openvm-cuda-backend = { git = "https://github.com/openvm-org/stark-backend.git", tag = "v1.2.0", default-features = false }
+openvm-cuda-builder = { git = "https://github.com/openvm-org/stark-backend.git", tag = "v1.2.0", default-features = false }
+openvm-cuda-common = { git = "https://github.com/openvm-org/stark-backend.git", tag = "v1.2.0", default-features = false }
 
 # OpenVM
 openvm-sdk = { path = "crates/sdk", default-features = false }

crates/circuits/mod-builder/src/README.md

@@ -84,7 +84,7 @@ Note that the variables in the expression tree don't actually have names, they a
 The `ExprBuilder` struct stores the constraints and computes associated to a single circuit.
 Every `FieldVariable` stores a shared reference to an `ExprBuilder` and it mutates the builder as needed.
 
-When we are done building the circuit, the `ExprBuilder` has all the data necessary to build the circuit. 
+When we are done building the circuit, the `ExprBuilder` has all the data necessary to build the circuit.
 We can pass the `ExprBuilder` into the `FieldExpr` constructor to build an AIR.
 
 ## The Select operation
@@ -140,7 +140,7 @@ Increase `range_checker_bits` and try again.
 
 This error could also occur if you are calling `FieldVariable::int_add` or `FieldVariable::int_mul` with large constants.
 These methods are not meant to be called with large constants.
-Instead create a constant with `ExprBuilder::new_const` and use that. 
+Instead create a constant with `ExprBuilder::new_const` and use that.
 
 
 ## Usage
@@ -169,7 +169,7 @@ See the [examples section](#examples) for code examples to follow along with.
    Usually you don't need to do this because variables are auto-saved when there is a possibility of overflow (i.e. when the carry for any of the limbs overflows).
    But it gives greater control over how the expression is broken down into constraints, if that's needed.
 
-7. Finally, pull out a copy of the builder as follows: `let builder = builder.borrow().clone()`, and pass it into the appropriate `FieldExpr` constructor: 
+7. Finally, pull out a copy of the builder as follows: `let builder = builder.borrow().clone()`, and pass it into the appropriate `FieldExpr` constructor:
     - If your chip has no setup instruction, use `FieldExpr::new(builder, range_bus, false)`.
     - If your chip has a setup instruction that only checks if the modulus is correct, use `FieldExpr::new(builder, range_bus, true)`.
     - If your chip has a setup instruction that checks the correctness of more than just the modulus, use `FieldExpr::new_with_setup_values(builder, range_bus, true, setup_values)` where `setup_values` is a `Vec<BigUint>` of values to be used in setup.
@@ -179,6 +179,5 @@ See the [examples section](#examples) for code examples to follow along with.
 
 See these examples in the elliptic curve extension code:
 
-- [Short Weierstrass Addition Chip](https://github.com/openvm-org/openvm/blob/main/extensions/ecc/circuit/src/weierstrass_chip/add_ne.rs)
-- [Short Weierstrass Double Chip](https://github.com/openvm-org/openvm/blob/main/extensions/ecc/circuit/src/weierstrass_chip/double.rs)
-
+- [Short Weierstrass Addition Chip](https://github.com/openvm-org/openvm/blob/main/extensions/ecc/circuit/src/weierstrass_chip/add_ne/mod.rs)
+- [Short Weierstrass Double Chip](https://github.com/openvm-org/openvm/blob/main/extensions/ecc/circuit/src/weierstrass_chip/double/mod.rs)

docs/vocs/docs/pages/book/acceleration-using-extensions/algebra.mdx

@@ -114,8 +114,8 @@ To have the correct imports for the above example, add the following to the `Car
 
 ```toml
 [dependencies]
-openvm = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0-rc.10" }
-openvm-algebra-guest = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0-rc.10" }
+openvm = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0" }
+openvm-algebra-guest = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0" }
 serde = { version = "1.0.216", default-features = false }
 ```
 

docs/vocs/docs/pages/book/getting-started/install.mdx

@@ -66,7 +66,7 @@ svm use 0.8.19
 Begin the installation:
 
 ```bash
-cargo +1.86 install --locked --git https://github.com/openvm-org/openvm.git --tag v1.4.0-rc.10 cargo-openvm
+cargo +1.86 install --locked --git https://github.com/openvm-org/openvm.git --tag v1.4.0 cargo-openvm
 ```
 
 This will globally install `cargo-openvm`. You can validate a successful installation with:
@@ -80,7 +80,7 @@ cargo openvm --version
 To build from source, clone the repository and begin the installation.
 
 ```bash
-git clone --branch v1.4.0-rc.10 --single-branch https://github.com/openvm-org/openvm.git
+git clone --branch v1.4.0 --single-branch https://github.com/openvm-org/openvm.git
 cd openvm
 cargo install --locked --force --path crates/cli
 ```
@@ -143,7 +143,7 @@ Note that `/usr/local/cuda` is a symlink for the latest version of CUDA installe
 Begin the installation:
 
 ```bash
-cargo +1.86 install --locked --git https://github.com/openvm-org/openvm.git --tag v1.4.0-rc.10 --features cuda cargo-openvm
+cargo +1.86 install --locked --git https://github.com/openvm-org/openvm.git --tag v1.4.0 --features cuda cargo-openvm
 ```
 
 This will globally install `cargo-openvm`. You can validate a successful installation with:
@@ -157,7 +157,7 @@ cargo openvm --version
 To build from source, clone the repository and begin the installation.
 
 ```bash
-git clone --branch v1.4.0-rc.10 --single-branch https://github.com/openvm-org/openvm.git
+git clone --branch v1.4.0 --single-branch https://github.com/openvm-org/openvm.git
 cd openvm
 cargo install --locked --force --path crates/cli --features cuda
 ```
@@ -184,10 +184,10 @@ Begin the installation:
 
 :::code-group
 ```bash [Without GPU]
-cargo +nightly-2025-08-19 install --locked --git https://github.com/openvm-org/openvm.git --tag v1.4.0-rc.10 --features tco cargo-openvm
+cargo +nightly-2025-08-19 install --locked --git https://github.com/openvm-org/openvm.git --tag v1.4.0 --features tco cargo-openvm
 ```
 ```bash [Nvidia GPU]
-cargo +nightly-2025-08-19 install --locked --git https://github.com/openvm-org/openvm.git --tag v1.4.0-rc.10 --features tco,cuda cargo-openvm
+cargo +nightly-2025-08-19 install --locked --git https://github.com/openvm-org/openvm.git --tag v1.4.0 --features tco,cuda cargo-openvm
 ```
 :::
 
@@ -202,7 +202,7 @@ cargo openvm --version
 To build from source, first clone the repository.
 
 ```bash
-git clone --branch v1.4.0-rc.10 --single-branch https://github.com/openvm-org/openvm.git
+git clone --branch v1.4.0 --single-branch https://github.com/openvm-org/openvm.git
 cd openvm
 ```
 

docs/vocs/docs/pages/book/getting-started/quickstart.mdx

@@ -14,7 +14,7 @@ This will generate an OpenVM-specific starter package. Notice `Cargo.toml` has t
 
 ```toml
 [dependencies]
-openvm = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0-rc.10", features = ["std"] }
+openvm = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0", features = ["std"] }
 ```
 
 Note that `std` is not enabled by default, so explicitly enabling it is required.

docs/vocs/docs/pages/book/guest-libraries/k256.mdx

@@ -1,6 +1,6 @@
 # K256
 
-The K256 guest library uses [`openvm-ecc-guest`](/book/acceleration-using-extensions/elliptic-curve-cryptography) to provide elliptic curve operations over the Secp256k1 curve. It is intended as a patch for the [`k256`](https://crates.io/crates/k256) rust crate and can be swapped in for accelerated signature verification usage. Note that signing from a private key is not supported. 
+The K256 guest library uses [`openvm-ecc-guest`](/book/acceleration-using-extensions/elliptic-curve-cryptography) to provide elliptic curve operations over the Secp256k1 curve. It is intended as a patch for the [`k256`](https://crates.io/crates/k256) rust crate and can be swapped in for accelerated signature verification usage. Note that signing from a private key is not supported.
 
 
 ## Example program
@@ -10,9 +10,9 @@ See a working example [here](https://github.com/openvm-org/openvm/blob/main/exam
 To use the K256 guest library, add the following dependencies to `Cargo.toml`:
 
 ```toml
-openvm-algebra-guest = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0-rc.10" }
-openvm-ecc-guest = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0-rc.10" }
-openvm-k256 = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0-rc.10", package = "k256" }
+openvm-algebra-guest = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0" }
+openvm-ecc-guest = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0" }
+openvm-k256 = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0", package = "k256" }
 ```
 
 The guest library provides a `Secp256k1Coord`, which represents a field element on the coordinate field of Secp256k1, and a `Secp256k1Point`, which represents an Secp256k1 elliptic curve point.
@@ -53,4 +53,3 @@ The `supported_moduli` parameter is a list of moduli that the guest program will
 The `ecc.supported_curves` parameter is a list of supported curves that the guest program will use. They must be provided in decimal format in the `.toml` file. For multiple curves create multiple `[[app_vm_config.ecc.supported_curves]]` sections. The order of curves in `[[app_vm_config.ecc.supported_curves]]` must match the order in the `sw_init!` macro.
 Also, the `struct_name` field must be the name of the elliptic curve struct created by `sw_declare!`.
 In this example, the `Secp256k1Point` struct is created in `openvm_ecc_guest::k256`.
-

docs/vocs/docs/pages/book/guest-libraries/keccak256.mdx

@@ -17,7 +17,7 @@ See the full example [here](https://github.com/openvm-org/openvm/blob/main/examp
 To be able to import the `keccak256` function, add the following to your `Cargo.toml` file:
 
 ```toml
-openvm-keccak256 = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0-rc.10" }
+openvm-keccak256 = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0" }
 hex = { version = "0.4.3" }
 ```
 

docs/vocs/docs/pages/book/guest-libraries/ruint.mdx

@@ -1,4 +1,4 @@
-# Ruint 
+# Ruint
 
 The Ruint guest library is a fork of [ruint](https://github.com/recmo/uint) that allows for patching of U256 operations with logic from [openvm-bigint-guest](/book/acceleration-using-extensions/big-integer).
 
@@ -13,7 +13,7 @@ See the full example [here](https://github.com/openvm-org/openvm/blob/main/examp
 To be able to import the `U256` struct, add the following to your `Cargo.toml` file:
 
 ```toml
-openvm-ruint = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0-rc.10", package = "ruint" }
+openvm-ruint = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0", package = "ruint" }
 ```
 
 ### Example matrix multiplication using `I256`
@@ -27,7 +27,7 @@ See the full example [here](https://github.com/openvm-org/openvm/blob/main/examp
 To be able to import the `I256` struct, add the following to your `Cargo.toml` file:
 
 ```toml
-openvm-ruint = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0-rc.10", package = "ruint" }
+openvm-ruint = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0", package = "ruint" }
 ```
 
 ### Config parameters

docs/vocs/docs/pages/book/guest-libraries/sha2.mdx

@@ -25,7 +25,7 @@ See the full example [here](https://github.com/openvm-org/openvm/blob/main/examp
 To be able to import the `sha256` function, add the following to your `Cargo.toml` file:
 
 ```toml
-openvm-sha2 = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0-rc.10" }
+openvm-sha2 = { git = "https://github.com/openvm-org/openvm.git", tag = "v1.4.0" }
 hex = { version = "0.4.3" }
 ```
 
@@ -34,4 +34,4 @@ hex = { version = "0.4.3" }
 For the guest program to build successfully add the following to your `.toml` file:
 
 ```toml
-[app_vm_config.sha256]
+[app_vm_config.sha256]