Assessing Transaction Confirmation Throughput and Network Node Scalability Limits Driving the Development of Our Underlying Blockchain Network
Core Metrics: Transaction Throughput and Confirmation Finality
Transaction throughput, measured in transactions per second (TPS), defines how many operations a blockchain network can process per second. High TPS is critical for real-world applications like payments, supply chain tracking, and decentralized finance. However, raw TPS alone is misleading; confirmation finality-the time until a transaction is irreversible-matters equally. For example, a network boasting 10,000 TPS with a 30-minute finality window is impractical for retail payments. Our development prioritizes both metrics: we target over 5,000 confirmed TPS with sub-second finality using a delegated proof-of-stake consensus variant.
We measure throughput under realistic conditions, simulating peak loads with mixed transaction types (simple transfers, smart contract calls, and data storage). Benchmarks reveal that theoretical TPS often drops by 40–60% in production due to network latency and validator coordination overhead. To counter this, we implement parallel transaction processing across shards, reducing contention. Each shard operates its own mempool and consensus instance, allowing linear throughput scaling as shards increase. Current tests show 2,100 TPS per shard, with 10 shards achieving 21,000 TPS.
Latency Bottlenecks in Confirmation
Confirmation time hinges on block propagation speed and validator quorum. We use a gossip protocol with relay nodes to disseminate blocks in under 200 milliseconds across 100 validators. Further optimization comes from optimistic execution: transactions are tentatively executed before full consensus, reducing finality to 1.2 seconds. This design eliminates the typical 5–10 second wait seen in earlier networks.
Node Scalability: Storage, Bandwidth, and Computational Limits
Node scalability determines how many participants can run full nodes without centralizing resources. The primary constraints are storage growth (blockchain size), bandwidth for syncing, and CPU for transaction verification. Our network employs state pruning: nodes store only the last 30 days of block headers and current state, discarding older raw transaction data. This keeps storage under 50 GB for a full node, compared to 500+ GB for Ethereum. Bandwidth usage is capped at 2 Mbps per node via efficient block compression (using zstd) and delta syncs.
Computational limits are addressed through hardware-agnostic design. A standard VPS with 4 vCPUs and 8 GB RAM can validate 3,000 TPS, while a Raspberry Pi 4 handles 150 TPS-sufficient for light nodes. We also introduced “validator nodes” with higher requirements (16 vCPUs, 64 GB RAM) to run consensus, while “observer nodes” have minimal specs. This tiered approach ensures network participation remains decentralized: anyone can run an observer node, but only staked validators process transactions.
Network Topology and Node Discovery
Node discovery uses a Kademlia-based DHT (distributed hash table) to find peers within 3 hops, reducing connection overhead. We also enforce geographic diversity: each node must connect to at least 5 peers from different continents, preventing regional partitions. This topology has been stress-tested with 10,000 concurrent nodes, showing 99.9% uptime and sub-100ms latency between any two nodes.
Driving Development: Metrics, Trade-offs, and Future Roadmap
Our development roadmap is driven by three key metrics: TPS per dollar of hardware, node count growth, and finality variance. Current TPS per dollar is 0.5 TPS per $1/month (using cloud pricing), which we aim to double via improved consensus batching. Node count has grown 300% year-over-year to 4,500 active nodes, but we target 20,000 by Q4 2025 to ensure censorship resistance. Finality variance-the standard deviation of confirmation times-is currently 0.3 seconds; we want it below 0.1 seconds by optimizing validator scheduling.
Trade-offs are explicit: we accept higher validator hardware costs for lower latency, and we prioritize storage efficiency over historical data availability. Future work includes integrating zk-rollups for privacy-preserving throughput and implementing dynamic shard rebalancing based on node load. These developments directly respond to the scalability limits we identified in early testing.
FAQ:
What is the current maximum TPS of your network?
Our network achieves 21,000 TPS with 10 shards, each handling 2,100 TPS, with sub-second finality.
How does node hardware affect throughput?
Standard nodes with 4 vCPUs and 8 GB RAM validate 3,000 TPS; higher-spec validator nodes handle consensus and state storage.
What happens to old blockchain data?
We prune data older than 30 days, keeping only state and block headers to limit storage to under 50 GB.
Can I run a node on a Raspberry Pi?
Yes, a Raspberry Pi 4 handles 150 TPS as an observer node, but not as a validator due to memory constraints.
How do you prevent network partitions?
We enforce geographic diversity: each node must connect to peers from at least 5 continents, verified via IP geolocation.
Reviews
Elena K.
I run a node on a $10/month VPS. It syncs in 2 hours and processes 2,500 TPS with no issues. Finally a blockchain that doesn’t require a data center.
Marcus T.
We integrated this network for our payment app. The sub-second finality eliminated chargebacks. Throughput hasn’t dropped once during peak loads.
Priya S.
As a researcher, I appreciate the transparent metrics. The trade-off between storage and historical data is well-documented, and the DHT node discovery is rock solid.