XRP Ledger confirms that no new XRPs have been issued and fixes vulnerabilities

The XRP Ledger Foundation confirmed that no new XRP issues have been added and key vulnerabilities have been fixed.

The XRP Ledger Foundation (XRPLF) issued a statement confirming that no new XRP tokens have been generated in recent online incidents. At the same time, the foundation disclosed that it had identified and fixed critical security vulnerabilities affecting XRP ledgers. This double confirmation responds to two distinct sets of concerns: issues related to supply integrity and issues related to protocol security. These two points are of substantial significance to holders, developers and operators running XRP ledger nodes.

Confirmation of "No new XRPs"

The Foundation's confirmation of "No new XRPs have been created" directly responds to market concerns about the unauthorized issuance of XRP ledgers. XRP has a fixed maximum supply of 100 billion tokens, and all tokens were created in one go at the beginning of the network. Therefore, any unauthorized creation will be considered a serious failure of supply integrity. The foundation statement clearly stated that this cap has not been exceeded.

Meaning of the "No New XRP" confirmation

For token holders, this confirmation distinguishes this event from "casting vulnerability attacks" common on other networks. However, the statement did not specify which activity on the necklace triggered the clarification, nor did it list the transaction hashes examined or the specific range of blocks audited. In the communication released by the foundation, these details were not provided and cannot be inferred from existing information.

Critical vulnerability has been fixed

At the same time, the foundation said key vulnerabilities in the XRP ledger have been fixed. As of the time of publication of this article, the nature of these vulnerabilities was not clearly defined in public information, including the software versions affected, the attack surfaces involved, and the timeline for disclosure. The foundation described the fix as a response to a "critical" vulnerability, a language that implied a high severity but did not conduct a quantitative assessment.

Why vulnerability fixes are critical to XRP ledger users

XRP ledgers are operated by a group of distributed validators, and security patches require coordinated upgrades between independent node operators. The fixes confirmed by the foundation do not mean that all verifier infrastructure has been updated; operators running older versions of rippled software may still be at risk until patches are applied. Developers building applications on ledgers and exchanges that process XRP settlements should verify their node versions against the version recommended by the foundation.

In addition, supply chain vulnerabilities affecting hardware wallet infrastructure suggest that even if the core protocol code is sound, third-party components can still introduce risks. This has been proved by previously documented cases of hardware signature equipment supply chain damage.

Confirmed facts and matters to be clarified

Two facts have been confirmed in the foundation's announcement: no new XRP has been created, and key vulnerabilities have been fixed. Everything else, including the vulnerability name, the corresponding CVE identifier if assigned, the specific rippled version affected, the fix date, and independent third-party verification of the fix, is not provided in the existing briefing and no assumptions should be made.

Readers are advised to wait for official documents to answer questions

In the existing records, the foundation has not publicly released a detailed post-mortem report or security bulletin containing specific erroneous names. Users who operate verifier nodes, build payment infrastructure, or hold XRPs in self-custody should directly consult the XRP Ledger Foundation's official communications and rippled release notes for implementation guidance. Given that previous hardware-level events, including supply chain attacks that resulted in significant Bitcoin losses, have shown that incomplete patch adoption can amplify the risk, the window between fixes being available for widespread application is a critical exposure period for any network.

Frequently Asked Questions (FAQ)

Has a new XRP been created?

The XRP Ledger Foundation confirms that no new XRP has been created. According to the foundation's statement, the total supply remains within a fixed issuance cap.

Has the XRP ledger vulnerability been fixed?

The foundation confirms that critical vulnerabilities have been fixed. The repair work is described as completed, but in the existing disclosure, the results of the independent verification and the specific technical scope of the repair have not been detailed.

Are specific remediation measures and affected components described in detail?

Detailed information is not provided in the existing briefing sheet. The name of the vulnerability, affected rippled versions, patch release dates, and any CVE assignments were not specified in the information disclosed at the time of publication of this article. Operators should pay close attention to the official channels of the XRP Ledger Foundation for complete security announcements.