Research topic

load testing

Open, evidence-backed analysis from the WalletD engineering team.

2 publications

View all research

Diagram defining one transaction as a full authorize-and-capture payment cycle that commits one balanced double-entry ledger transaction, above a stepped load ladder of plateaus rising from 400 to 2,600 payments per second.

MethodologyAug 27, 20269 min read

How we load-test a ledger, and what a payment per second really means

A benchmark number is only as good as its definition. Here is exactly how we drive load against the ledger, what one transaction per second counts, and why the method maps to real production traffic rather than a lab trick.

Read analysis

Load-test diagram showing 1,600 payments per second, full delivery, equal debits and credits, an independent audit over 1,550,594 transactions, zero ledger violations, and about 26 percent writer processor use.

EngineeringAug 26, 20267 min read

We proved our ledger stays correct at 1,600 payments a second.

A ledger has one job it can never get wrong: the books must balance, always, no matter how much money is moving. We load-tested for speed and correctness, then published every number.

Read analysis