Skip to main content

Wallet SDK v2.0.1 release notes

For the complete documentation index, see llms.txt
  • Version: v2.0.1
  • Date: 2026-11-16
  • Environment: Mainnet, Preview, Preprod

High-level summary​

Wallet SDK 2.0.1 is a patch release on the 2.0 line. It upgrades @midnightntwrk/ledger-v9 from ^1.0.0 to 1.0.2 and runs proof server 9.0.2. The ledger-v9 key material is unchanged (circuit generation 10), so wallets don't need to re-derive keys or re-sync for this release.

Test stacks move to node 2.1.101 and indexer 4.4.101.


Audience​

This release is relevant for developers who:

  • Build or maintain a wallet for Mainnet, Preview, or Preprod
  • Use the wallet SDK in a DApp, a backend service, or tests

What changed (Summary of updates)​

  • Upgrades @midnightntwrk/ledger-v9 to 1.0.2 and runs proof server 9.0.2. Ledger-v9's key material is unchanged (circuit generation 10).
  • Test stacks move to node 2.1.101 and indexer 4.4.101.
  • The wallet SDK packages move together to the versions in the table below.

Fixes​

  • In-process proving of Compact 0.36 circuits (prover-client 2.0.1). WasmProver now proves circuits compiled with compactc 0.36.0 or later, which emit ZKIR v3 only. Before, every such circuit failed with expected one of 'ir-source[v2-generic]' or 'ir-source[v2]', got 'ir-source[v3-generic]'.
  • Job Queue full from a busy proof server (capabilities 4.0.1). The HTTP prover client keeps at most 10 requests waiting at a proof server (maxConcurrentRequests beside url in provers changes it), and retries HTTP 429, 502, 503 and 504 with backoff for up to 5 minutes (retrySchedule). A transaction with many proofs no longer fails because the queue filled up.
  • Shielded wallet never synced on an empty chain (shielded 4.0.1). On a fresh devnet with no shielded outputs, isSynced never became true. It now reports synced after a single indexer query.
  • Coins and DUST released too early after a failed submit (facade 5.0.1). submitTransaction used to release every booking on any submission error, even when the transaction was already in a block, so the wallet offered spent coins until sync caught up. It now releases them only when the failure proves no block holds the transaction.
  • DUST projections sync stopping (dust-wallet 5.1.0). The sync no longer stops when a pass finds DUST it already applied.
  • Bad DUST snapshots retried forever (dust-wallet 5.1.0). Restoring a snapshot with out-of-range pendingDust values now fails with SnapshotRestoreError (invalid-shape) instead of restoring and throwing on every sync.

New​

  • dustWalletProbes(configuration) is exported from @midnightntwrk/wallet-sdk-dust-wallet, so a custom composition can start its DUST where DustWallet would, including at the ledger 9 boundary when skipLedgerV8DustHistory is set.
  • Capabilities exports classifySubmissionFailure, SubmissionFailure and Lifecycle.isCoveredBy.

Released packages​

PackageVersion
@midnightntwrk/wallet-sdk-dust-wallet5.1.0
@midnightntwrk/wallet-sdk-facade5.0.1
@midnightntwrk/wallet-sdk-capabilities4.0.1
@midnightntwrk/wallet-sdk-unshielded-wallet4.0.1
@midnightntwrk/wallet-sdk-shielded4.0.1
@midnightntwrk/wallet-sdk-address-format4.0.1
@midnightntwrk/wallet-sdk-prover-client2.0.1
@midnightntwrk/wallet-sdk-node-client2.0.1
@midnightntwrk/wallet-sdk-utilities1.3.1
@midnightntwrk/wallet-sdk-indexer-client2.0.1
@midnightntwrk/wallet-sdk-runtime2.0.1

Breaking changes or required actions​

None. This is a patch release; no migration is required from 2.0.0.


Known issues​

  • A fresh wallet on Preprod can take hours to sync DUST, because DustWallet replays the ledger 8 DUST history by default. Setting skipLedgerV8DustHistory skips it, but the boundary search can time out on a slow indexer connection and silently fall back to the full replay. Track it in servicedesk#319.