Wallets & Identity / Developer Tools
In Brief
Go Wallet Toolbox now provides an optional way to keep a storage server’s main private key in a hardware security module—a device designed to protect keys while performing cryptographic work. Version 0.192.0 includes the integration, with hardware checks reported by the project; operators must build and configure a separate server to use it.
News Report
Go Wallet Toolbox 0.192.0 was published on November 17, 2026, at 23:13 UTC. Its main addition connects the toolbox’s wallet and storage-server components to Securosys hardware through the PKCS#11 interface.
The change concerns the server’s own root key: the main private key from which it derives other keys and produces signatures. In the new mode, that root key stays inside the hardware device rather than being loaded from the server’s usual private-key configuration.
Using the Key Without Exporting It
The integration supports key derivation and signing, including the wallet’s handling of payment inputs and change. It also checks the hardware-held identity at startup and when recovering a failed device session.
If a session fails, the next request attempts to establish a fresh session and verifies that the same identity is still present. The failed operation is not automatically replayed.
Hardware support is optional. The ordinary toolbox server continues to use software keys; the hardware-enabled server must be built separately from the repository and configured with the Securosys provider, key details and a PIN file. Updating the toolbox alone does not enable it.
Hardware Checks and Remaining Limits
The project reports successful checks on November 17 using Securosys’s remote Grimsel developer HSM. These covered signatures, key derivation, identity verification and recovery after session failures. The release workflow also completed successfully.
The protection has a defined scope. Some intermediate cryptographic material still passes through application memory, with temporary buffers wiped by the implementation. A specialized BRC-69 operation for proving a relationship between keys remains unsupported in hardware mode.
The remote-hardware benchmark also showed capacity limits. Increasing simultaneous clients from four to eight increased waiting without improving throughput. That small test measured cryptographic request-and-response work, excluding HTTP handling, database operations and transaction signing. It does not establish production payment capacity.
BSV TIMES Read
For a storage-service operator, separating the signing identity from ordinary application memory can reduce exposure of the root key. The recovery checks address another practical requirement: reconnecting to hardware must preserve the service’s identity. The release gives operators a concrete integration to evaluate against their own security needs and workload.
Developer Context
GitHub contributor sirdeggen, whose public profile lists the BSV Association, authored the integration. His recent work also includes the Wallet Relay QR pairing correction released in version 0.8.0.
Source Links
- Go Wallet Toolbox — Version 0.192.0 release
- Go Wallet Toolbox PR #1097 — Hardware key derivation, signing and validation
- Version 0.192.0 HSM documentation — Setup, security limits and hardware measurements
- Go Wallet Toolbox — Successful release workflow
- sirdeggen — Public developer profile
- TS Stack PR #1590 — Related Wallet Relay contribution
Posted on November 18, 2026 (UTC)

Leave a Reply