What's in v1.4.2
Version 1.4.2 is a focused maintenance and polish release. It does not introduce major new features — those are tracked on the roadmap — but it addresses several performance issues and UI rough edges that have been accumulating since v1.4.0. If you are on any earlier version, we recommend updating.
The most impactful changes are under the hood: transaction broadcasting is now significantly faster for users with lower-bandwidth connections, and the node connection logic is more resilient when the initially selected node is unreachable or slow. These improvements directly affect how quickly your transactions appear on the network and how reliably the wallet stays in sync.
Performance
- Transaction broadcasting latency reduced by approximately 40% for users on constrained connections. The wallet now optimizes the encoding and submission pipeline before broadcasting to the node.
- Balance sync is now incremental rather than full-refresh on wallet open. Only UTXOs that have changed since last sync are fetched, reducing startup time for wallets with long transaction histories.
- Memory usage during address scanning reduced. The previous implementation loaded the full UTXO set into memory; the new approach uses streaming processing.
Node Connectivity
- Fallback node logic rewritten. If the primary node is unreachable at startup, the wallet now silently rotates to the next available node from the pool rather than displaying an error and requiring manual intervention.
- Node health checks are now periodic rather than one-time. If a connected node degrades during a session, the wallet detects this and reconnects automatically.
- Custom node configuration now persists correctly across restarts. A regression in v1.4.1 caused custom node settings to be overwritten on relaunch — this is resolved.
Send Screen Redesign
- The send screen has been redesigned with a clearer address input, larger amount field, and inline fee display. The fee is now shown in both KAS and the estimated USD equivalent (fetched from a public price feed; can be disabled in settings).
- Address validation now highlights errors inline rather than displaying a modal dialog.
- Paste-and-confirm flow improved: pasting an address from clipboard now triggers immediate validation and shows a preview of the address before submission.
- Send confirmation screen now displays the full transaction breakdown including outputs, fee, and total deducted from the sending address.
Bug Fixes
- Fixed: wallet occasionally showed incorrect balance after sending a transaction until next manual refresh. Balance now updates immediately after broadcast confirmation.
- Fixed: on Linux (AppImage), the wallet window occasionally failed to render on first launch after a cold boot. Root cause was a timing issue with the GPU compositor initialization.
- Fixed: transaction history pagination broke when the wallet had more than 500 transactions. Pagination now works correctly regardless of history length.
- Fixed: seed phrase display during wallet creation did not respect the system dark mode setting on macOS Sonoma in some configurations.
- Fixed: CSV export of transaction history omitted the fee column for outgoing transactions.
How to Update
Kaspa Wallet does not update automatically. To update to v1.4.2:
- Download the new version from the download page for your platform.
- Before uninstalling the previous version, confirm that you have a valid backup of your seed phrase and know your wallet password.
- Install the new version. Your wallet file from the previous version is not affected by the update.
- Open the new version and verify that your wallet opens correctly and shows the expected balance.
No migration required: v1.4.2 reads the same wallet file format as all previous v1.x releases. You do not need to re-enter your seed phrase or recreate your wallet to update.
Looking Ahead
The next major milestone on the roadmap is Ledger hardware wallet support, currently in development. Hardware wallet integration requires extensive testing across the full range of Ledger device firmware versions and Kaspa transaction types. We will publish a separate announcement when it is ready for a public beta.
Several other roadmap items are also in active development: address book functionality, multi-account support, and the foundations for KRC-20 token handling. Community contributions are welcome — see the GitHub repository for open issues tagged as good first contributions.
Thanks to everyone who reported bugs and tested pre-release builds. The quality improvements in v1.4.2 are a direct result of that community feedback.