The amendment package was on the home stretch, but during another routine check a brief glitch occurred: several servers momentarily lost connection, causing the number of votes to drop to 26. The nodes recovered immediately, and the project is now steadily approved by 31 of the 35 participants.
However, because of the temporary break in the chain, the timer was reset. Developers are taking this calmly: the strict filters guarantee that the network would rather wait than accept code amid an unstable connection.
The update itself is not related to hacker attacks or breaches. This bug-fix amendment is a planned closure of theoretical vulnerabilities in the new protocols:
-
Issuance control: An account with a token-burning function (PaymentBurn) could, under rare conditions, bypass the code logic and launch the issuance of new assets. The loophole has been completely eliminated.
-
Foundation for DeFi and lending: The patch improves the rounding precision of numbers for deposits into future native vaults (Single Asset Vaults) and changes the logic of loan defaults: a delinquency is now recorded strictly after the deadline has passed.
-
Code optimization: Bugs in the operation of AMM (erroneous burning of LP tokens at a zero refund balance), NFTs, and escrow accounts have been fixed.
For ordinary $XRP holders, the postponement changes nothing. Balances, transaction speed, and fees remain the same.
Institutional players also ignored the hiccup. Amid news that Franklin Templeton continues to buy up millions of $XRP for its ETF clients, the token’s price is steadily holding around $1.35. Large capital is satisfied with the uncompromising strictness of XRPL’s automation.
