CBDC pilot achieves 50,000 transactions per second in test run
The Bank of Japan reported that its digital currency pilot reached 50,000 transactions per second during high-load tests. The findings, presented at the sixth CBDC Forum meeting, identified no critical technical obstacles for online payments across 84 working sessions with 163 firms.
Benchmarking throughput and account limits
During high-load testing for Japan’s digital currency pilot, the architecture completed 50,000 transactions per second across a mixed workload of 10,000 balance updates and 40,000 inquiries within three seconds.
Single-account stress tests verified throughput of up to 6,000 transactions per second using record splitting.
The Bank of Japan reported that evaluations found no irresolvable technical barriers for online payments.
However, testing exposed operational vulnerabilities: execution spikes caused momentary halts and pushed processing units to full capacity, demonstrating a requirement for message flow controls.
Furthermore, while splitting account records improved throughput, excessive divisions degraded processing efficiency, requiring refined timeout protocols.
From sandbox tests to private coexistence
The findings synthesize 84 forum sessions held since 2023, drawing on technical presentations from 163 participating private entities.
Deliberations centered on five operational areas: core ledger architecture, identity verification and anti-money laundering frameworks, overlay API sandboxes, coexistence with commercial deposits, and emerging tools like asset tokenization and offline payment support.
Intermediaries also tested programmable payments for conditional settlement and retail bond issuance.
Promising speed, lingering operational debt
While baseline throughput proves viable, processing one-tenth of projected peak volume leaves real scaling questions open.
Connecting pilot ledgers to legacy banking systems will create severe friction in error management and cost distribution.
Lab feasibility alone will not resolve the structural hurdles of full deployment.
Source: Sixth General Meeting of the CBDC Forum
IN: