fixCleanup3_4_0 holds majority since 21 October, could activate 4 November
Victoria Shinder1 min readThe fixCleanup3_4_0 amendment has held a supermajority of validator votes on the XRP Ledger since 21 October. A feature query against a public XRPL server on 28 October returns a majority timestamp of 845,909,182 seconds in Ripple epoch, which is 21 October 2026 at 14:46 UTC. Under the amendment process an amendment activates once it has kept more than 80% support for two weeks, so the earliest activation is 4 November at about 14:46 UTC. If support drops below the threshold in the meantime, the clock resets.
According to the xrpl.org known-amendments page, fixCleanup3_4_0 is a collection of fixes across single-asset vaults, the lending protocol, AMMs, the permissioned DEX, trust lines, NFTs, MPTs, escrow, sponsorship, transaction signing and permission delegation. Examples from that list: VaultDeposit, VaultWithdraw and VaultClawback round more precisely so vault assets cannot over- or under-deliver; loan lateness, impairment and default checks require the due date to have strictly passed; AMMBid can no longer win the auction slot at a zero or dust price on a zero-fee pool; AMMDeposit and AMMWithdraw return tecAMM_FAILED instead of tefEXCEPTION for an out-of-range amount; an all-zero credential ID is rejected as malformed; and creating a trust line that already exists returns tecDUPLICATE as a no-op.
The same page lists the amendment's default vote in the latest stable release as No, meaning validators must opt in explicitly.
What it means
A default-No amendment reaching majority means operators chose to vote for it, not that they upgraded and accepted a default. Applications that depend on the exact old behaviour — an error code they match on, a rounding result they test against, a duplicate trust-line create that used to fail — have about a week to check. Two weeks is a floor, not a date: watch the majority field, not the calendar.