How does Kaspa decide its blocks-per-second and transactions-per-second settings?

Kaspa's network parameters — including blocks per second (BPS) and transactions per second (TPS) — are set through structured benchmarking rather than guesswork. Developers run tests across devnets and testnets, analyze the trade-offs of different configurations, and use those results to settle on a BPS/TPS setup intended for the long run. For a beginner, this matters because it shows that Kaspa's performance targets are backed by empirical testing, not arbitrary choices.