In this article6 sections
The XRP Ledger’s fixCleanup3_4_0 amendment has reached the 29 validator votes needed for approval and is projected to activate on October 23 at around 09:34 UTC, Crypto.news reported on October 19. The network’s planned lending system is not part of that activation and still lacks the votes to go live.
Crypto.news cited the XRPL Dashboard, which counted support from 29 of the 35 validators on the network’s default trusted list. The amendment cleared the threshold on October 9, starting a mandatory 14-day approval window during which backing must stay above 80%. As of October 19, roughly nine days of that period had elapsed.
Also readXRP Ledger v3.3.0 Upgrade Targets Banks and Tokenized Assets With Five New Features
Key facts
- fixCleanup3_4_0 held exactly 29 of 35 trusted validator votes on the October 19 snapshot, leaving no spare supporters.
- Activation is projected for October 23 at about 09:34 UTC; amendments are decided at flag ledgers, which the network processes every 256 ledgers.
- The LendingProtocol amendment (XLS-66) had 19 votes, ten short of the 29 needed.
- SingleAssetVault (XLS-65), which would hold funds used for loans, had 21 votes, eight short.
- XRPL developers released xrpld version 3.4.0 on September 16 and told operators to upgrade to stay compatible.
A voting margin with no room to spare
Because support sits exactly at the minimum, a single validator withdrawing would push the proposal below the required majority. Under XRPL rules, the two-week countdown would restart once sufficient support returned. Crypto.news stressed that the October 23 date is a projection, not confirmation that the update is live.
Servers running older software without code for approved amendments can become amendment-blocked once the network enforces new rules. Version 3.4.0 also shifts how compatible packages are distributed, with signed Linux installers issued through the XRPL Foundation.
Also readAvalanche founder warns AI could expose XRP Ledger bugs
What the fix actually repairs
The package addresses automated market maker recovery transactions that could destroy a user’s liquidity-provider tokens when rounding left no underlying assets recovered, according to Crypto.news. It also adjusts vault deposit and withdrawal calculations so asset balances and share counts stay consistent, and updates lending rules covering authorization, frozen assets, credentials and payment destinations. Other changes touch permissioned decentralized exchange transactions, NFT offers, escrow processing and signature prefixes.
News.bitcoin reported a separate flaw the upgrade closes: a feature called PermissionDelegationV1_1, activated October 8, lets an account hand limited authority to another account. One permission, PaymentBurn, is meant to let a delegate destroy certain tokens, but under specific conditions a software defect could let those tokens be created instead. Official XRPL documentation warned operators against granting that permission until the cleanup amendment activates, News.bitcoin reported. Crypto.news did not describe this flaw.
Lending waits on three separate votes
The lending design pools depositor assets in a shared vault, with a loan broker arranging fixed-term loans and assessing borrowers offchain. Borrowers would not post collateral directly through the protocol; brokers would judge creditworthiness and terms. An optional first-loss capital mechanism could see a broker place assets in a separate account to absorb defaults, though it would not guarantee full recovery for depositors. XRPL documentation states the protocol has no automatic on-chain collateral management or liquidation, and brokers could declare a loan in default after a missed payment and the grace period.
A third amendment, LendingProtocolV1_1, had 19 votes. Introduced in version 3.4.0, it would require new loan brokers to use closed-ended vaults with subscription, investment and redemption stages, and would recognize interest revenue when borrowers actually pay rather than when a loan is booked.
The vote tallies differ slightly between the two reports. Crypto.news, citing the XRPL Dashboard, recorded 29 votes for the cleanup, 19 for LendingProtocol and 21 for SingleAssetVault. News.bitcoin, citing XRPSCAN tracking for October 15-17, described 26 to 29 supporters for the cleanup out of 32 to 35 validators and roughly 17 to 19 for the lending amendments, with SingleAssetVault at around 19 to 21.
Why it matters
Even if the lending amendments hit 29 votes immediately, the two-week waiting rule means they could not activate alongside the October 23 package. The ledger processes amendment decisions on its own schedule, so the maintenance work can land well before the financial product it partly supports. Ripple backed both lending amendments through its validator in August while they sat below the threshold, and a June security re-audit of the lending changes by Halborn reported no critical or high-risk findings — which did not constitute network approval.
What to watch
Validator support for fixCleanup3_4_0 through the remainder of the approval window: any defection before the flag ledger resets the countdown. Separately, watch whether LendingProtocol and SingleAssetVault close the gap to 29 votes, which would begin their own 14-day periods.
Sources: crypto.news, News.bitcoin
