The XRP Ledger has processed 3,254 transactions inside a single validated ledger, a figure that validator operator Vet described as a new single-ledger record for the network. The burst occurred on Sept. 14, and according to Vet’s review of the ledger data, the overwhelming majority of those entries were payments carrying exactly one drop of XRP — the smallest native unit the network can record, equal to one-millionth of a single XRP.
A throughput test, most likely
Vet, a well-known XRPL validator operator, published the figure after reviewing the ledger and later elaborated on X. “I don’t know why this person is doing these transactions, but it looks like throughput testing, probably,” he wrote. The description remains speculative, because the account that initiated the burst has not publicly explained its purpose, and Vet did not identify the ledger index or the sending account in his post.
Because the record claim relies on one operator’s analysis, it cannot be independently compared through the post alone against every earlier ledger in XRPL history. Still, the mechanics of what happened are instructive for anyone trying to understand how the XRP Ledger handles load — and why a raw transaction count can be misleading.
Not all transactions are equal
Most of the 3,254 transactions were simple native-asset payments. Simple XRP transfers require far less processing work than transactions involving decentralized exchange orders, NFT operations or cross-currency payment paths. Vet estimated that 500 simple payments could place less stress on validators than 200 transactions requiring heavy automated-market-maker or order-book processing. “Not all transactions are equal in load footprint,” he cautioned.
There is also a nuance in what the number actually counts. Official XRPL documentation states that each validated ledger records the transactions applied to the preceding ledger state, along with metadata showing the result and effects of each. Transactions carrying a tesSUCCESS result completed their requested action, but entries with a tec result remain recorded and still consume a fee even when they fail to perform their intended operation. The headline figure of 3,254 therefore describes included transactions, not necessarily 3,254 successful transfers.
Why XRPL can absorb a burst like this
The episode also highlighted a structural difference between the XRP Ledger and networks like Bitcoin. As Vet pointed out, XRPL blocks are governed by dynamic size limits rather than a fixed ceiling. The network does not use one permanent transaction cap for every ledger; instead, servers adjust operating conditions in response to transaction volume, network latency and consensus performance.
According to Vet and XRPL documentation, the network can raise its soft transaction target when a heavily loaded ledger still closes within the expected time window. When close times drift beyond the preferred range, the target can be reduced to help validators return to normal timing. Servers exchange proposals until trusted validators agree on a transaction set, then each calculates the new ledger state and distributes a signed validation containing the resulting ledger hash. A supermajority of trusted validators must agree on the same hash before the ledger becomes final.
The 3,254-transaction result proves the validators agreed on a ledger carrying that many entries. It does not establish a new permanent throughput rate, because sustained capacity depends on transaction complexity, hardware, network conditions and consecutive ledger close times. No performance report from Ripple, the XRP Ledger Foundation or the maintainers of the reference software has confirmed any permanent capacity change following the burst, and no service interruption or failed consensus round was reported in connection with it.
Activity context: BatchV1_1 and rising volume
The record landed during a period of elevated interest in XRPL throughput questions. The BatchV1_1 amendment, which introduces batched transactions to the ledger, remains under validator voting and requires sustained 80 percent support before automatic mainnet activation. Earlier in September, the network also activated the fixcleanup3_3_0 amendment tied to its native lending roadmap, a upgrade cycle that has kept attention on what the ledger can handle.
Recent quarters have also shown heavier organic usage. XRP Ledger order-book volume rose 79 percent year over year during the second quarter of 2026, according to an Evernorth report cited in related coverage, with average daily order-book activity climbing alongside broader usage of the network’s decentralized exchange.
What it means for XRP holders
For market participants, the event is a reminder that headline transaction counts on any network measure activity, not value moved. A ledger full of one-drop payments shifts almost no economic value, even as it stresses — or in this case, fails to stress — the consensus layer. XRP traded around 1.40 USD in Monday trading, up roughly 4.5 percent over 24 hours as the broader market rebounded ahead of this week’s Federal Reserve decision.
The more durable takeaway is architectural. Because XRPL adjusts its transaction target adaptively, a burst that might congest a fixed-block-size network was absorbed, validated and finalized without incident. Whether the sender was stress-testing, probing fee markets or simply experimenting, the network’s dynamic design handled 3,254 entries in one ledger — and closed on time.
3,254 txs in one ledger and nearly all one-drop payments. thats someone stress testing with the cheapest payload possible, vets throughput theory sounds right
Curious what the total fee came to for the whole burst. Thousands of payments for pocket change is either a test or someone probing the spam limits
even at a few drops per tx the whole burst cost a fraction of one XRP. the fee burn was never the point, load footprint was
back of napkin, 3254 payments at standard ten drop fees burns about 0.03 XRP total. someone stress tested the whole ledger for the price of a gum ball
3254 payments of exactly one drop each. someone really paid fees to spam the smallest unit XRPL can record, wild way to stress test
Vet calling it throughput testing without identifying the ledger index or the account is a bit thin honestly. interesting stat, weak sourcing
validators read the raw ledgers directly, he doesnt need to name the account to count 3254 txs. but yeah, posting the ledger index would take ten seconds and end the debate
one drop is one millionth of an XRP. fees on that burst cost basically nothing, which is kind of the point of the exercise i guess