Rusty Kaspa v1.1.0 RC2 was a focused corrective pre-release published on January 20, 2026. It fixed fresh-node UTXO-index initialization after UTXO-set download, reverted a problematic WASM build configuration, ran Docker containers as an unprivileged user, and added a pruning-proof descriptor, while preserving the need for careful candidate testing.

Key takeaways

• RC2 remained a pre-release; it was not the final v1.1.0 package.
• The urgent operator issue concerned nodes freshly synchronized on RC1 with --utxoindex enabled.
• The official release included a three-stage recovery procedure for affected RC1 nodes.
• RC2 also addressed release-build WASM errors, changed Docker containers to an unprivileged user, and added guided pruning-proof reconstruction data.
• The small changelog demonstrates the purpose of release candidates: find integration defects before a stable rollout.

What changed in Rusty Kaspa v1.1.0 RC2?

The official Rusty Kaspa v1.1.0 RC2 release lists five merged changes between RC1 and RC2. The principal fix was proper UTXO-index resynchronization after a UTXO-set download. Other entries ran Docker images as the kaspa user, reverted a WASM build configuration, added a pruning-proof descriptor for guided reconstruction, and bumped the version.

GitHub identifies the tag as v1.1.0-rc.2, the node version as the same string, and the package as a pre-release. That explicit status should govern deployment decisions even when a fix addresses a serious problem.

What was wrong with the fresh-node UTXO index?

The supporting PR #827 explains the lifecycle issue. After a node downloaded a new UTXO set, the earlier version did not automatically trigger resynchronization of the optional UTXO index. Older software had initiated the index update when a new consensus instance was committed, but newer flow committed consensus before downloading the UTXO set.

That ordering change left the auxiliary index at risk of not reflecting the downloaded state on a freshly synchronized RC1 node. The patch adds the missing trigger after the download path. It changed 16 lines across two files according to GitHub, which is a reminder that operational impact is not proportional to diff size.

An index problem is not automatically evidence that consensus accepted invalid blocks. It concerns a derived lookup structure used by node services. Even so, applications relying on indexed UTXO queries could receive incomplete or inconsistent results, so the recovery instruction mattered.

What recovery procedure did the release provide?

For a node freshly synchronized on RC1 with --utxoindex enabled, the release says to stop the node, restart without --utxoindex, and let it fully synchronize and advance normally. Then stop it again and restart with --utxoindex enabled.

Operators should preserve logs, command-line configuration, database backups appropriate to their environment, and monitoring evidence before remediation. Confirm current virtual state and RPC health after the non-indexed run, then allow the rebuilt index to complete before reconnecting dependent services.

Do not apply this historical sequence blindly to a later release. The correct action depends on the installed binary and database state; current release notes take precedence.

Why did RC2 revert part of the WASM build configuration?

PR #830 says changes introduced by an earlier WASM update produced runtime bugs in release builds, likely involving the new optimization configuration. Rather than delay the release line, maintainers reverted the configuration while improving the developer workflow for building from the wasm directory.

The PR includes a Node.js resolver test and the runtime error that should no longer appear. This is relevant to browser and Node.js integrators because successful compilation alone does not prove a generated WASM bundle works at runtime. Candidate validation should exercise actual connection, resolver, wallet, and serialization flows in the target JavaScript environment.

What did the Docker and pruning changes add?

PR #824 changed official container execution to an unprivileged kaspa user. Running a network service without root privileges narrows the impact of a process compromise, although operators must still set volume ownership, network exposure, secrets, and runtime capabilities correctly.

PR #828 added a pruning-proof descriptor for guided proof reconstruction. The release title establishes its purpose but does not provide a user-facing benchmark or migration promise. It belongs to the same broader effort to make pruning-proof creation and synchronization more efficient; operators should judge it through release behavior rather than infer performance from the PR name alone.

How should integrators have validated RC2?

Node operators needed two test paths: a clean RC2 synchronization with the UTXO index enabled, and an upgrade or recovery from representative RC1 data. Compare index query results with direct node state, let the node advance beyond the downloaded snapshot, and test restart behavior.

WASM consumers should rebuild release artifacts from a clean workspace and run the published JavaScript examples plus their own production calls. Container users should confirm the non-root process can read configuration, write database and log volumes, bind the intended ports, and stop cleanly.

Because RC2 was not final, maintain rollback and do not mix binaries behind a service endpoint without version-aware monitoring.

How did this candidate relate to the wider roadmap?

RC2 was maintenance on the v1.1.0 node line, not activation of Kaspa’s later programmable-transaction roadmap. Work on verification primitives was occurring in parallel; Kaspa Groth16 Verification explains why reference code did not equal immediate mainnet availability.

Similarly, reliable price feeds and on-chain verification solve different problems. The Kaspa oracle research overview covers the external-data boundary. Neither research track turns a corrective node release into a KAS price forecast.

What were the limits of RC2 evidence?

The release proves that fixes were packaged and links their reviews. It does not publish fleet-scale uptime data, independent security audits, a cross-platform performance study, or counts of affected RC1 nodes. It also cannot prove that every third-party wallet, pool, explorer, or container deployment was compatible.

RC2 should therefore be read as a concrete corrective milestone with a documented recovery path, not as proof that the entire v1.1.0 line was already stable.

Frequently asked questions

Did all RC1 nodes need the UTXO-index recovery procedure?

The release specifically addresses nodes freshly synchronized on RC1 with --utxoindex enabled. Other installations should be diagnosed from their version, flags, state, and official guidance.

Did RC2 require deleting the node database?

The published procedure does not instruct operators to delete it. It tells them to synchronize without the index and then restart with the index enabled.

Was the WASM fix a new feature?

No. The cited PR reverted a problematic build configuration to restore release-runtime behavior and reduce risk to the upcoming release.

Did RC2 change Kaspa issuance or guarantee price appreciation?

No such change or guarantee appears in the release note. It was a node-software candidate focused on correctness and packaging.

Source and verification note

This article is based on the official v1.1.0 RC2 release note, published January 20, 2026. Root-cause and scope statements were checked against merged Rusty Kaspa PR #827, PR #830, PR #824, and PR #828. The source supplies no affected-node count or independent benchmark.