Research topic

ledger

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

2 publications

View all research

Architecture diagram showing payment traffic at 2,600 per second moving through horizontally scalable stateless compute, a removed write-path contention point, and a healthy ledger database at about half capacity, with all payments committed and zero hard or ledger failures.

EngineeringAug 27, 20264 min read

We pushed our ledger until something broke. It wasn't the ledger.

We kept driving the payment path until we found the next limit, removed a database contention point, and left the ledger database running at about half capacity at peak.

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