XRP Under Fire: Foundation Addresses Billion-Dollar Bug Crisis!
The XRP Ledger Foundation has defended its emergency decision to circumvent the standard amendment process, addressing a critical security vulnerability that could have led to trillions of unauthorized XRP being minted. While clarifying that no XRP was minted and the exploit was never active on the public network, the foundation explained the risks of a delayed patch and its coordinated response to protect the network's integrity.
The XRP Ledger Foundation recently defended its decision to bypass the standard XRP Ledger amendment process, citing a critical security vulnerability that posed a significant threat to the network. This vulnerability could have allowed malicious actors to mint trillions of XRP, potentially endangering the entire $94 billion XRP market cap by bypassing the fixed supply cap.
The foundation clarified that no unauthorized XRP was actually minted, and it addressed various misconceptions surrounding the recently discovered flaw. They confirmed that the vulnerability indeed had the potential for massive XRP creation, with estimates suggesting up to 18.45 trillion XRP could have been minted in a single transaction – an amount 180 times greater than the original XRP supply. However, the exploit was never observed on the public network.
This critical bug, reportedly present in the XRP Ledger payment engine since 2015, was uncovered by Veria Labs, an AI-powered security firm. The foundation vehemently addressed speculations regarding possible unauthorized XRP creation, stating that all XRP balances are public information, meaning any new XRP minting would be immediately visible. Furthermore, the network's supply is continuously monitored and verified by community members.
The XRP Ledger Foundation also tackled criticisms concerning the non-standard security patch release. Typically, changes to the XRP Ledger protocol require approval from over 80% of trusted validators for two consecutive weeks. However, the foundation argued that this conventional process would create a window of several weeks, during which potential attackers could exploit the vulnerability, especially given the ease with which flaws can be discovered and reverse-engineered with the aid of artificial intelligence. Consequently, developers determined that an immediate software update was necessary.
An emergency response was coordinated involving the XRP Ledger Foundation, RippleX, core developers, and validators. The patched software was distributed to validators, and public binaries were released on September 25. The foundation emphasized that no single entity has the authority to compel network participants to adopt any software update.