The XRP Ledger community is experiencing heightened debate over whether the 3.1.3 upgrade amounts to a hard fork, with infrastructure operators warning of potential network disruption. According to recent reports, 60% of the network may be forked off as of early upgrade figures, sparking governance questions about who determines XRP mainnet protocol. The controversy centers on the fixCleanup3_1_3 amendment included in version 3.1.3, which addresses critical issues in NFTs, Permissioned Domains, Vaults, and the Lending Protocol. As reported by crypto.news, Ripple CTO Emeritus David Schwartz has addressed the controversy, explaining why XRPL experiences more technical hard fork events than most established public blockchains. The amendment's default vote is set to 'Yes' due to the nature of the essential fixes, with validators requiring immediate updates before the nine-day deadline to maintain network compatibility.
Schwartz linked XRPL's higher frequency of technical hard forks to the platform's design and use of smart transactors. As reported by crypto.news, he pushed back against a simple 'one node one vote' model, stating that someone could create multiple nodes to manipulate such a system. The CTO emphasized that raw node count alone does not determine which chain becomes the main ledger in case of a split, as each side would need sufficient validators to create a working Unique Node List (UNL) with validators agreeing on a ledger stream. According to CoinCentral, Schwartz rejected the idea of a simple voting system where each node has equal weight, explaining that such a model would allow manipulation through large numbers of fake nodes, describing this risk as a Sybil attack. As confirmed by Schwartz, XRPL has more events that are technically hard forks than most other established public ledgers, mostly due to its unique positioning and use of smart transactors.
The nine-day deadline has raised significant concerns among community members as older nodes face potential disconnection from the network. According to the latest reports, 44% of the network had upgraded as of recent updates, with RippleX head of engineering J. Ayo Akinyele urging operators to move quickly, stating 'Only 8 days left before the fix amendment activates — don't be left out!' The technical consequence for outdated servers remains material, as servers running earlier versions without the amendment code cannot determine ledger validity, submit or process transactions, participate in consensus, or vote on future amendments. As of May 18, only 40% of the network had successfully updated to version 3.1.3, highlighting the urgency of the upgrade deadline. The current upgrade centers on bug fixes rather than new market features, with validators must updating before the deadline to maintain compatibility with the network.
XRPL community members are defending the upgrade process as amendment blocking rather than a hard fork, emphasizing its security benefits. According to XRPL.org, the amendment system requires more than 80% support from trusted validators for two weeks before permanent implementation, with the mechanism designed to protect data accuracy when old software no longer understands active network rules. Daniel Keller, CTO of Eminence, argued that raw node counts may overstate operational risk, questioning 'how many of them actually matter to XRPL operations?' and 'how many are abandoned?' He framed the cutoff as 'maintenance discipline rather than a decentralization failure,' stating that running a node is a responsibility, not participation trophy. Krippenreiter emphasized that 'forking has a negative connotation because it sounds like the network is less secure, when in reality, the amendment block mechanism itself is a security feature' designed to prevent transaction data misinterpretation by unupdated nodes.
