Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
XRP The XRP ledger vulnerability once allowed the creation of tens of thousands of trillions of XRPs, and the repair process triggered a transparency controversy.
On October 9, developers disclosed an XRP ledger security vulnerability. If this vulnerability is exploited, in theory, approximately 18.45 trillion XRPs can be generated per transaction. Although the vulnerability existed as early as 2015 and was fixed on September 25, developers confirmed that no evidence of exploitation was found on the public network. The XRP Ledger Foundation also stated on social media that after verification, the public circulation supply remained complete.
How a vulnerability bypasses supply restriction checks
The vulnerability was reported by Veria on September 22. RippleX replicated the issue on a separate server, confirming that the newly created tokens can be used to fund other payments. Veria Labs co-founder Cayden Liao pointed out in an October post that the discovery benefited from Veria AI technology. He estimated the potential impact to create approximately 18.45 trillion XRPs per transaction, more than 184 times the initial supply, and earned a $250,000 vulnerability bounty.
This payment engine flaw involves integer overflow: when the total is too large, the value is wrapped around to a smaller number. This results in sellers being able to receive full payment while buyers paying only a very small amount. The supply protection mechanism originally used to prevent overruns failed to prevent unauthorized XRP casting due to repeated execution of the same arithmetic errors. According to reports, triggering this vulnerability requires deliberately making abnormal quotes between hundreds of accounts. Ordinary payments cannot activate the vulnerability, despite its long exposure time.
XRP ledger bug fix sparks transparency debate
Before releasing the source code, developers first pushed the 3.4.1 version of xrpld that included compiled software. The move sparked controversy over temporarily withholding source code. Justin Bons criticized the practice on social media, arguing that promoting XRP as "decentralized" but running closed source code was fraudulent, and pointed out that future upgrades would become mandatory.
RippleX engineer Mayukha Vada responded that artificial intelligence can quickly expose key fixes in public versions. Releasing patches before protections are activated could give attackers a window of time to exploit the XRP ledger vulnerability. However, overflow fixes take effect immediately after a server upgrade, bypassing the usual amendment delay process. On the day of release, more than 80% of the default UNL verification nodes were upgraded.
The XRP Ledger Foundation states that operators independently select their software and coordinate responses through community consensus. The foundation emphasized that this emergency deployment was different from the subsequent amendment vote that made upgrades necessary for synchronization. In addition, another batch fix was activated through an amendment on October 9. The foundation also promises to conduct broader formal verification, adversarial AI testing, and collaboration among researchers.
