Imports & Dependencies

The protocol crates move from 0.15.3 to 0.16.1, miden-client from 0.15 to 0.16.1, and the VM crates jump 0.23 → 0.29.2 — six minor versions, not one. miden-crypto was absorbed into the Miden VM workspace and now shares its version number (0.25 → 0.29.2). The client and protocol MSRV is Rust 1.98.1. Because the MAST wire format, the package format, and several commitment preimages changed, 0.15 artifacts do not round-trip: re-assemble every package from source, recreate your local store, and upgrade your node in lockstep with your client.

Quick Fix

Cargo.toml

# Replace these
miden-client              = "0.15"
miden-client-sqlite-store = "0.15"
miden-protocol            = "0.15.3"
miden-standards           = "0.15.3"
miden-tx                  = "0.15.3"
miden-tx-batch-prover     = "0.15.3"
miden-assembly            = "0.23"
miden-core                = "0.23"
miden-core-lib            = "0.23"
miden-processor           = "0.23"
miden-prover              = "0.23"
miden-crypto              = "0.25"

# With these
miden-client              = "0.16.1"
miden-client-sqlite-store = "0.16.1"
miden-protocol            = "0.16.1"
miden-standards           = "0.16.1"
miden-tx                  = "0.16.1"
miden-tx-batch            = "0.16.1"   # renamed from miden-tx-batch-prover
miden-assembly            = "0.29.2"
miden-core                = "0.29.2"
miden-core-lib            = "0.29.2"
miden-processor           = "0.29.2"
miden-prover              = "0.29.2"
miden-crypto              = "0.29.2"

package.json (Web SDK)

{
  "@miden-sdk/miden-sdk": "0.16.1",
  "@miden-sdk/react": "0.16.0"
}

Then run:

cargo update && cargo build

If you encounter errors, continue reading for detailed migration steps.

The protocol and client crates are now published as stable v0.16 releases. The examples above pin the patch versions used to validate this snapshot.

The MAST wire format moved 0.0.3 → 0.0.4 and the package format 4.0.0 → 6.0.0, so serialized packages and MastForest blobs from 0.15 will not load. The .masl library format no longer exists at all. Several commitment preimages also changed (ECDSA public keys, MMR peaks, empty domain-separated hashes), so derived values must be recomputed. Re-assemble from source and re-sync into a fresh store.

---

Summary

Every layer of the stack moves:

• The protocol crates (miden-protocol, miden-standards, miden-tx, miden-testing) go 0.15.3 → 0.16.1.
• The VM crates (miden-assembly, miden-core, miden-core-lib, miden-processor, miden-prover, miden-mast-package) go 0.23 → 0.29.2. This is a much larger jump than previous releases and carries breaking MASM language changes — see VM & Assembler Changes.
• miden-crypto goes 0.25 → 0.29.2. It is no longer an independent crate line: it was imported into the Miden VM workspace and now shares the VM version number.
• miden-client and miden-client-sqlite-store go 0.15 → 0.16.0.
• The Web SDK packages go 0.15 → 0.16.0.

Two crates changed identity: miden-tx-batch-prover is now miden-tx-batch, and a new miden-protocol-build-utils crate provides MASM assembly helpers. On the VM side the core package was split, adding a miden-precompiles package alongside miden-core.

---

Version Bumps

Crate	v0.15	v0.16
miden-client	0.15	0.16.0
miden-client-sqlite-store	0.15	0.16.0
miden-protocol	0.15.3	0.16.0
miden-standards	0.15.3	0.16.0
miden-tx	0.15.3	0.16.0
miden-testing	0.15.3	0.16.0
miden-tx-batch-prover	0.15.3	renamed to miden-tx-batch 0.16.0
miden-protocol-build-utils	—	0.16.0 (new)
miden-assembly	0.23	0.29.2
miden-core	0.23	0.29.2
miden-core-lib	0.23	0.29.2
miden-processor	0.23	0.29.2
miden-prover	0.23	0.29.2
miden-verifier	0.23	0.29.2
miden-mast-package	0.23	0.29.2
miden-precompiles	—	0.29.2 (new)
miden-crypto	0.25	0.29.2

npm package	v0.15	v0.16
@miden-sdk/miden-sdk	0.15.x	0.16.0
@miden-sdk/react	0.15.x	0.16.0
@miden-sdk/vite-plugin	—	0.16.0

Earlier guidance listed a miden-idxdb-store npm dependency. No such package exists on the public registry — the IndexedDB store ships inside @miden-sdk/miden-sdk. Remove it from your package.json if you carried it over.

---

Affected Code

Cargo.toml:

- miden-client              = "0.15"
- miden-client-sqlite-store = "0.15"
- miden-protocol            = "0.15.3"
- miden-standards           = "0.15.3"
- miden-tx                  = "0.15.3"
- miden-tx-batch-prover     = "0.15.3"
- miden-assembly            = "0.23"
- miden-core                = "0.23"
- miden-core-lib            = "0.23"
- miden-processor           = "0.23"
- miden-prover              = "0.23"
- miden-crypto              = "0.25"
+ miden-client              = "0.16.1"
+ miden-client-sqlite-store = "0.16.1"
+ miden-protocol            = "0.16.1"
+ miden-standards           = "0.16.1"
+ miden-tx                  = "0.16.1"
+ miden-tx-batch            = "0.16.1"
+ miden-assembly            = "0.29.2"
+ miden-core                = "0.29.2"
+ miden-core-lib            = "0.29.2"
+ miden-processor           = "0.29.2"
+ miden-prover              = "0.29.2"
+ miden-crypto              = "0.29.2"

package.json (Web SDK):

- "@miden-sdk/miden-sdk": "^0.15.0",
- "@miden-sdk/react": "^0.15.0",
- "miden-idxdb-store": "^0.15.0"
+ "@miden-sdk/miden-sdk": "0.16.1",
+ "@miden-sdk/react": "0.16.0"

---

MSRV (Minimum Supported Rust Version)

The MSRV rose across the board. Update your rust-toolchain.toml to Rust 1.98.1 for client and protocol development:

rust-toolchain.toml

[toolchain]
channel = "1.98.1"

Component	v0.15	v0.16
protocol crates	1.90	1.98.1
miden-client	1.93	1.98.1
Miden VM	1.90	1.96.1

---

Migration Steps

1. Bump every Miden crate per the table above and run cargo update.
2. Rename the miden-tx-batch-prover dependency to miden-tx-batch if you used it.
3. Set your toolchain to at least Rust 1.98.1 (1.99 when building the Rust contract SDK/compiler).
4. Bump @miden-sdk/miden-sdk and @miden-sdk/react together — mixing 0.15 and 0.16 packages will not link against the shared WASM ABI. Drop any miden-idxdb-store dependency.
5. Re-assemble every .masp package from source under the new toolchain, and delete cached MastForest blobs. The .masl format is gone entirely.
6. Recreate your local store. The SQLite store's schema fingerprint changed and existing databases are rejected; browser users have their IndexedDB store cleared automatically on the version bump. See Client Changes.
7. Upgrade your node together with your client. 0.16 clients seal transaction inputs before submission; a 0.16 node rejects plaintext submissions and an older node rejects sealed ones, so the two cannot be mixed.

---

Common Errors

Error Message	Cause	Solution
failed to select a version for miden-protocol	Miden dependencies resolved to incompatible patch or prerelease versions	Pin the validated stable versions above and update the lockfile.
failed to select a version for miden-tx-batch-prover	Crate renamed in 0.16	Depend on miden-tx-batch instead.
MastForest deserialization failed: unexpected version	MAST wire format moved to 0.0.4	Re-assemble every package from source under VM 0.29.2.
package fails to load with a version mismatch	Package format moved to 6.0.0	Rebuild the .masp; .masl is no longer supported at all.
Migration error: Attempt to migrate a database with a migration number that is too high	Existing SQLite store predates the 0.16 schema	Delete and recreate the store, then re-sync.
Node rejects a submitted transaction	Client and node versions are mixed	Upgrade both to 0.16; sealed and plaintext submissions are mutually incompatible.
rustc version error during build	Client and protocol MSRV raised to 1.98.1; compiler MSRV is 1.99	Update rust-toolchain.toml for the components you build.