- XRP Ledger 2.6.2 update activated a mandatory network amendment
- Outdated XRPL nodes became amendment blocked after December 18
- XRP users may see exchange issues if platforms fail to upgrade
The XRP users of centralized exchanges have been given a major warning with the XRP Ledger 2.6.2 update that has blocked a great number of network node amendments. XRPL validator Vet raised the alarm and warned that service interruptions with XRP deposits or withdrawals are probably due to exchanges using older XRP Ledger software.
The XRP Ledger 2.6.2 release brought about an important protocol change that necessitates the upgrading of all nodes participating in the network to ensure that they do not become fully functional on it.
Blocking of old XRPL nodes before the deadline of December 18.
The problem emerged into the limelight of attention upon the complaints of numerous users who testified of delays in transactions, which were associated with the updates of the infrastructure of the key cryptocurrency platforms. Validators made it clear that the failure is not caused by the XRP Ledger itself, but only by nodes that did not upgrade before the deadline of the amendment.
On December 18, the Fix Directory Limit amendment was turned on, and the XRP Ledger 2.6.2 update became obligatory. As of that time, approximately 45% of XRP Ledger nodes were still running on older versions, which means that they were susceptible to amendment blocking (vet). Amendment blocking is an inbuilt security system that maintains the accuracy of the ledger in the case of protocol amendments.
Coinbase XRP service disruptions linked to XRPL 2.6.2 upgrade timing
With an amendment coming into effect, nodes with older copies of rippled do not have the code required to read the new rules of the ledgers. Rather than authenticating possibly false information, such nodes independently discontinue authenticating ledgers, putting forward transactions, or consensus. Consequently, transactions with old nodes might fail to work well with the XRP transactions.
Vet also noted that Coinbase announced poor performance of XRP deposits and withdrawals around the same time that the XRP Ledger 2.6.2 update had been released. The time indicated that not all exchange infrastructure would have migrated to the new XRPL software by the time the amendment was switched on.
Coinbase platform expansion highlights need for timely XRPL node updates
On December 17, Coinbase announced a more comprehensive system upgrade and expanded its platform to support tokenized stocks, prediction markets, and assets of a decentralized exchange on the Solana ecosystem. The exchange also introduced Coinbase Tokenize, an institutional product meant to take real-world assets on-chain. Although these updates did not have a direct connection with XRPL, the possibility of these two updates coinciding indicated the significance of coordinated node upgrades.
XRPL validators are still encouraging exchanges and server operators to ensure that their XRP Ledger nodes are maintained. Nodes are unable to support XRP transactions fairly with amendments that introduce new ledger data unless they are upgraded to support Rippled 2.6.2 or later.
