XRPL's 2.8 Billion AMM Volume Spike: Why the Number Misleads

A finance team would never add 2.7 billion Korean won to 100 million US dollars and call the result “2.8 billion of revenue.” The currencies need conversion into a common unit at defensible rates. A current XRPL automated-market-maker statistic creates the same problem with token quantities.

On 24 September 2026, two recently created XRPL pools reportedly accounted for 2.74 billion units across 185 pool-level trades—97.24% of a provider's seven-day AMM tally of about 2.82 billion. The headline sounds like a vast burst of liquidity. The underlying pool balances and unspecified valuation method support a much narrower conclusion: unusual on-chain activity dominated one ranking metric.

What the two pools reported

The XPM/TIX pool was reported at approximately 1.681 billion units across 69 trades. The RLUSD/TIX pool contributed roughly 1.062 billion units across 116 trades. Both pools involved TIX from the same issuer, and the two pools were created on 21 September.

At the time of the reviewed snapshot, the XPM/TIX pool reportedly held about 1,545.50 XPM and 9.69 million TIX. The RLUSD/TIX pool was shown with vanishingly small current balances—about 0.000000000000051 RLUSD and 0.000000062 TIX. Neither pool held native XRP.

Those figures make it unsafe to describe the activity as $2.74 billion, 2.74 billion XRP or 2.74 billion of deployable liquidity. The source total was a pool-sorting metric expressed in “units,” without a disclosed common-currency methodology for these token-to-token fills.

Units are not value

Suppose one token trades at one millionth of a dollar. A transfer of one billion units has a notional value of $1,000, not $1 billion. The unit count looks large because the token's denomination is small.

The reverse can happen with a high-priced asset: ten units may represent more value than a billion units of another token. Adding raw quantities across different assets is therefore like adding litres to kilometres. The arithmetic can be correct while the economic statement is meaningless.

Good volume reporting converts each side into a common reference currency using a documented price at the time of the trade. It also explains whether both sides are counted, whether routed trades are duplicated across pools and how illiquid token prices are established.

Why 185 trades can create a huge total

A trade count measures events, not unique people. One trader can create many transactions. A routed XRPL payment can also touch more than one liquidity source, producing pool-level observations that should not be casually equated with independent customer trades.

Token quantities can circulate repeatedly. If two controlled accounts exchange the same inventory back and forth, reported turnover rises even though little new capital enters. That pattern can have legitimate explanations, such as testing or arbitrage, and abusive ones, such as wash trading. The reviewed data do not establish motive, so the article should not label the activity without further evidence.

The safe finding is concentration: a very small number of pools and transactions dominated the metric. Analysts then need addresses, transaction paths, economic prices and liquidity history before describing the purpose.

Volume is not liquidity

Liquidity asks how much can be bought or sold near a quoted price. Volume asks how much trading was recorded over a period. A pool may show high historical turnover and still contain almost nothing when a new trader arrives.

For a corporate user, executable depth matters. Could the treasury convert $100,000 of RLUSD without moving the price by 10%? Could it reverse the transaction? Is there a reliable market outside one pool, and can the issued token be redeemed for the asset it claims to represent?

The reported RLUSD/TIX reserve snapshot was nowhere near evidence of a deep dollar market. A token symbol containing “RLUSD” does not make the other token valuable, and a tiny RLUSD balance does not demonstrate material Ripple stablecoin liquidity.

Our guide What Is Liquidity and Why Does It Matter So Much for XRP? explains why depth, spreads and slippage are more useful than a standalone turnover number.

Neither pool contained XRP

XRPL AMMs can hold XRP and an issued asset, or two issued assets. These two pools were reported as XPM/TIX and RLUSD/TIX. Their activity therefore did not require XRP as either pooled principal asset.

They still operated on the XRP Ledger and paid XRP-denominated transaction costs. Those fees are tiny relative to the headline unit total. No defensible analysis can convert the 2.74 billion-unit metric into equivalent XRP demand.

This is a practical example of the separation discussed in Does XRPL Adoption Actually Create Demand for XRP?. Network activity can be genuine while its direct asset-demand channel is limited to fees and account reserves.

RLUSD's name needs careful treatment

One side of the second pool was RLUSD, Ripple's US-dollar stablecoin. A legitimate RLUSD amount has a familiar reference value near one US dollar, subject to issuer terms and market conditions. The TIX side did not inherit that valuation merely by being paired with RLUSD.

AMM prices are ratios of pool reserves. In a thin pool, a tiny transaction can move that ratio sharply. A displayed spot price does not prove that a large position can be sold at the same level or redeemed with the issuer.

An analyst valuing a token-to-token trade should identify a robust price source for both assets. When one token lacks an external market, the most honest output may be “not reliably valued” rather than a precise dollar total.

A better dashboard for XRPL AMMs

A useful monitoring screen would start with volume in a common currency and clearly state the pricing method. It would then show current and average liquidity, trade count, unique addresses, median trade size, largest trade, pool age and concentration by the top pools.

It should separate swaps from deposits, withdrawals and other AMM-related transactions. XRPL.to's broader token-market dashboard, for example, distinguishes AMM and order-book activity and reports values in XRP for its market summary. Even then, users should review the provider's methodology and the quality of token prices.

For an unusual pool, examine the ledger directly. The account addresses, transaction hashes and issuer identifiers let a researcher reconstruct the activity. Public verifiability is one of XRPL's strengths, but a public record does not interpret itself.

Does this mean XRPL data are unreliable?

No. The ledger can accurately record every validated transaction while a dashboard chooses an unhelpful aggregation. Data quality has layers: the protocol record, the indexer's classification, the pricing model and the journalist's description.

The distinction is familiar in accounting. A general ledger can contain correct entries, while a management report groups them badly. Fixing the report does not require declaring the accounting system fraudulent.

The episode is useful because it exposes the limits of raw volume. It encourages data providers to label units and valuation methods, and readers to ask whether a number represents tokens, XRP, dollars or a provider-specific score.

What It Means for XRP

The two pools do not show billions of dollars entering XRPL, and they do not show 2.74 billion XRP of demand. They show that two non-XRP token pools dominated a seven-day AMM unit metric through a small number of pool-level trades.

That does not make the activity irrelevant. It may reveal testing, token distribution, routing behaviour or another pattern worth investigating. But the connection to XRP is limited unless the activity pays material fees, creates account reserves, uses XRP liquidity elsewhere in a route or changes investor expectations.

Price claims built on the headline should therefore be rejected. The network can host the transactions without the number saying anything reliable about XRP's fair value.

The practical takeaway

The 2.8-billion figure is a lesson in measurement. Raw token units from different assets cannot be treated as a common currency, historical volume does not equal current liquidity, and pool-level trades do not necessarily represent separate users or economic purchases.

Before repeating an XRPL volume headline, ask four questions: what is the unit, how was it valued, how much executable liquidity exists and how concentrated is the activity? In this case, those questions turn a dramatic adoption claim into a more accurate finding: two new token pools generated an abnormal provider metric that deserves investigation, not celebration or panic.