XRP Ledger validators briefly lost the required majority for fixCleanup3_4_0 on October 21. Support returned in under two hours, but the protocol restarted the full waiting period for the package of token-permission and DeFi fixes.
XRP Ledger’s fixCleanup3_4_0 bug-fix package will miss its expected October 23 activation date. XRPL Dashboard’s voting history records a loss of the required majority at 12:54 UTC on October 21 and its recovery at 14:46 UTC. The gap lasted one hour and 52 minutes, but the protocol restarted the entire two-week waiting period.
XRPLWin’s October 22 morning snapshot showed 31 of 35 listed trusted validators supporting the package. If sufficient support continues without interruption, the two-week period will end on November 4 at 14:46 UTC. Servers will activate the amendment during the relevant voting cycle after the period expires.
A brief loss of support restarts the two-week wait
Protocol changes on XRPL are voted on by validators that servers trust. Holding XRP alone does not provide an amendment vote. More than 80% of the validators must support a change for two weeks before it activates; a calculation based on 35 validators therefore requires at least 29 votes. Dashboard recorded 26 supporting votes during the October 21 drop.
| Date and time | Recorded status |
|---|---|
| October 9, 2026, 09:34 | The first two-week wait began, pointing to October 23. |
| October 21, 2026, 12:54 | Support fell below the required majority, ending the first wait. |
| October 21, 2026, 14:46 | Sufficient support returned and the clock restarted. |
| November 4, 2026, 14:46 | The new two-week period ends if support holds. |
The two trackers calculate support using different sets of validators. At 08:04 UTC on October 22, XRPLWin showed 31 supporters among 35 validators. Dashboard’s view refreshed at 08:08 UTC showed 31 supporters among the 34 validators from which its own node had received votes, with a threshold of 28. Dashboard still listed 35 validators in the trusted list. The records reviewed do not establish why support fell or which operators withdrew their votes.
Under XRPL’s amendment rules, losing the majority cancels the time already accumulated. Regaining support starts a new period. Servers assess votes every 256 ledgers, a cycle the documentation describes as roughly 15 minutes, and record when a majority is gained or lost. Once the full waiting period has passed, a voting cycle can activate the change.
“Bug fixes that change transaction processes also require amendments.”
XRPL documentation, “Amendments”
Burn permission will no longer allow tokens to be minted
Developers introduced the package in September’s xrpld 3.4.0 announcement. The detailed amendment specification covers token permissions, liquidity pools, vaults, loans and other transaction types. Servers will apply the amendment’s transaction rules on mainnet only after validators provide the required support for the full waiting period.
One delegated-permission flaw could let an account authorised only to burn tokens cross a balance boundary and create new tokens during a payment. The fix rejects a payment made with only PaymentBurn permission if it would cross zero into minting; the delegate would also need PaymentMint. The software will add different prefixes to the data signed by sponsors and counterparties. A digital signature authorising one role will therefore not work for the other.
For deposits into pooled-asset vaults, withdrawals and issuer clawbacks, the software will round amounts more precisely to prevent overpayment or underpayment. It will also check that a loan’s payment date has passed before marking the loan as late, impaired or in default. A withdrawal of a fixed number of shares from a fully impaired vault will also be allowed to deliver zero assets instead of automatically failing.
In automated market maker, or AMM, pools, a clawback will be able to remove the last liquidity provider’s entire position, while amounts that round to zero will be rejected. In pools with no trading fee, users will no longer be able to buy the auctioned trading privilege for a zero or negligible amount. NFT offers will also be rejected if they label a non-XRP amount with the currency code “XRP”.
For permissioned decentralised exchange transactions, the software will check that the specified permission domain exists and remove expired credentials. When funds are returned or delivered from escrow, the escrow owner’s reserve will be released before the payment can recreate an asset holding. Ending a sponsorship will require a check that the sponsored account can meet the reserve requirement itself.
Lending still needs separate amendments to pass
Activating the bug-fix package will not automatically launch XRPL lending. In Dashboard’s same morning view, LendingProtocol and LendingProtocolV1_1 each had 19 votes, while SingleAssetVault had 21. All three were below the tracked node’s 28-vote threshold and had not begun their own two-week waiting periods.
A September 30 explanation by RippleX developer Shota Natenadze says all three amendments must activate for lending to go live. New loan brokers will be restricted to closed-ended vaults: investors deposit during a subscription window, the vault then closes to new deposits while capital is lent out, and withdrawals open during the designated redemption phase. Vaults will recognise interest as income only when it is received, instead of booking all scheduled interest when a loan is originated.
RippleX set out the additional approvals needed for lending in its September 30 post. The announcement preceded the October 21 loss of voting support.
RippleX’s LendingProtocolV1_1 voting announcement
The post loads from X when you open it.
Updating a server and activating a rule are separate steps
Server operators must run software that understands activated rules. XRPL’s documentation says an outdated server that does not support an enabled amendment can no longer perform its normal transaction-processing and validation duties. Voting against a package and failing to install compatible software are separate choices. Developers addressed other bugs in the 3.4.1 security release on September 25. The XRP minting flaw patched in that release is separate from the token-burning permission bug now awaiting approval.
For an explanation of the voting mechanism, XRPL Commons’ official channel offers the eight-minute, 38-second “Consensus & Amendments” lesson published on July 31, 2025. Denis Angell explains how proposals pass through validator voting and become active on the network. The lesson predates the current delay.
November 4 depends on continued support. Another drop below the threshold would restart the two-week wait again. Validators must also provide enough support for each lending and vault amendment and maintain it for two weeks; a firm lending launch date has not been announced.
