At a Glance

This week’s Latest News concentrated on wallet reliability, developer correctness and payment infrastructure. BSV Desktop moved into version 3 with wallet profiles and new recovery tools while ending WAB login and built-in STAS support; Wallet Toolbox 2.14.9 corrected duplicate receipt accounting in SQL-backed wallets; SmartLedger-BSV aligned a signature-hash edge case with node behavior; and Go Wallet Toolbox introduced a merchant point-of-sale gateway with cashier separation, signed invoices and payment-recovery handling. BSV TIMES

Weekend Headlines

• Wallet Watch / Applications
  BSV Desktop Version 3 Adds Wallet Profiles, Drops WAB Login and Built-In STAS Support
• Wallet Infrastructure Watch / Developer Tools
  BSV Wallet Toolbox 2.14.9 Adds Duplicate-Receipt Protection for SQL Wallet Storage
• Developer Infrastructure Watch / Developer Tools
  SmartLedger-BSV Corrects Chronicle Signature Hashing in New Library Releases
• Payments Infrastructure Watch / Payments Infrastructure
  Go Wallet Toolbox v0.191.0 Adds Merchant Point-of-Sale Gateway

Editorial Summary

The week opened with a material BSV Desktop transition. Version 3 adds separate wallet profiles, recovery-phrase backup shares and new troubleshooting tools, but it also creates clear migration boundaries. Phone-and-password WAB wallets remain on version 2, built-in STAS support has been removed, and recovery behavior differs between modern phrase wallets and earlier wallet formats. The result is a more defined application-wallet direction, accompanied by upgrade decisions that existing users need to understand before moving forward. BSV TIMES

Wallet Toolbox 2.14.9 addressed a different reliability problem: multiple storage instances processing the same received transaction at nearly the same time could record one output twice in the recipient’s SQL-backed wallet balance. The correction coordinates receipt processing through a database-backed claim and also fixes a case in which the actual broadcast result could be lost from the response. Importantly, the reported duplicate was an accounting error in wallet storage, not the creation of additional funds on BSV Blockchain. BSV TIMES

SmartLedger-BSV’s three library releases moved the week further down into byte-level correctness. The principal change aligns signature-hash calculation for certain incomplete script encodings with the original-algorithm behavior used by SV Node, including when selected through Chronicle. Follow-up releases add an optional stricter message-signature check and a warning when an application changes a script object without updating the bytes that will actually be serialized. The changes do not alter BSV Blockchain consensus rules; they strengthen agreement between application behavior and the underlying cryptographic data being signed or transmitted. BSV TIMES

The week closed by moving from wallet internals into merchant operations. Go Wallet Toolbox v0.191.0 adds a point-of-sale gateway in which approved cashiers can request invoices and relay customer payments without receiving the merchant’s private key. The gateway checks the intended output and amount, issues signed invoices and receipts, preserves submitted transactions for interrupted-payment recovery and provides a dedicated container release. It is a concrete building block for merchant payment systems, while actual retail deployment still requires the operator’s wallet, persistent storage, blockchain connectivity and broader service setup. BSV TIMES

Taken together, the week was less about introducing entirely new protocol concepts than about making application infrastructure more dependable at the boundaries where mistakes matter: recovering wallets, recording payments once, signing the exact intended bytes and operating a merchant checkout without distributing the merchant’s signing key.

→ Browse Latest News for all posts

Weekend Edition: October 18, 2026