The official Teranode repository released v0.16.0-beta-3 on July 14 as a pre-release, introducing a broad set of changes across transaction validation, block processing, UTXO handling, peer-network behavior, security, and operational reliability.

The release includes enforcement of BIP68 sequence-lock rules for non-coinbase transactions, an additional satoshi-range and no-inflation backstop, an overflow-safe coinbase reward and fee check, and stricter coinbase script validation. It also hardens P2P synchronization by preventing peer selection from relying on unvalidated claims.

Several changes address block and fork handling. These include using the full block hash when constructing orphan-fork identifiers, basing secret-mining decisions on chainwork, correcting the timing of mined-set clearing during fork validation, stabilizing the reload order for unmined transactions so parents are handled first, and preventing a fork-blocked spin in block validation.

The update also includes UTXO batching and metadata improvements, a fix for a concurrent Aerospike map failure, safer handling of in-flight Aerospike operations during shutdown, reduced allocations on UTXO processing paths, and a storage-reader fix intended to prevent corrupted subtree reads during an mmap fallback.

Security and code-quality work includes patches for nine dependency findings and a CodeQL integer-conversion alert, stronger secret-handling guidance for the Teranode operator, and hardening of the project’s automated secret-scanning workflow.

View the Teranode v0.16.0-beta-3 release

BSV TIMES read:
This is not a new throughput benchmark or a production-launch announcement. Its importance lies in the operational details. Large-scale node infrastructure depends on strict validation rules, reliable UTXO state, safe reward and fee calculations, defensible peer-selection boundaries, predictable fork handling, and resilience when storage or network components fail. Teranode v0.16.0-beta-3 shows continued work across those foundations while remaining clearly identified as pre-release software.

Posted on July 14, 2026