Scaling & Teranode / Node Software

In Brief

Teranode’s latest beta fixes a bug that could stop a node accepting new network connections after weeks of operation. Published on November 6 (UTC), version 0.16.1-beta-7 also improves recovery when the active blockchain branch changes and adjusts transaction handling while nodes catch up on missing blocks.

News Report

Teranode is node software for validating and processing transactions and blocks on BSV Blockchain. This pre-release combines networking repairs, improvements to transaction recovery and an additional database option for operators.

Keeping Nodes Connected

The connection fault was in an underlying networking library. If another node closed a connection before Teranode accepted it, resources could remain reserved for a connection that no longer existed. Those unused reservations accumulated, eventually filling the allowance for incoming connections.

The project reports that affected nodes stopped accepting new connections after two to four weeks of operation. Beta 7 includes a patched library that releases those unused resources.

Keeping Transaction Records Consistent

When competing blocks cause a node to switch to another branch of the blockchain—a chain reorganization—its records need to follow that change. Beta 7 clears references left behind when certain transactions are removed. It also saves affected transaction records so they can be restored if the earlier branch becomes active again.

The release also changes how conflicting transactions are found in previously validated transaction groups. On supported databases, a targeted index replaces repeated checks of every transaction, addressing a bottleneck identified in the project’s scaling tests.

A Change for Payment Services

While a node catches up on missing blocks, it now refuses incoming transactions that have not yet been mined. This also applies during brief catch-up periods after normal operation.

Those submissions are not queued for later. Payment applications and other clients must resubmit them once the node is running normally again. The change protects the records needed to process incoming blocks from interference by newly received transactions.

An Optional Storage Choice

Beta 7 adds another PostgreSQL-based option for tracking unspent coins, called utxoset. It requires a fresh database; existing Aerospike and SQL deployments are not automatically converted.

Separately, operators upgrading the existing PostgreSQL transaction store must stop older processes before the new version builds its database index. Earlier upgrade instructions also remain applicable when moving from beta 5 or older.

BSV TIMES Read

Dependable payment infrastructure needs nodes that stay connected over time, keep consistent records and communicate temporary unavailability. The catch-up change also shows why improvements inside a node need corresponding behavior in the applications using it: a temporary refusal needs a reliable retry process.

Developer Context

Highlighted contributions come from oskarszoon for the connection fix, Simon Ordish (ordishs) for transaction recovery, freemans13 for catch-up handling and the new storage option, and Siggi (icellan) for validation and network protections.

Source Links

• Teranode v0.16.1-beta-7 — release and upgrade notes
• Connection-resource repair and verification — PR #2122
• Transaction cleanup and restoration during reorganizations — PR #2102
• Indexed lookups for conflicting transactions — PR #2110
• Transaction handling during catch-up — PR #2094
• Optional utxoset storage design and limitations — PR #1663
• Teranode Beta 7 — operator changelog

Posted on November 7, 2026 (UTC)