The XRP Ledger (XRPL) is inching closer to a major network upgrade after a surge in validator upgrades, but a key amendment still needs much wider backing before activation.
Snapshot of adoption
- Trusted validators running xrpld v3.2.0: 84 (55.63% of the validator set)
- All network nodes running v3.2.0: 353 (42.12% of nodes)
- Validators still on v3.1.3: 58 (38.41% of validators)
- Nodes still on v3.1.3: 440 (52.51% of nodes)
How upgrades activate
On the XRPL, trusted validators vote on protocol amendments; regular nodes simply follow the trusted validator list. Under the network’s governance rules, an amendment must be supported by more than 80% of trusted validators for two consecutive weeks before it can be activated. With ~55.6% currently on v3.2.0, the network needs roughly another quarter of validators to migrate before the upgrade can move toward activation.
What’s in xrpld v3.2.0
Released as xrpld v3.2.0 (formerly rippled under the XLS-0095 proposal), the update bundles infrastructure changes, developer improvements and bug fixes. Notable changes since June 15 include:
- Official renaming of the server software from rippled to xrpld.
- New configuration paths, server metadata, database directory locations and version naming conventions — requiring operators to update deployment scripts and server configs.
- Developer conveniences, including the ability to access protocol info and server definitions without running a full server (useful for wallets, APIs and explorers).
fixCleanup3_2_0 amendment: security and cleanup
The release also introduced the fixCleanup3_2_0 amendment, which targets multiple security and ledger-integrity issues:
- Fixes for Single Asset Vaults, the Lending Protocol, permissioned decentralized exchanges, Multi-Purpose Tokens (MPTs) and permissioned domains.
- New invariant checks to prevent deleted accounts from leaving residual ledger data.
These changes are intended to strengthen security and improve ledger consistency.
Where support stands
Despite broad software adoption growing, support for the fixCleanup3_2_0 amendment is lagging. Current network data shows the amendment has about 40% support — well short of the >80% supermajority required for activation. Ripple has publicly endorsed the amendment, and the Lending Protocol — one of the affected components — recently passed an independent security audit, which should bolster confidence in the fixes.
Operational hiccups to watch
Developers are monitoring migration-related issues reported by node operators. One GitHub ticket (report #7581) describes a case where the service log showed the updated validator public key, while the running server continued using the older key stored in the wallet database. The issue appears to be related to migration behavior rather than the protocol itself, underscoring operational steps node operators must take during the transition.
What’s next
Adoption of xrpld v3.2.0 is rising, but the network still needs about 24–25% more of the trusted validator set to upgrade and sustain support for two weeks before the amendment can be activated. Node operators should prioritize updating deployment scripts and configurations to accommodate the renamed server and new paths, and the community will be watching amendment support closely in the coming weeks.
Read more AI-generated news on: undefined/news
