The XRP Ledger has restored previously suspended functionality through its latest rippled software update, reinstating features that were removed after critical bugs were identified. The restoration is part of the network's amendment-based governance process, with the changes documented in the project's official release and accompanying blog materials.

The XRP Ledger is a Layer 1 blockchain used for cross-border payments, tokenization, and decentralized finance applications, making the reliability of its core software directly relevant to a broad ecosystem of developers, financial institutions, and infrastructure providers.

Details of the Restoration

The update is tied to the rippled 3.2.0 release, the core software powering XRP Ledger nodes. It reinstates capabilities that had been withdrawn during an earlier remediation period following the discovery of network reliability issues.

Feature activation on the XRP Ledger is governed by amendments, which require validator approval before taking effect network-wide. Amendments must maintain at least 80% support from the network's trusted validators over a two-week period to activate — a mechanism designed to prevent unilateral changes and ensure network-wide consensus. The current status of each amendment is tracked on the known amendments reference page, which lists every amendment and its state on the network.

The reinstated functionality follows this amendment pathway rather than an automatic switch, meaning it depends on validator support before going live. The ledger recently demonstrated this mechanism when it activated the fixCleanup3_2_0 amendment after achieving 85.7% validator support.

Why the Features Were Removed

The features were originally pulled after issues surfaced that affected network reliability. Details on the underlying problem were published in a vulnerability disclosure report from September 2025, which outlined the nature of the bug and the project's response.

Between the rollback and the restoration, the fix had to be developed, reviewed, and packaged into a formal software release. The full sequence of rippled builds is visible on the project's GitHub releases page, which records each version and its accompanying notes.

The process was framed as a reliability matter rather than an ongoing security threat, demonstrating the network's approach of prioritizing stability by removing affected features until a verified fix was in place — a posture that aligns with how other major blockchain projects have handled similar discoveries, where conservative feature suspension is preferred over deploying incomplete patches.

Implications for the XRP Ledger Ecosystem

For node operators, the practical step is upgrading to the latest rippled build to ensure infrastructure remains compatible with the network as amendments progress. Validators, in turn, determine whether associated amendments reach the activation threshold required for network-wide implementation.

Developers building on the XRP Ledger regain access to the previously withdrawn functionality once the relevant amendments are enabled, allowing applications that depend on those features to resume operation. However, activation is not guaranteed until validator voting completes, so builders are advised to confirm amendment status before relying on the restored behavior. Developers should also monitor the known amendments page for additional amendments advancing through the voting process, as the 3.2.0 release cycle may introduce further capability changes that could affect application behavior.