We ran the first throughput benchmarks on the Valdium testnet this week. 500 transactions, then 1000. Multiple submission strategies. The goal wasn't to produce marketing numbers — it was to find bottlenecks. We found them. Then we fixed them. Then we ran the numbers again.
Simple VLD transfers between wallets. Each wallet pre-funded, round-robin transfers so nonces increment cleanly. Three approaches: sequential (one tx, wait, next), parallel (batches of 25 concurrent), and batch via POST /tx/batch in chunks of 50.
| Sequential | Parallel | Batch | |
|---|---|---|---|
| Submit rate | 12.1 tx/s | 134.5 tx/s | 140 tx/s |
| Max txs/block | 26 | 235 | 550 |
| Block TPS | 11.5 | 75.2 | 166.7 |
| Accepted | 500/500 | 500/500 | 1000/1000 |
Zero failures across all three runs.
The sequential bottleneck was us, not the chain. At 12.1 tx/s, each submit took ~80ms round-trip. The chain was idle most of the time.
Dilithium3 verification is fast enough. Each transaction requires a post-quantum signature verification (~3,300 byte signature). The block builder verified 550 signatures in under 2 seconds. This was the main performance concern with PQC — it's not the bottleneck.
2-second finality is real. Consistent across all three tests. Not "expected" — measured.
The gas limit has massive headroom. 550 transfers at 21,000 gas each = ~11.5M gas. The block gas limit is 30M. Theoretical max for simple transfers: ~714 tx/s at 2-second blocks.
These are testnet numbers on a 4-validator network. They're a baseline. The first real data point. — dev team
Join the launch list and we'll send you a note whenever there's a new devlog entry, a research drop, or a real milestone.