The official Teranode repository published v0.16.0-beta-1 on June 26 as a pre-release. The release notes include work around policy-rejected transactions, subtreeprocessor deadlock prevention, Kubernetes-based P2P public exposure guidance, dependency updates for fuzz-discovered fixes, and expanded multinode scenarios covering validator isolation, topology splits, propagation freezes, asset control, network partitions, and reorg testing.
The same pre-release also includes deeper reliability and performance-related changes, including replacement of BadgerDB with an off-heap mmap hash table in block-validation maps, crash-safe conflict-resolution handling, blockassembly metrics, subtree streaming backpressure, Aerospike overload retries, and fixes for validation and observability edge cases.
BSV TIMES read:
This should be read as infrastructure hardening, not as a new public throughput claim. The important signal is operational: Teranode development continues to focus on validation behavior, peer-network exposure, blockassembly reliability, testing under adverse network conditions, and the kinds of failure handling needed before large-scale applications can depend on the network layer with confidence.
Posted on June 29, 2026

Leave a comment