@ledgerhq/zcash-utils 2.5.0 → 2.5.1

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @ledgerhq/zcash-utils
 
+## 2.5.1
+
+### Patch Changes
+
+- c963227: The Node addon now creates Orchard and Ironwood proofs on every core, about five times faster on an Apple M1 Max; the proof itself is unchanged.
+
 ## 2.5.0
 
 ### Minor Changes

package/README.md

@@ -16,7 +16,7 @@ Published on the public npm registry under the `@ledgerhq` scope; no registry co
 
 Prebuilt `.node` binaries are bundled for six targets — `darwin-arm64`, `darwin-x64`, `linux-x64-gnu`, `linux-arm64-gnu`, `win32-x64-msvc`, `win32-arm64-msvc` — so there is no compilation step and no Rust toolchain to install. On any other platform, build from source: see [`CONTRIBUTING.md`](CONTRIBUTING.md).
 
-Node.js 20 or later. The addon is a native module, so it runs in Node and in the Electron main process, not in a browser or a renderer without `nodeIntegration`.
+Node.js 24 or later. The addon is a native module, so it runs in Node and in the Electron main process, not in a browser or a renderer without `nodeIntegration`.
 
 ## Quick start — scanning
 
@@ -155,7 +155,7 @@ Full signatures, every field, and its constraints are in [`index.d.ts`](index.d.
 
 | Export | Purpose |
 | --- | --- |
-| `buildTransaction(params)` | Builds, proves, and serializes a V5 PCZT from Orchard notes, transparent UTXOs, or both. Bears the Halo 2 proving cost inline (~2–5 s cold, ~hundreds of ms after, via a process-global proving-key cache). |
+| `buildTransaction(params)` | Builds, proves, and serializes a V5 PCZT from Orchard notes, transparent UTXOs, or both. Halo 2 proving runs on every core, off the JavaScript thread: about five times faster than on a single core (roughly 0.35–0.4 s per action on an Apple M1 Max), plus a one-time proving-key build per circuit (cached process-wide). The Node addon enables this. A consumer of the `zcash-crypto` Rust crate proves on a single core unless it enables the crate's `multicore` feature; inside this workspace, feature unification turns it on for every build and test. |
 | `buildIronwoodTransaction(params)` | Same, for an Ironwood (NU6.3) source — a redacted V6 PCZT. See [Ironwood (NU6.3)](#ironwood-nu63) below. |
 | `parsePczt(pcztHex)` | Decodes canonical PCZT bytes into the `PcztTransaction` the device signer consumes. Fails if a field the device needs to sign is missing. |
 | `finalizeTransaction(params)` | Injects device signatures, computes the binding signature, extracts the signed transaction and its txid. CPU-bound (proof verification), dispatched to a blocking thread. |

package/index.d.ts

@@ -285,10 +285,12 @@ export interface BuildTransactionResult {
  * Build, prove, and serialize a PCZT for a send transaction.
  *
  * Supports Orchard-source (Private→*) and transparent-source (Public→*)
- * flows. Halo 2 proof generation happens here for Orchard-bundle transactions
- * (~2-5 s first call, ~hundreds of ms thereafter thanks to the process-global
- * ProvingKey cache). Transparent-only transactions skip the Orchard prover, and
- * need no UFVK — see `ufvk` / `transparentAccountPubkey` on the params.
+ * flows. Halo 2 proof generation happens here for Orchard-bundle transactions.
+ * It runs on every core, off the JavaScript thread: about five times faster
+ * than on a single core (roughly 0.35–0.4 s per action on an Apple M1 Max),
+ * plus a one-time proving-key build per circuit that the
+ * process-global ProvingKey cache then amortizes. Transparent-only transactions
+ * skip the Orchard prover, and need no UFVK — see `ufvk` / `transparentAccountPubkey` on the params.
  *
  * Note: unlike `finalize_transaction` (purely CPU-bound, offloaded via
  * `spawn_blocking`), this is an async orchestrator that interleaves gRPC
@@ -375,9 +377,10 @@ export interface BuildIronwoodTransactionResult {
  * place of Orchard ones and emitting a V6 (ZIP-230) PCZT.
  *
  * Same proving-cost profile as `buildTransaction`: Halo 2 proof generation
- * happens here for the Ironwood bundle (~2-5 s first call against the
- * `PostNu6_3` circuit, ~hundreds of ms thereafter via the process-global
- * proving-key cache).
+ * happens here for the Ironwood bundle, on every core and off the JavaScript
+ * thread (roughly 0.35–0.4 s per action on an Apple M1 Max), plus a one-time
+ * proving-key build for the `PostNu6_3` circuit that the process-global
+ * proving-key cache then amortizes.
  */
 export declare function buildIronwoodTransaction(params: BuildIronwoodTransactionParams): Promise<BuildIronwoodTransactionResult>
 /** Parameters for finalizing a PCZT with device-provided signatures. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ledgerhq/zcash-utils",
-  "version": "2.5.0",
+  "version": "2.5.1",
   "description": "Native Zcash key derivation and shielded sync — Node.js (NAPI)",
   "main": "index.js",
   "types": "index.d.ts",
@@ -18,7 +18,7 @@
     "access": "public"
   },
   "devDependencies": {
-    "@changesets/cli": "^2.29.8",
+    "@changesets/cli": "^3.0.3",
     "@napi-rs/cli": "^2.18.0",
     "@types/node": "^25.5.2",
     "prettier": "^3.9.6",