Scaling & Teranode / Node Software
In Brief
Teranode Beta 9 corrects a problem that could leave a failed node service offline instead of automatically restarting. Available to node operators as a prerelease, it also improves startup with large databases and reduces some of the memory overhead involved in checking transactions.
News Report
Version 0.16.1-beta-9 was published on November 12, 2026, at 15:12 UTC. Its three changes address service failures, database recovery and transaction validation, with further memory work still outstanding.
Making Failed Services Restart Properly
Previously, a service failure could shut down Teranode while reporting a successful exit to the software supervising it. Systems configured to restart failed processes could therefore leave it stopped. In deployments where services run separately, other components could continue reporting that they were healthy.
Beta 9 returns a failure status so restart policies in systems such as Docker and systemd can respond. A clean, requested shutdown still reports success. The fix makes failures visible to existing restart controls; operators still need those controls configured.
Avoiding a Database Search That Prevented Startup
Block Assembly, the service that prepares transactions for new blocks, checks a recovery log when it starts. With the Aerospike database, finding that small set of records previously required searching a much larger collection. On a database comparable in size to mainnet, the search could time out and prevent startup.
The update adds a database index that lets the service find the relevant records directly. It also retries failed recovery-log reads for up to ten minutes each, giving temporary storage problems time to clear. Persistent failures can still stop startup.
Operators must allow for the index’s memory cost: at least 16 MiB per Aerospike node. Exceeding the database’s index-memory budget can stop writes. Where Teranode lacks permission to create the index, an administrator needs to create it; otherwise, startup continues using the slower search.
Reducing Memory Pressure During Transaction Checks
The memory changes follow repeated service shutdowns observed while a testnet node caught up with blocks containing large data transactions. Part of the problem was that its automatic memory budget overlooked a cache allocated outside the area managed by Go, Teranode’s programming language.
Beta 9 reserves room for that cache and other memory use. It also reduces repeated allocations when decoding large transactions from the node’s own storage. In a project benchmark using a 32 MB transaction, the decoding step allocated roughly the transaction’s size in memory, down from about 5.8 times that amount. The figure covers that processing step only.
This remains a partial fix. Low memory limits can still be insufficient, and the broader memory issue remains open. Separate project benchmarks also found slower decoding for transactions with many small inputs or outputs; the effect on a running node has not been measured.
BSV TIMES Read
For operators, reliability includes whether a failed service restarts, whether recovery finishes, and whether memory limits reflect what the software actually uses. Beta 9 addresses those everyday operating conditions. Its remaining limitations make testing with an operator’s own database size, transaction mix and memory settings especially relevant.
Developer Context
GitHub contributor oskarszoon authored all three changes included in Beta 9 and published the prerelease. Earlier Teranode work includes integrating a fix for connection resources becoming exhausted after weeks of uptime, which could prevent a node from accepting new peers.
Source Links
- Teranode — Version 0.16.1-beta-9 release and upgrade notes
- Teranode PR #2149 — Report service failures to restart systems
- Teranode PR #2151 — Find recovery records without a database-wide scan
- Teranode PR #2177 — Memory budgeting and stored-transaction decoding
- Teranode issue #2176 — Testnet memory failures and remaining work
- Teranode issue #2179 — Decoding performance tradeoffs
- Teranode Beta 7 — Earlier peer-connection reliability work
Posted on November 16, 2026 (UTC)

Leave a Reply