Wallets & Identity / Developer Tools

In Brief

Wallet Toolbox 2.16.0, published on November 13 (UTC), expands the tools available to developers for restoring wallet records and moving them between compatible storage providers. Wallet users gain access to these improvements as their wallet providers integrate and test the release.

News Report

The update is available in the core, browser-client and mobile packages. For someone replacing a device or changing storage providers, the practical aim is to preserve the information their wallet needs to recognize and use its funds.

Why Wallet Records Matter

In the Wallet Toolbox model, recovery needs both access to the user’s keys and the records associated with their funds. Those records can include information needed to identify and spend particular payments, alongside transaction history, labels and certificates. Keeping a recovery key alone does not preserve all of that information; an encrypted data backup does not replace the key either.

What the Update Adds

Version 2.16.0 extends existing encrypted-backup support with interfaces that process archives in pieces, reducing the need to hold a complete archive in memory. New recovery paths check imported data in a separate, inactive wallet profile before that profile can be selected for use. Importing a file does not automatically make the restored copy the active wallet.

For compatible storage providers, the release also adds a coordinated handoff. Most records can be copied while the original provider remains active. The final switch checks that the destination has received the latest records before activating it. Wallet writes can pause briefly during this final step, and all participating providers need compatible support.

The update also introduces a device-backup controller to help applications manage copying when an app runs, pauses or resumes. Applications still have to supply and manage that integration; installing the package does not automatically start a backup service.

Evidence and Availability

The project’s merged change reports successful tests using Metanet Client desktop on TTN, a test network. These included a payment, checks of wallet records and certificates, device-backup synchronization and a restart with the controlled data preserved.

That evidence covers the tested setup. The implementation map still identifies Windows-specific native recovery components as awaiting platform validation. Some bundled documentation also retains older candidate or unpublished wording, although npm records and the completed release process confirm publication of version 2.16.0.

BSV TIMES Read

The useful outcome is a wallet that can reopen with the right records and still authorize payments after a device or storage-provider change. This release supplies more of the code needed for that process. Its practical reach depends on wallet providers turning those components into a complete, tested recovery experience that users can understand and carry out.

Developer Context

Ty Everett authored the main synchronization and portable-recovery change, PR #569. He also coauthored BRC-100 with Tone Engel and Brayden Langley, defining the standard interface through which BSV applications communicate with wallets.

Source Links

• Wallet Toolbox 2.16.0 — npm package records: core, browser client, mobile
• Wallet interoperability — merged synchronization and recovery change, PR #569
• Wallet synchronization and portability — implementation map at the published source revision
• Storage-provider handoff — behavior and compatibility requirements at the published source revision
• TS Stack — completed package release workflow
• Wallet backup and recovery — keys, wallet records and product responsibilities
• BRC-100 — wallet-to-application interface and authors

Posted on November 14, 2026 (UTC)