The upcoming XRP Ledger 3.1.3 upgrade has triggered fresh discussion across the crypto community after David Schwartz explained why the XRP Ledger experiences more events that can technically resemble hard forks compared to many other blockchain networks.
The debate comes as node operators prepare for the activation of the fixCleanup3_1_3 amendment, which is expected to go live on May 27.
XRPL 3.1.3 upgrade focuses on bug fixes
According to the official XRP Ledger release, version 3.1.3 includes the fixCleanup3_1_3 amendment, which contains fixes related to:
- NFTs
- Permissioned Domains
- Vaults
- Lending Protocol functionality
Because of the nature of the fixes, the amendment’s default validator vote was automatically set to “yes.”
The XRP Ledger development team has urged validators, exchanges, and infrastructure providers to upgrade before the activation deadline to avoid compatibility problems.
Why the XRPL hard fork debate started
Concerns emerged after community members warned that nodes running outdated software could lose normal access to the network once the amendment activates.
This led some users to question whether the upgrade process represents routine maintenance or a form of hard fork risk.
Schwartz addressed the discussion on X, explaining that XRPL experiences more events that are technically considered hard forks because of the network’s architecture and consensus design.
David Schwartz explains XRPL consensus model
Schwartz argued that XRPL’s governance system differs significantly from traditional “one node one vote” systems.
According to him, relying purely on node count could allow bad actors to manipulate the network by creating large numbers of fake validators.
Instead, XRP Ledger consensus depends heavily on the Unique Node List, commonly known as the UNL.
Under the XRPL model:
- Validators rely on trusted validator lists
- Consensus is based on aligned validator agreement
- Network coordination depends on software compatibility and validator trust
Schwartz explained that even if validators split into different groups, both sides would still need enough trusted validators and aligned software to maintain a functioning ledger stream.
No active chain split has occurred
Despite the debate, Schwartz clarified that the discussion does not mean XRP Ledger has experienced a live chain split.
Instead, the conversation highlights how XRPL upgrades rely on:
- Validator coordination
- Software updates
- User adoption of new rules
- Consensus alignment across the network
The system differs from proof-of-work or proof-of-stake blockchains where mining power or staking weight typically determines the dominant chain.
Why the May 27 deadline matters
The upcoming amendment activation is particularly important for:
- Exchanges
- Validators
- Infrastructure providers
- Wallet services
- Projects built on XRPL
Nodes that fail to update before the deadline could:
- Become amendment blocked
- Fall out of sync with the network
- Experience service disruptions
- Lose compatibility with updated ledger rules
Because of this, XRPL developers are encouraging all operators to complete the upgrade before activation.
XRPL continues evolving
The XRP Ledger upgrade reflects the network’s ongoing effort to improve functionality and fix protocol-level issues while supporting growing use cases such as:
- NFTs
- Tokenized assets
- Lending systems
- Permissioned financial applications
At the same time, the debate surrounding technical hard forks shows that governance and coordination remain critical challenges for decentralized blockchain ecosystems.
As XRPL continues expanding its infrastructure, software upgrades and validator alignment will likely remain key areas of discussion within the Ripple and XRP community.
