Mobile Infrastructure Watch / Developer Tools
In Brief
BSV Association has released BSV Browser 1.6.0 for iOS with a new YubiKey-backed Vault, encrypted server-assisted recovery for wallet metadata, and a redesigned wallet experience. The App Store says metadata caching is enabled by default but can be disabled in Settings. Version 1.6.1 followed on September 11 with bug fixes and performance improvements. The new recovery capability addresses an important limitation of key-only wallet restoration, although BSV Browser’s existing public support documentation has not yet been updated to explain the cache server, what metadata it stores, or how the new recovery path changes earlier guidance that wallet state remains only on the device. (App Store)
News Report
BSV Association has released a substantial update to BSV Browser, adding hardware-assisted key protection and a new encrypted recovery mechanism for wallet metadata.
Apple’s App Store identifies version 1.6.0 as introducing three principal changes: a new Vault for YubiKey 5C-class devices, the ability to push wallet metadata to and recover it from an encrypted cache server, and an overhaul of the wallet user experience. The release notes specify that the metadata-recovery service is enabled by default and can be disabled in Settings. (App Store)
Version 1.6.1 followed on September 11 with bug fixes and performance improvements, making it the current iOS release at the time of the BSV TIMES check. (App Store)
The update is notable because both additions address different parts of a broader wallet-recovery problem.
BSV Browser is a self-custodial mobile browser and wallet built around the BRC-100 application-to-wallet interface. Compatible applications can request payments, signatures, encryption operations and identity functions through the wallet, while the browser maintains the transaction and metadata state needed to make those capabilities usable over time. (BSV Browser)
Holding the root key is therefore only one part of recovering the complete wallet.
Recovering More Than the Root Key
BSV Browser’s existing support documentation makes that distinction explicitly.
A 12-word recovery phrase can restore the wallet’s root key. However, the documentation says there is no chain-scanning or derivation process that can reconstruct all of the wallet’s transaction history, UTXOs and certificates from that phrase alone.
Until now, the documented method for preserving that additional state has been to export the complete wallet database manually and keep a separate backup copy. (BSV Browser)
Version 1.6.0 introduces another path.
According to the App Store release notes, BSV Browser can now push wallet metadata to an encrypted cache server and recover that metadata later. The feature is enabled by default, with an option to turn it off in Settings. (App Store)
That potentially reduces one of the practical weaknesses of local-only wallet state: a user who securely retains the cryptographic key but loses the phone may otherwise discover that the key alone does not reproduce the complete operational wallet.
The release notes do not currently specify the full contents of the cached metadata, the server operator, retention policy, encryption-key architecture or precise recovery sequence.
They do, however, explicitly describe the material sent to the server as encrypted wallet metadata, rather than indicating that the server receives custody of the wallet’s root private key.
That distinction should remain clear until fuller technical documentation is published.
A Hardware-Backed Vault
Version 1.6.0 also introduces a Vault feature for YubiKey 5C-class hardware.
The App Store describes the Vault as allowing encryption keys to be held on an external hardware device. This adds a physical security boundary between ordinary wallet operation on the phone and key material protected by compatible YubiKey hardware. (App Store)
Hardware-backed key handling is increasingly visible elsewhere in BSV Association’s developing mobile-wallet architecture. Its separate public bsv-wallet project also includes an optional YubiKey-secured Vault and native mobile interfaces for hardware-backed operations, although that project remains under development and should not be treated as the same released application. (GitHub)
For BSV Browser specifically, the App Store release is the important threshold: the Vault is no longer merely visible in experimental wallet development but is now named as part of a distributed BSV Browser release.
Existing Documentation Has Not Yet Caught Up
The new encrypted cache mechanism also creates a documentation issue that is worth distinguishing from the technical release itself.
BSV Browser’s currently indexed support guide still tells users that their keys and transaction data are stored on the device only. Its recovery section says that a manually exported wallet database is the only way to restore transaction history, UTXOs and certificate data after loss of local wallet state. (BSV Browser)
Those statements describe the earlier architecture.
Version 1.6.0 now explicitly says that wallet metadata can be pushed to an encrypted cache server and that this feature is enabled by default. (App Store)
That does not establish that the new design compromises self-custody, nor does it show that unencrypted wallet information or private keys are being transmitted.
It does mean that users now need updated documentation explaining what leaves the device, how it is encrypted, who operates the cache service, what is needed to decrypt recovered metadata, how long the service retains it, and exactly what disabling the feature changes.
Those details become particularly important because the feature is default-on rather than opt-in.
iOS Confirmed, Android Not Yet
The new release is currently confirmed through Apple’s App Store.
The Google Play listing available during the September 11 check still reports an August 1, 2026 update date and does not expose the 1.6.0 or 1.6.1 release notes. BSV TIMES therefore does not yet treat the same rollout as confirmed on Android. (Google Play)
The public BSV Browser repository continues to describe the application as supporting both iOS and Android and implements the BRC-100 wallet interface through its integrated self-custodial wallet architecture. (GitHub)
BSV TIMES Read
The important change in BSV Browser 1.6.0 is not simply the addition of another security setting.
It begins separating two problems that are often treated as if they were the same.
Key recovery answers: can the user recover control of the cryptographic keys?
Wallet-state recovery answers: can the user reconstruct the information needed to understand and operate everything associated with those keys?
BSV Browser’s own earlier documentation makes clear that the first did not automatically provide the second. A mnemonic could restore a root key while transaction history, UTXOs, certificates and other wallet state still depended on a separately preserved database.
An encrypted metadata cache attempts to close that operational gap.
At the same time, moving any wallet state from a purely local device to a server introduces a different infrastructure relationship, even where the information is encrypted. Encryption can protect content, but users still need to understand what is being stored, the service on which recovery depends and what information may remain observable outside the encrypted payload.
The YubiKey Vault moves in the opposite physical direction: particularly sensitive key operations can be separated from the phone and placed behind dedicated hardware.
Taken together, those changes show BSV Browser becoming a more complete wallet system rather than simply a browser with payment capabilities.
The next step should be documentation that makes the boundaries equally clear: which keys remain solely under the user’s control, what metadata is recoverable through the server, what the server can observe, and how a user can choose a completely local configuration if preferred.
For infrastructure intended to carry payments, identity and application permissions in one environment, those boundaries are as important as the new capabilities themselves.
Source Links
BSV Browser — Support & User Guide
Posted on September 11, 2026
Leave a comment