Skip to content

2026

  • 7 min read

Scaling Throughput in Waterfall Private Network: Results from Tests 25-29

Disclosure

  • This article text was prepared with AI assistance.
  • All test data, measurements, and reported metrics were produced from actual test runs without AI-generated data.
  • Main number: Best result is Test 29 with 128,333.33 TPS sustained, 93,095.24 TPS full-run, and 175,000 TPS peak.
  • Main takeaway: Throughput scaling is strongest with 2s slots and 35 blocks/slot, but only if node capacity and distribution can retain performance beyond peak windows.
  • Main limitation: Results come from a single-datacenter private environment; real distributed-network throughput is expected to be lower.

This Waterfall Network testing cycle was designed to answer a practical scaling question: which parameters increase throughput most effectively, and where does system behavior break down under load.

Across tests 25-29, we changed three main dimensions:

  • Slot duration (3s -> 2s)
  • Blocks per slot (25 -> 35)
  • Network decentralization level (node count increase from 10 to 17)

The central hypothesis was that protocol-level changes alone are not enough. Throughput growth in Waterfall Network depends on the interaction between protocol configuration, node distribution, and hardware capacity. The final runs confirm this: all high-load profiles reached very high peak values, but only some preserved that performance during the full run.

In short, the strongest profile in this series is Test 29 (2s, 35 blocks/slot), while the full dataset shows why retention and stability matter as much as peak TPS.