Don't want to trade it yourself?
Our desk runs DEX portfolios on profit share.
- XRPL activated fixCleanup3_3_0, bringing corrections for transaction handling, AMMs, vaults, lending, Checks and pseudo-accounts into live rules.
- Servers lacking support can become amendment blocked, losing the ability to validate ledgers, process transactions or participate in consensus.
- Native Lending Protocol and other version 3.3.0 features remain disabled, awaiting separate validator-approved amendments for activation.
The XRP Ledger activated a package of fixes for transaction handling, AMMs, and newer protocol features, putting outdated servers at risk.
The fixCleanup3_3_0 amendment went live Sept. 11 at 11:29 UTC in validated ledger 106,911,489 Ripple’s public XRP Ledger endpoint showed the amendment enabled and supported on Sept. 12
The update bundles maintenance corrections involving Checks, automated <a href="https://xpertsstudio.com/from-bear-market-to-w-group/” title=”from bear market to W Group”>market makers, pseudo-accounts, permissioned trading, Single Asset Vaults, and the Lending Protocol as part of the network’s live rules.
Several changes target transaction paths that could previously fail in edge cases. CheckCash and CheckCancel now reject an all-zero CheckID during preflight with temMALFORMED, while a narrow divide-by-zero condition involving AMMWithdraw returns tecAMM_FAILED instead of ending in tefEXCEPTION.
Other fixes adjust freeze handling for transfers involving pseudo-accounts and tighten safeguards around AMMs, permissioned markets and cleanup processes, according to the XRPL amendment registry.
The code supporting those changes has been available since xrpld 3.3.0 was released Aug. 6. Their activation this week marks the point when they shifted from optional software support into rules that servers must understand to remain fully compatible with the ledger.
The fixes now carry consequences for outdated servers
XRPL’s amendment system allows new code to be distributed before validators make it part of the network’s consensus rules. Once an amendment secures the required majority for the prescribed period and activates, servers that do not support it can become amendment blocked.
That creates the immediate operational issue for exchanges, custodians, payment companies and other businesses running their own XRP Ledger infrastructure.
XRPL documentation says an amendment-blocked server cannot determine whether ledgers are valid, submit or process transactions, or participate in consensus. Restoring those functions requires software that supports the active amendment, with the project recommending operators use the latest appropriate xrpld release.
XRPSCAN reported 31 of 35 validations supporting fixCleanup3_3_0 against a threshold of 28 at 01:45 UTC on Sept. 12, after the amendment completed its two-week majority period.
XRP lending model leaves depositors with 90% of a bad loan’s loss despite reserves twice its size
The activation does not mean every feature included alongside the fixes in version 3.3.0 is now live.
Separate amendments covering LendingProtocol, SingleAssetVault, BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1 and Sponsor remained disabled on Sept. 12. Ripple’s public server reported support for those amendments, meaning the software can recognize them even though validators have not yet made them active network rules.
For users relying on maintained wallets or exchanges, the compatibility work largely sits with service providers. Firms operating their own XRPL servers now face the more immediate requirement of keeping those systems current as validator-approved amendments move from available code into the ledger’s active rule set.
Related AssetXRP#5XRP$1.3724-hour change: down1.75%Loading price history…24HDown1.75%7DDown3.26%30DUp35.88%Related CompanyRippleFinancial technology and enterprise blockchain company
FeaturedTechnologyXRP
Editorial credits
Source: cryptoslate.com