RippleX has issued an urgent notice to XRP Ledger node operators and validators, warning that servers must upgrade to rippled version 3.0.0 before Tuesday, January 27, 2026.
Nodes that miss the deadline face being amendment-blocked, a safeguard that removes outdated software from active participation once new consensus rules take effect.
Amendment-blocked servers are effectively sidelined. They can no longer determine ledger validity, submit or process transactions, or participate in consensus and future amendment voting. The cutoff is tied to protocol changes that have already met the network’s activation threshold.
What Changes With rippled 3.0.0
Version 3.0.0 activates multiple amendments that reached the required 80% approval from trusted validators. The updates focus on correctness and standardization across token, AMM, and oracle mechanics.
Specifically, the release addresses an escrow accounting issue affecting Multi-Purpose Tokens, corrects rounding behavior for LP token balances during AMM clawbacks, standardizes price-oracle pair ordering, and adds missing metadata that summarizes the actual delivered amount in MPT payment transactions.
Together, these fixes reduce edge-case risk and align data handling across the ledger, which is why older nodes become incompatible once the amendments activate.
Operational Risk for Unpatched Infrastructure
The urgency reflects recent experience. During the December 2025 update cycle, nearly 45% of nodes were at risk of disconnection before upgrading.
RippleX is again urging exchanges to verify node status, noting that outdated infrastructure can degrade deposit and withdrawal processing even if the broader network remains healthy.
Looking Ahead to 2026 Features
Beyond immediate fixes, rippled 3.0.0 ships code paths for upcoming “Smart Features,” including the Lending Protocoland Dynamic MPTs, which are expected to open for validator voting later in Q1 2026.
While those features are not activated by this release, the upgrade positions nodes to participate once governance moves forward.
Detailed upgrade steps and official release notes are available on the XRP Ledger blog. For operators, the message is straightforward: upgrading before January 27 is required to remain in sync with consensus and fully operational on XRPL.
