At a Glance

Latest News since the last Headline Digest concentrated on payment reliability, wallet interoperability and operational resilience. Tabellarius moved radio payments into a signed public firmware release; Teranode published two successive betas addressing mining, validation, connectivity and chain recovery; wallet and SDK projects corrected verification, registration, broadcasting and spendability-reporting problems; and ProjectBabbage opened a public interoperability laboratory with reproducible wallet tests. A community transaction test also produced a confirmed BSV Blockchain block containing more than 5.37 million transactions.

Weekend Headlines

Developer Tools / Payments Infrastructure

• Tabellarius Publishes First Signed Radio-Payment Firmware Release on BSV Blockchain

Scaling & Teranode / Node Software

• Teranode v0.16.1 Beta 5 Fixes Mining and Policy Validation

Enterprise / Developer Tools

• Digital Product Passport Project Merges Wallet-Signed Publisher Registration

Developer Tools / Payments Infrastructure

• BSV Python SDK Merges Fix for Skipped BEEF V1 Proof Checks

Payments Infrastructure / Developer Tools

• BSV Broadcaster Adds Live Receipts for Submitted Payments

Wallets & Identity / Developer Tools

• BSV Desktop Merges Security Protections for Application-Manifest Requests

Wallets & Identity / Payments Infrastructure

• BSV Wallet Backend Adds Recovery for Interrupted Registration Payments

Developer Tools / Wallets & Identity

• BSV Wallet Toolbox 2.15.3 Fixes Rejection of Some Confirmed Payments

Developer Tools / Network & Protocol

• ProjectBabbage Opens Public Interoperability Lab With First BSV Blockchain Wallet Test Results

Network & Protocol / Scaling & Teranode

• BSV Blockchain Community Test Produces 5.37-Million-Transaction Block

Scaling & Teranode / Node Software

• Teranode v0.16.1 Beta 7 Fixes Connection Failures and Improves Chain Recovery

Developer Tools / Wallets & Identity

• BSV Go SDK v1.7.4 Fixes How Wallets Report Funds Available to Spend

Editorial Summary

Payment reliability formed the strongest thread across this edition, beginning at two very different edges of the network. Tabellarius published its first signed beta firmware for sending BSV payments through compatible radio hardware, with initial distribution limited to Europe. At the conventional network layer, BSV Broadcaster v0.20.0 added an earlier RECEIVED status so a wallet can distinguish a payment recorded by the broadcaster from later network acceptance and mining. The same release improved handling when one unmined payment spends change from another and added further recovery around transaction status after blockchain reorganizations.

Several wallet and SDK updates dealt with a related problem: making sure valid transaction information is neither accepted too easily nor rejected for the wrong reason. The Python SDK merged a repair for BEEF V1 verification after BSV TIMES reproduced a case in which the published package could return success without checking a supplied Merkle proof against a block header. Wallet Toolbox 2.15.3 addressed the opposite failure, where unrelated records inside an Atomic BEEF package could cause an otherwise valid confirmed payment to be rejected before the wallet’s cleanup process ran.

The Wallet Authentication Backend added recovery for another uncertain payment state: a newcomer’s starter payment could already exist even though an interrupted response left registration unfinished. Version 1.8.18 can locate, verify and reuse that original transaction rather than allocating another payment or forcing the registration to restart. The update has passed staging checks, while production deployment remains an operator decision.

BSV Go SDK v1.7.4 extended the interoperability theme into wallet-to-application data itself. The release fixes a binary-format problem that could turn a wallet’s “not spendable” output status into an apparently spendable one when read by an application. It also aligns message authentication with shared BRC conventions, tightens Atomic BEEF checks and rejects several malformed or oversized values rather than silently changing their meaning.

BSV Desktop addressed security at a different boundary. Its merged manifest-fetching protections restrict external applications from directing the wallet toward private or reserved network addresses, require HTTPS, block redirects and limit response size. The change is confirmed in source, although its inclusion in the latest downloadable desktop release had not yet been established when BSV TIMES reported it.

ProjectBabbage then moved interoperability testing from individual fixes toward a shared public process. Its Transaction Processing Network Interoperability Laboratory provides executable tests, defined environments and retained evidence for examining how independently developed wallets, applications, storage systems and transaction services behave together. Initial experiments with Yours Wallet 5.1.0 produced successful results in several workflow groups while also recording unmet expectations and blocked tests, making the project a testing framework rather than a blanket product certification.

Teranode development progressed through two releases during the same period. Beta 5 corrected mining-candidate handling, improved the distinction between policy rejection and transaction invalidity and applied an existing finality rule consistently enough that the project called for coordinated upgrades. Beta 7 later fixed a networking-resource leak that could stop nodes accepting new connections after two to four weeks, improved transaction-state recovery during chain reorganizations and changed how nodes handle new unmined transactions while catching up on missing blocks.

The week also produced a directly inspectable mainnet scale result. A community-organized transaction test generated block #973563 with 5,374,368 confirmed transactions, while BSV Intel recorded more than 47 million transactions across a wider approximately 22.5-hour observation window. The confirmed block establishes a substantial real mainnet result, while participant-reported broadcasting rates remain distinct from independently measured sustainable network-wide throughput.

Beyond payments and nodes, the Digital Product Passport reference project added wallet-signed publisher registration, allowing an application to request admission to an index using its own signing key while leaving the operator in control of approval and revocation. The feature is merged in source but had not yet reached the published package or hosted reference index at the time of reporting.

Across these developments, the strongest common direction is correct handling of state across independently operated components. A wallet needs to know whether funds are actually spendable; a receiver needs to verify proof data without rejecting legitimate payments; a broadcaster needs to distinguish receipt, network acceptance and mining; a node needs to recover when connections or blockchain branches change; and applications need a reproducible way to test whether those separate implementations work together. This week’s Latest News moved repeatedly through those boundaries, where dependable infrastructure depends as much on preserving the meaning of information as on moving transactions quickly.

→ Browse Latest News for all posts

Weekend Edition: November 8, 2026