At a Glance

Latest News since the last Headline Digest centered on direct wallet payments, infrastructure reliability and safer application behavior. WebRTPay moved encrypted wallet-to-wallet delivery into a published developer package before BSV Browser and BSV Desktop carried the same live-payment direction into user-facing applications. Elsewhere, 1Sat Ordinals replaced a vulnerable marketplace contract, Go SDK and Wallet Toolbox releases corrected processing and notification failures, Teranode strengthened hashing and recovery behavior, and Go MessageBox Server addressed both privacy logging and purchase verification for custom handles.

Weekend Headlines

Developer Infrastructure Watch / Developer Tools

• SmartLedger-BSV 9.42.0 Adds Compact Covenant Scripts

Token Infrastructure Watch / Applications, Developer Tools

• 1Sat Ordinals Replaces OrdLock Contract After Security Review Finds Vulnerability

Payments Infrastructure / Developer Tools

• WebRTPay Publishes Experimental Package for Direct BSV Wallet Payments

Developer Tools

• BSV Go SDK v1.7.3 Fixes Excessive CPU Use in BEEF Transaction Processing

Developer Tools

• Go MessageBox Server v1.5.2 Reduces Identifying Data in Notification Logs

Wallets & Identity

• BSV Browser v1.8.0 Adds Live Payments Over WebRTC

Developer Tools

• Go Wallet Toolbox v0.191.1 Fixes Lost Transaction Status Notifications

Scaling & Teranode / Node Software

• Teranode v0.16.1-beta-4 Adds Hardware-Accelerated Hashing and Recovery Fixes

Wallets & Identity / Applications

• BSV Desktop v3.3.1 Releases Live Payments With Receive-Tab Controls

Developer Tools

• Go MessageBox Server v1.6.0 Adds Purchase Verification for Custom Handles

Editorial Summary

The clearest progression this week was the movement of direct wallet-to-wallet payments from reusable developer infrastructure into downloadable applications.

WebRTPay first appeared as an experimental package in the BSV TypeScript stack, carrying Atomic BEEF transaction data and BRC-29 derivation information through encrypted WebRTC connections between authenticated BRC-100 wallets. BSV Browser v1.8.0 then incorporated the approach into an Android application, attempting a live route to the recipient before offering MessageBox as a fallback. BSV Desktop v3.3.1 extended the same direction to Windows, macOS and Linux while narrowing incoming connections to the Receive tab and adding recipient-side transaction broadcasting.

That sequence is notable because the individual releases are no longer only about demonstrating WebRTC transport. Together they begin to define how a live payment behaves when the recipient is available, how an asynchronous route remains available when they are not, and how the receiving wallet communicates whether a transaction has actually entered its local state.

Several other releases focused on failure conditions that become important once infrastructure is operating continuously. Go Wallet Toolbox v0.191.1 corrected a case in which database updates could succeed before a later task failure caused the corresponding transaction-status notifications to be lost. The BSV Go SDK v1.7.3 addressed repeated ancestry processing in BEEF transaction packages that could drive excessive CPU use when transaction histories shared common ancestors.

Teranode v0.16.1-beta-4 continued the same operational theme at the node layer. The prerelease brought processor-assisted SHA-256 implementations into its validation dependency while adding recovery around several block-processing failures that could previously terminate the node process. It also made mined-status recording mandatory and corrected network-specific alert settings.

Application security and privacy formed another thread. 1Sat Ordinals publicly disclosed a vulnerability in the original OrdLock marketplace contract, canceled existing listings and moved continued selling to OrdLock v2. The replacement had already entered the public SDK before the disclosure, making the October announcement primarily an operational migration and security notice for users and integrating applications.

Go MessageBox Server v1.5.2 addressed a different form of exposure by removing identity keys, message identifiers and device-token fragments from several operational logs. The change does not eliminate all metadata or every remaining identifying log path, but it reduces unnecessary linkage between identity and message-delivery activity.

The week closed with Go MessageBox Server v1.6.0 adding purchase verification for custom handles, extending MessageBox infrastructure further into paid identity and naming workflows. Taken together with the WebRTPay, Browser and Desktop releases, the week shows wallet infrastructure becoming less about isolated send-and-receive functions and more about coordinated identity, delivery, payment, recovery and service-state handling.

Across the nine Latest News items, the common direction was therefore not a single new protocol feature. It was the strengthening of the layers around everyday application use: delivering payments directly when possible, recovering cleanly when something fails, limiting unnecessary identifying data, correcting resource-intensive processing and making higher-level payment and identity services more dependable.

→ Browse Latest News for all posts

Weekend Edition: October 25, 2026