2026

when

Read

In a recent tweet, <a href="https://u.today/ripplex-drops-12-quick-facts-about-xrp-in-buzz-worthy-post-on-x" rel="noopener noreferrer nofollow">RippleX</a> issued a friendly reminder to node operators, urging them to upgrade as a slew of amendments are set to activate on the XRP Ledger mainnet on Tuesday, Jan. 27.
RippleX referred back to its earlier <a href="https://x.com/RippleXDev/status/2014743132613828775" rel="noopener noreferrer nofollow">tweet</a> where it stated that all XRPL version 3.0.0 amendments have been triggered for mainnet adoption. In this light, RippleX stated that it was critical for XRP Ledger node operators or validators to upgrade their software to the current version 3.0.0 to avoid being amendment blocked.
<blockquote class="twitter-tweet">
 Friendly reminder to node operators to upgrade before these amendments activate on Tuesday, January 27 ⬇️ <a href="https://t.co/6N0mzPvi2d" rel="noopener noreferrer nofollow">https://t.co/6N0mzPvi2d</a>— RippleX (@RippleXDev) <a href="https://twitter.com/RippleXDev/status/2014743132613828775?ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow">January 23, 2026</a>
</blockquote>
Amendment blocking is a security feature to protect the accuracy of <a href="https://u.today/18-million-daily-transactions-xrp-ledger-shows-key-growth-per-latest-report" rel="noopener noreferrer nofollow">XRP Ledger</a> data. When an amendment is enabled, servers running earlier versions of rippled without the amendment's source code no longer understand the rules of the network. Rather than for them to guess and misinterpret ledger data, these servers become amendment blocked and may not be able to determine the validity of a ledger, submit or process transactions, participate in the consensus process and vote on future amendments.
<h2 id="what-s-coming">What's coming?</h2>
According to xrpscan data, five fix amendments included in <a href="https://u.today/ripple-backed-evernorth-to-expand-xrpl-adoption" rel="noopener noreferrer nofollow">XRPL</a> version 3.0.0 are set to be activated on the XRP Ledger mainnet with the current countdown now 3 days 7 hours from now.
These amendments include fixTokenEscrowV1, fixIncludeKeyletFields, fixMPTDeliveredAmount, fixAMMClawbackRounding and fixPriceOracleOrder.
The fixTokenEscrowV1 resolves an accounting error in MPT escrows. The fixIncludeKeyletFields amendment includes missing keylet fields for specific ledger entries. The fixPriceOracleOrder resolves an issue where the order of asset pair data was different when a price oracle is created versus when it is updated.
FixAMMClawbackRounding resolves a rounding error that might occur in the LPTokenBalance of an AMM when an AMMClawback transaction is performed. The fixMPTDeliveredAmount amendment includes missing DeliveredAmount and delivered_amount metadata fields from direct MPT Payment transactions.
Permissioned domains, XLS 80 amendment, which represents a compliance building block for institutions, has achieved majority, with its activation on the mainnet expected for Feb. 4. According to xrpscan data, the current countdown for the permissioned domains amendment is 10 days 19 hours. <a href="https://u.today/ripplex-alerts-node-operators-ahead-of-crucial-upgrade-deadline-details" rel="noopener noreferrer nofollow">Read original article on U.Today</a>

RippleX Alerts Node Operators Ahead of Crucial Upgrade Deadline: Details

Table of Contents

U.Today

Other articles published on Jan 24, 2026

Was This Bitcoin Art the First Ever NFT?

Bitcoin Price Surpasses Historical Levels Across 6,230 Days

Veteran Traders Flock To Zero Knowledge Proofs’ (ZKP) 7000x Potential as ETH & ADA Struggle With ...

Ethereum Staking Hits Record High Amid Institutional Demand

Join our free newsletter for daily crypto updates!