Disclaimer: The opinions expressed by our writers are their own and do not represent the views of U.Today. The financial and market information provided on U.Today is intended for informational purposes only. U.Today is not liable for any financial losses incurred while trading cryptocurrencies. Conduct your own research by contacting financial experts before making any investment decisions. We believe that all content is accurate as of the date of publication, but certain offers mentioned may no longer be available.
XRP Ledger node operators are facing an important upgrade following the latest xrpld version 3.3.0 release.
This has prompted a new alert for network participants, with node operators urged to update their nodes to stay aligned with the latest improvements and fixes. The upgrade push comes as XRPL 3.3.0 gains adoption across the network.
More than 60% of XRP Ledger nodes had already upgraded to the new xrpld version, according to a recent post by XRP Ledger Operations, an X account dedicated to sharing XRP Ledger infrastructure and software updates.
The alert for node operators remains essential to avoid amendment blocking, a security feature to protect the accuracy of XRP Ledger data.
When an amendment is enabled, servers running earlier versions of xrpld without the amendment's source code no longer understand the rules of the network. Rather than guess and misinterpret ledger data, these servers become amendment-blocked and can't determine the validity of a ledger, submit or process transactions, participate in the consensus process, or vote on future amendments.
The XRPL 3.3.0 release introduces several new amendments alongside bug fixes and build improvements. The new amendments are BatchV1_1: Atomic batch transactions (XLS-56); ConfidentialTransfer: Privacy-preserving Multi-Purpose Token transfers (XLS-0096); DynamicMPT: Multi-Purpose Token properties that issuers can make permanently immutable (XLS-94); PermissionDelegationV1_1: Granular account permission delegation; Sponsor: Reserve and transaction sponsoring (XLS-68); fixCleanup3_3_0, a bundle of amendment-gated bug fixes; all of these are up for voting.
fixCleanup3_3_0 hits 68% consensus
The fixCleanup3_3_0 amendment, a collection of fixes for Single Asset Vaults, the Lending Protocol, Automated Market Makers, the permissioned DEX, Checks, and pseudo-accounts, has reached 68.57% consensus, with less than 12% needed for it to reach the required 80% threshold.
Changes in the fixCleanup3_3_0 include fixes for hybrid offers being removed from the open order book when the account that placed them loses access to the permissioned domain; fixes for Automated Market Maker liquidity being included in quality estimates for permissioned DEX order books; and additional precision and rounding fixes for Single Asset Vaults and the Lending Protocol, among others.
Arman Shirinyan
Dan Burgin
