The XRP Ledger is preparing to activate the fixCleanup3_4_0 amendment around 09:34 UTC on October 23, 2026. This package, introduced in xrpld version 3.4.0 and released on September 17, bundles a series of amendment-gated corrections.
It currently holds the minimum validator support required for activation and is nine days into its mandatory two-week confirmation window.
Under the ledger’s amendment process, a proposed change must receive more than 80 percent support from trusted validators—typically 29 of approximately 35 nodes—and maintain that level continuously for 14 days. fixCleanup3_4_0 reached majority on October 9 and sits at exactly 29 votes as of mid-October.
The absence of surplus support means that the withdrawal of any single validator would restart the countdown.
Server operators must upgrade to compatible software to continue participating in consensus after activation.
Several corrections within the package refine behavior related to the proposed Single Asset Vault and Lending Protocol features.
These include precision and rounding adjustments for vault deposits, withdrawals, and clawbacks so that tracked total assets, available balances, and share supply remain consistent.
The amendment also refines freeze, authorization, credential, and destination handling for vaults and loans.
In the lending logic, checks for arrears, impairment, and default now require that a loan’s due date has strictly passed.
Separately, the package closes a gap involving the PaymentBurn granular permission: an account authorized only to destroy tokens could previously create new trust-line tokens or multi-purpose tokens under certain conditions.
Additional fixes extend beyond lending.
The asfDisallowIncomingTrustline flag now applies to OfferCreate transactions.
Deleted domain offers are excluded from the permissioned decentralized exchange invariant.
AMMClawback no longer silently recovers zero amounts when multi-purpose token rounding floors a value, and it can bypass owner-reserve checks when auto-creating a paired holding.
Multi-purpose token balance and transfer invariants are now enforced rather than log-only.
Distinct signing hash prefixes prevent a signature created for a counterparty role from being reused as a sponsor signature.
Escrow cancellation and finish operations recycle the owner reserve so that returning issued tokens at the reserve boundary no longer fails.
Activation of these corrections does not enable the native lending system.
The LendingProtocol, LendingProtocolV1_1, and SingleAssetVault amendments remain below the activation threshold, with recent counts showing roughly 19 votes for the lending amendments and 21 for SingleAssetVault.
None has entered a countdown.
Even if those amendments reached 29 votes immediately, the two-week confirmation period would push the earliest possible activation into early November.
xrpld 3.4.0 also introduced LendingProtocolV1_1, which adds closed-ended vaults with subscription, investment, and redemption phases plus a cash-basis accounting model that recognizes interest only when payments are received.
The cleanup amendment addresses issues in code that is not yet live on mainnet while also hardening several active features. Most holders and traders require no action; only node and validator operators need to ensure their software supports the upcoming rules.
