Ripple CTO Explains Why XRPL Faces More Hard Forks Before May 27 Deadline

by

<a href="https://jpyeur.com/xrp-usd/">Ripple</a> CTO explains XRPL hard forks before 3.1.3 deadline

The next update to the XRP Ledger, version 3.1.3, is generating discussion after Ripple’s former Chief Technology Officer, David Schwartz, clarified why the XRPL often experiences events that appear to be major, disruptive upgrades – known as “technical hard forks.”

Summary

  • David Schwartz said XRPL has more “technical hard forks” than most established public ledgers.
  • XRPL 3.1.3 includes fixCleanup3_1_3 for NFTs, Permissioned Domains, Vaults, and Lending Protocol.
  • Nodes that miss the May 27 upgrade deadline may face amendment blocking and service disruption.

The XRP Ledger is preparing to update to version 3.1.3, which includes a fix called ‘fixCleanup3_1_3’. According to the official announcement, this update resolves issues with NFTs, Permissioned Domains, Vaults, and the Lending Protocol. Because these fixes are important, the update was automatically set to be approved.

As crypto.news reported earlier, the update began a two-week activation phase and is planned to go live on May 27th. Network operators will need to update their systems to comply with the new rules.

Some community members are worried about the deadline because older systems might stop working properly once the update is applied. This has sparked a discussion about whether the update is simply standard upkeep or a potentially disruptive change to the system.

David Schwartz explains XRPL hard forks

During a discussion about X, Schwartz pointed out that the XRPL has undergone more significant, fundamental changes – what are known as ‘hard forks’ – than many older, well-known blockchains. He explained this is due to the way XRPL is built and how it utilizes ‘smart transactors’.

I’ve been following the discussions about how to govern these crypto networks, and one idea – where each node gets a single vote – doesn’t really sit right with me. David Schwartz pointed out something crucial: it’s way too easy to exploit. Someone could just create a ton of nodes to unfairly influence the voting process, and nobody wants that.

He explained that how the XRP Ledger manages agreement between nodes is key. He believes simply having the most nodes doesn’t guarantee which version of the ledger will be considered the official one if the network divides.

XRPL validator split and UNL debate

According to Schwartz, simply dividing the validators isn’t enough to determine the result. He explained that both sides would need a sufficient number of validators to establish a functioning Unique Node List (UNL) – a group of validators that all agree on the transaction history.

This is important because the XRP Ledger relies on lists of trusted validators to confirm transactions, instead of methods like mining or staking. If different groups of users were to operate by different rules, they would also need to agree on the same list of trusted validators and use the same software to continue creating and verifying the ledger.

This discussion doesn’t indicate the network has split. It highlights that updates to the XRPL rely on software being updated, validators agreeing on changes, and users deciding which version of the rules to use.

XRPL amendment fixes remain the main focus

This update focuses on resolving technical issues and improving stability, rather than adding new features. According to the official XRPL release notes, it addresses problems with NFTs, Permissioned Domains, Vaults, and the Lending Protocol.

The May 27th deadline is crucial for anyone involved with the XRPL, including exchanges, infrastructure providers, validators, and projects that rely on it. If nodes aren’t updated by then, they might not work correctly with the network anymore.

Read More

2026-05-19 14:47