BSV Desktop Version 3 Adds Wallet Profiles, Drops WAB Login and Built-In STAS Support

Wallet Watch | Applications

In Brief

BSV Desktop’s latest downloadable release, v3.1.1, was published on October 11, with builds for Windows, macOS and Linux.
Version 3 introduces a redesigned interface, separate wallet profiles and recovery-phrase backup shares.
Phone-and-password WAB login and built-in STAS handling are no longer supported. Existing users need to check the migration guidance before upgrading.
The latest patch fixes counterparty approval requests that could remain pending indefinitely.

News Report

BSV Desktop has moved into its version 3 release series, combining changes to its wallet interface and recovery tools with significant changes to supported login methods and token handling.

The project is an Electron-based desktop wallet and BRC-100 reference implementation for the BSV Blockchain ecosystem. Its latest release, v3.1.1, follows v3.0.3 earlier on October 11. The broader redesign and profile features belong to the version 3 transition; they were not all introduced by the final patch.

Existing users face different upgrade paths

The release guidance distinguishes between wallets accessed through a self-managed recovery phrase or private key and wallets using phone-and-password WAB login.

For the former, the project says an existing saved wallet should retain its identity and funds after updating. Restoring a BSV Desktop 2 wallet on another device supports its 24-word phrase or 64-character hexadecimal private key.

WAB users are told to remain on version 2. Version 3 does not support that login or recovery route. The documented migration option is to keep version 2 available, create a new version 3 wallet and transfer funds from the old wallet.

The project also calls for an offline backup of the recovery material and recommends moving funds out before updating to reduce migration risk.

Profiles and backup shares have defined limits

Modern recovery-phrase wallets can now maintain multiple, renameable profiles. Each profile has a separate identity, local database and application permissions, while sharing the same underlying recovery phrase.

This gives users a way to separate wallet activity without maintaining an entirely different phrase for each identity.

Recovery on a new device has a limitation: importing the phrase initially restores only the Default profile. Additional profiles must be recreated in their original order to recover the same identities. This does not restore their previous local history.

The backup-share implementation splits a 12-word recovery phrase into three shares, with any two sufficient to reconstruct it.

These features do not apply universally to imported wallets. The version 3 import screen explicitly says wallets restored using the BSV Desktop 2 key scheme do not receive wallet profiles or backup shares.

Token handling moves outside the core wallet

Version 3 removes the wallet’s built-in ability to display, send or receive STAS tokens.

The stated direction is for dedicated applications to handle token operations through a wallet permission module. That STAS replacement is described as future work, so the release does not provide an equivalent built-in migration destination.

The project advises STAS holders to remain on version 2, or use it to transfer their tokens to a supporting wallet or application before upgrading.

The latest patch repairs stalled approval requests

The v3.1.1 source history includes a fix for counterparty permission dialogs that were not being displayed. Requests could consequently remain queued, preventing wallet locking or profile switching.

The fix mounts the missing dialog handler, accommodates the relevant request formats and corrects how grouped approval decisions are passed back to the wallet.

Separately, the merged version 3 work changes the default for application signing approvals. The new default applies to fresh installations and users who have never saved Advanced Settings; previously saved settings retain their stored value.

Troubleshooting and wallet-data export also change

A new help area provides a guided tour and troubleshooting workflow covering connections, transactions, coin records, incoming payments and backup status.

Troubleshooting can perform repairs, including retrying failed transactions and processing waiting incoming payments. It is more than a status display.

The merged work also fixes wallet-data exports that failed validation because locally stored timestamps used different formats.

BSV TIMES Read

The release gives BSV Desktop a clearer role as a wallet for identities, permissions and application payments. Profiles make that separation more practical, while the token changes move more responsibility into specialized applications.

The immediate issue for existing users is compatibility. A modern phrase wallet, a legacy BSV Desktop 2 wallet, a WAB wallet and a wallet holding STAS tokens do not have the same upgrade path.

For the BSV Community, this is a material application release. Its value should be assessed alongside the recovery limits and the token functionality still to come.

Developer Context

Deggen — GitHub: sirdeggen

Deggen authored the merged wallet-profile and troubleshooting changes. The release history also attributes the counterparty-permission fix to him.

His public GitHub profile lists BSV Association and features BSV Desktop, BSV Browser and the BSV TypeScript stack among its pinned projects.

Source Links

Posted on October 12, 2026