Hot topic · builder-side · non-market

Developer Tools & Core Development

Capacity Efficiency
@BSVTeranode argued that many networks spend a large share of capacity on inter-node chatter, while Teranode nodes operate more independently so more capacity goes to actual user transactions.
(View post)

Architecture Capacity
The current system continues to be described as capable of roughly 6 million tx/sec, with optimisation potentially reaching around 10 million — framed as math on the existing architecture rather than a distant roadmap claim.
(View post)

Deployment Paths
Discussion continued around what “running a node” requires. Documented options include a single-host Docker Compose setup (Aerospike + Postgres + Kafka/Redpanda) alongside Kubernetes configurations for horizontal scale. Multi-region and S3 backends remain optional rather than baseline requirements.
(View post)

Subtree & Storage
Subtree-based block design and sub-millisecond UTXO lookups via Aerospike remain part of the technical picture for high-throughput operation.
(View related)

Projects & Adoption

LocalBSV Improvements
@bsvdrip highlighted better 0-conf trading (back-to-back purchases without waiting for prior confirmations) and partial-fill limit orders. An earlier UTXO selection bug affecting some BSV-21 purchases is still being worked, with a fix targeted before early October.
(View post)

Overlay Coordination
Notes on dynamic topic subscription at the overlay level, and subtree filtering at the miner level, for specialised processing.
(View post)

Community Reflections & Other Activity

Scaling Narrative
Posts continue to frame unbounded block size and Teranode-level throughput as the path to global on-chain utility.
(View example)