Wallet Infrastructure Watch / Developer Tools
In Brief
BSV Wallet Toolbox 2.11.0 has been published as the latest npm release of BSV Association’s BRC-100 reference wallet package. The TypeScript toolkit connects BRC-100 application calls with persistent wallet storage, transaction construction and signing, protocol-derived keys, permissions, chain tracking and transaction monitoring. The public package documentation now describes an increasingly production-oriented wallet infrastructure layer spanning server, browser and mobile environments, although npm does not currently provide a concise 2.11.0-only changelog from which every documented capability can be attributed specifically to this release. (npm)
News Report
A new release of the BSV Wallet Toolbox has been published to npm, advancing the principal TypeScript implementation used to connect applications with the BRC-100 wallet interface.
Version 2.11.0 was published September 6 and is now marked as the package’s latest release. The preceding 2.10.4 release was published nine days earlier. (npm)
Wallet Toolbox is maintained inside BSV Association’s consolidated TypeScript Stack, or ts-stack, and describes itself as the reference implementation of BRC-100.
Rather than being an end-user wallet application by itself, the package supplies the infrastructure that wallet applications and services can use to implement the BRC-100 interface consistently. It connects application-facing wallet operations to storage systems, cryptographic key management, network services, transaction construction, signing and lifecycle monitoring. (npm)
Its current wallet implementation includes BRC-100 action creation and signing, certificate management, identity discovery and output tracking.
The storage layer supports several operating environments, including SQLite and MySQL through Knex, IndexedDB for browser-oriented use and remote wallet-storage services. That allows the same higher-level wallet model to operate across local, browser and server-backed architectures rather than requiring each application to recreate its own storage logic. (npm)
The network-services layer connects wallet activity with transaction broadcasting, ChainTracks-based chain tracking, Merkle-proof verification and UTXO lookups. A separate monitor manages pending transaction states, rebroadcast attempts, proof acquisition and chain reorganizations in the background. (npm)
Wallet Toolbox also implements protocol-derived key management based on BRC-42 and BRC-43 and provides an application-permission manager for controlling access on a per-application and per-protocol basis.
Together, those capabilities make the package more than a library for constructing payments. It provides much of the operating infrastructure needed when a BRC-100 application asks a wallet to create transactions, use identity keys, disclose certificates, encrypt information or manage application-specific outputs.
Storage and Transaction Reliability
The current package documentation places significant emphasis on wallet-state reliability.
Storage replication applies each received synchronization page and its corresponding durable checkpoint inside the same provider transaction. If processing a page fails, the page is rolled back without advancing the checkpoint. This is intended to prevent a wallet from recording that synchronization has progressed beyond data it has actually stored. (npm)
Output queries also return the complete number of matching outputs alongside each page of results, including when the requested page falls at or beyond the end of the result set.
The transaction interface preserves BRC-100 compatibility across ordinary JSON application bridges by returning completed createAction and signAction Atomic BEEF data as numeric arrays, while binary transports can continue using Uint8Array. (npm)
For transactions entering a wallet, internalizeAction accepts BRC-95 Atomic BEEF and can restrict larger legacy BEEF envelopes to the declared transaction and the dependencies actually required for validation. The wallet then independently validates the relevant transaction data, proofs and BRC-29 payment outputs. (npm)
These functions are increasingly important as BRC-100 wallets interact with applications that create more complex transactions than conventional address-to-address payments.
Permissions Without Blocking the Application
Another current Wallet Toolbox behavior concerns persistent application permissions.
When an application receives a durable permission grant, the internal transaction representing that permission can be queued for delayed broadcast rather than forcing the application to wait for network broadcast before approval completes.
The wallet’s funding logic prefers already settled change and uses queued permission ancestry only when necessary. The goal is to keep application interaction responsive without treating funds involved in pending permission transactions as if they had disappeared from the wallet. (npm)
This fits the broader BRC-100 model in which permissions are not merely browser-interface settings. They can control access to particular wallet functions, protocols and identity capabilities across applications.
Supporting Different Wallet Environments
The Wallet Toolbox project is divided into three package targets.
The full @bsv/wallet-toolbox package provides the complete storage and service environment. Separate browser and mobile distributions remove platform-specific dependencies that do not belong in those runtimes. (npm)
At the time of the September 6 check, the separate mobile package remained at version 2.10.4, published eight days earlier. It provides a mobile-safe implementation for React Native, Capacitor, Cordova and compatible environments, including Wallet, WalletSigner, Services, Monitor, permission management and remote storage without Node-specific database bindings. (npm)
The 2.11.0 publication should therefore be understood specifically as the current release of the core Wallet Toolbox package, rather than evidence that every companion distribution has simultaneously moved to the same version.
The npm documentation also identifies BSV Desktop and BSV Browser as BSV Association reference applications built around the BRC-100 interface, while independent applications can implement the same interface with their own packaging and service choices. (npm)
That distinction is central to the purpose of Wallet Toolbox: BRC-100 is intended to provide a common application-facing wallet boundary without requiring every BSV application to use one particular end-user wallet.
Release Scope
The current npm documentation contains a large amount of recently developed functionality, including wallet storage and synchronization controls, managed change, transaction monitoring, local ChainTracks integration, proof handling, mobile packaging and testing infrastructure.
However, the public npm version page does not currently expose a concise 2.11.0 release note identifying every change introduced specifically between versions 2.10.4 and 2.11.0.
BSV TIMES therefore treats the September 6 publication itself as the confirmed release milestone and does not attribute the complete current feature set uniquely to version 2.11.0.
What can be established directly is that 2.11.0 has replaced 2.10.4 as npm’s current latest package and that Wallet Toolbox continues to serve as the BRC-100 reference implementation for connecting wallet applications with storage, signing, network and permission infrastructure. (npm)
BSV TIMES Read
Wallet infrastructure tends to become less visible as it becomes more useful.
An application developer should not have to solve transaction storage, key derivation, proof tracking, synchronization, permissions and network recovery independently merely to ask a wallet to perform an action.
That is the role the BRC-100 interface and Wallet Toolbox increasingly divide between them.
BRC-100 provides the common language applications use to communicate with compatible wallets. Wallet Toolbox provides a substantial reference implementation beneath that interface, connecting those requests to the less visible systems required to make a functioning wallet dependable over time.
The distinction also matters for interoperability.
If different wallets can expose the same application interface while choosing different storage providers, transaction services, user interfaces and operating environments, applications become less tightly coupled to one wallet product. The wallet remains responsible for keys and authorization while the application can concentrate on its own function.
Version 2.11.0 is not, from the public information currently available, a reason to claim that every part of that architecture has suddenly changed. Its importance is more incremental: the principal BRC-100 reference implementation continues to mature as a maintained software package rather than remaining only a specification.
For infrastructure intended to support applications over long periods, that continuing implementation work is as important as adding new protocol documents.
Source Links
BSV Wallet Toolbox — npm package
BSV Wallet Toolbox Mobile — npm package
BRC-100 — Unified Wallet-to-Application Interface
Posted on September 6, 2026
Leave a comment