XRP Ledger Upgrade Moves Ahead As Security Vote Remains Pending

TLDR

• The XRP Ledger upgrade reached 89% adoption across the default Unique Node List validators, exceeding the activation threshold.
• About 43% of active XRP Ledger nodes run v3.2.0, while 51% still operate the older v3.1.3 release.
• The fixCleanup3_2_0 amendment remains under separate validator voting despite strong software upgrade adoption.
• Ripple voted in favor of the security amendment, which adds fixes for vaults, MPTs, lending, and permissioned DEX features.
• Validators that fail to upgrade before the amendment activates could enter an amendment-blocked state on the XRP Ledger.

The XRP Ledger (XRPL) has moved closer to its latest network upgrade as most trusted validators adopted version v3.2.0. However, many public nodes still use the previous release, while an important security amendment remains under voting. The latest figures show strong validator support, but the broader network has not completed the transition.

XRP Ledger Nodes Remain Split

The XRP Ledger now runs v3.2.0 across most trusted validators on the default Unique Node List. Meanwhile, public node adoption remains split between the latest and previous software versions. The difference highlights separate progress across different network participants.

XRPSCAN data shows about 833 active nodes currently support the XRP Ledger network. About 43% run v3.2.0, while about 51% still run v3.1.3. The remaining nodes use older releases or different configurations.

Validators play a different role because they confirm transactions and maintain network agreement. The default Unique Node List includes 35 trusted validators across the XRP Ledger ecosystem. Currently, 31 validators run v3.2.0, representing about 89% support.

Software Adoption and Amendment Voting Remain Separate

The XRP Ledger requires more than 80% validator support for two consecutive weeks before activation. Current validator adoption already exceeds that required threshold across the default validator list. However, software installation alone does not complete every network change.

The fixCleanup3_2_0 amendment follows a separate on-ledger voting process. It includes security updates for single-asset vaults and permissioned decentralized exchanges. It also covers multi-purpose tokens, known as MPTs, and the lending protocol. The amendment also introduces internal checks that prevent deleted accounts from leaving unwanted ledger data.

Ripple Backs the Proposed Security Amendment

Ripple has voted in favor of the fixCleanup3_2_0 amendment for the XRP Ledger. That vote supports the proposed package of security fixes and operational improvements. Other validators continue deciding whether to approve the amendment before activation.

The XRP Ledger treats amendment approval separately from software upgrades because each process serves a different purpose. Validators must complete both steps before the network activates the proposed changes. The system applies those requirements through its established governance process.

Validators that miss the required upgrade could enter an amendment-blocked state after activation. The XRP Ledger automatically restricts those validators from participating under updated network rules. That outcome encourages timely upgrades as the amendment approaches the required level of approval.

The post XRP Ledger Upgrade Moves Ahead As Security Vote Remains Pending appeared first on CoinCentral.