On October 23, 2026 at 09:34 UTC, the amendment fixCleanup3_4_0 becomes active on the XRP Ledger. If you simply hold or trade XRP, there is nothing to do: balances, addresses and payments already in flight stay as they are. The only people who have to act are those running a node or a validator of their own, because that software has to know the amendment by then.
The bundle is notable for a different reason. Among other things it repairs Single Asset Vaults and the lending protocol, the credit function that has been written about for weeks as a thing of the future. Neither is live on mainnet to this day. The repair, in other words, arrives before the feature it repairs.
What the XRP Ledger does on October 23
An amendment is a change to the rules by which the network checks transactions. The change bites only once enough validators have agreed, and from then on it holds permanently for every subsequent ledger version. Undoing such a change takes another amendment.
fixCleanup3_4_0 carries the identifier 98433DD0…CA76 and reached the required majority on October 9, 2026 at 09:34:30 UTC. That fixes the date exactly two weeks later, October 23 at the same hour.
A look at the ledger itself shows how quiet the network otherwise is: of 107 known features, 97 are active and 10 are not. Among those ten sits exactly one majority entry, and it belongs to fixCleanup3_4_0. The bundle is therefore the only item on the ledger with a clock running at all.
How an amendment takes effect: 80 percent and two weeks
The rule sits in the XRP Ledger documentation and is short: an amendment needs more than 80 percent approval from the trusted validators and has to hold that approval for two weeks. A validator is a server whose vote other participants treat as trustworthy; it confirms transactions and votes on changes of this kind.
The reverse side of the rule matters just as much. If support drops below 80 percent, the amendment is temporarily rejected and the two-week window starts over. An amendment can win and lose a majority as often as it likes before it goes permanently active. October 23 is not a date carved in stone, then, but one that holds only as long as the majority does.
The same pattern ran in September, when the preceding bundle, fixCleanup3_3_0, went live. What applied back then to wallet, node and AMM users is set out in our piece on the amendment activation of September 11. fixCleanup3_1_3, fixCleanup3_2_0 and fixCleanup3_3_0 are all three active by now; the series is routine rather than an exception.
Nothing changes for holders, something does for node operators
The picture splits cleanly in two. Anyone holding XRP on an exchange or in a wallet of their own will notice nothing on October 23: no hard fork, no new address, no token swap, no freeze on deposits and withdrawals. Exchanges and wallet providers run their nodes themselves and keep the software current.
It looks different if you run a rippled server yourself. Should that server be on a version that does not know fixCleanup3_4_0 on the day, it becomes amendment-blocked: it no longer follows consensus and no longer serves reliable data. The safeguard is deliberate, because a server that does not understand the new rules would otherwise spread a divergent view of the ledger.
For almost all readers that means sitting tight. If you hold your XRP through a trading venue, the most this day calls for is a glance at the fees and the licence of that venue; our crypto exchange comparison sets the terms side by side. It has nothing to do with the amendment itself, but it is the only lever a holder can actually pull on that day.
fixCleanup3_4_0 repairs vaults, loans and the permissioned DEX
The bundle is not a single patch but a collection of corrections running right across the protocol. According to the XRP Ledger amendment overview, it touches Single Asset Vaults, the lending protocol, the automated market maker, the permissioned DEX, trust lines, NFTs, multi-purpose tokens, escrow, sponsoring, the transaction signature and rights delegation. The last comparably targeted intervention was the patch to the payment engine at the start of October.
Single Asset Vaults: rounding and the ValidVault rule
A Single Asset Vault is a protocol-level pot into which users deposit a single asset and receive shares in return. The corrections land exactly where decimal places decide who gets money: deposits, withdrawals and clawback will round more precisely, so that a vault pays out neither too much nor too little. A withdrawal at a fixed share quota from a fully impaired vault will be allowed to move zero assets instead of failing with an error. And the ValidVault rule will no longer block a vault change when accrued interest alone pushes past the upper limit.
Lending: default only once the due date has truly passed
In the credit section, a small thing shifts to large effect: the checks for arrears, impairment and default will require the due date to have strictly elapsed. Until now a loan could count as overdue on the due date itself. There is also an exception that exempts a loan default from freeze, deep freeze and MPT lock when the transfer runs from the broker to the vault.
AMM, trust lines, NFTs and escrow
The automated market maker is the protocol’s own trading venue, where buyer and seller do not meet but a pool sets the price. Here a bid will be prevented from taking the auction slot of a fee-free pool at a price of zero or for scattered amounts. With trust lines, the lines of credit through which an account holds foreign currencies, an attempt to create a line that already exists will simply return a duplicate notice instead of running into nothing. NFT offers that use the currency code XRP for a non-XRP amount will be rejected. And with escrow, the protocol’s own trust arrangement, the owner’s reserve will be released before the returned or delivered amount can create a new balance.
One change stands out because it concerns security: sponsor and counterparty signatures get their own signature prefixes. A signature can no longer be moved from one role into the other.
Why the fix arrives before the feature
This is where the real finding lies. The validators’ software has long known the code for vaults and loans: SingleAssetVault, LendingProtocol and LendingProtocolV1_1 are listed in the ledger as supported, which means the features are contained in the shipped server versions. They are still not active, because they lack a majority.
The corrections to those very features, by contrast, are going through first. Technically that makes sense: a bug that costs money only in use should be fixed before use becomes possible at all. For readers it also means the activation on October 23 brings no new feature. The bundle clears the path for features whose start date remains open.
What has changed since October 11
On October 11 the lending amendment stood at 17 of 25 evaluated votes; the arithmetic behind that is in our article on the 17 of 25 votes for the lending amendment. Two things have happened since, and only one of them concerns the credit function.
First, on October 9, two days before that article, fixCleanup3_4_0 cleared the 80 percent threshold and started its clock. Second, as of October 17 the ledger still shows only that one majority entry. Whether the number of yes votes for the lending protocol has risen since, the ledger does not say; it shows only that the threshold was not crossed in those six days. Had it held, a second entry with its own timestamp would be sitting there.
The lending protocol still has no majority
Of the ten features not yet activated, five feed directly into the new financial layer: SingleAssetVault, LendingProtocol, LendingProtocolV1_1, ConfidentialTransfer for confidential transfers and Sponsor for sponsored reserves. All five count as supported; not one has a majority.
That the lending protocol sits in the ledger in two versions, once as LendingProtocol and once as LendingProtocolV1_1, has so far appeared nowhere in German-language coverage. It is a sign that development carried on while the vote was still open.
That yields a calculation anyone can follow: as soon as one of these features reaches a majority, another two weeks pass before activation. Were the majority to come together today, the earliest conceivable start would be October 31, 2026. Since it is not there today, that date moves out with every passing day.
Until then, lending against crypto assets stays what it is now: a business run through platforms and providers rather than through the protocol itself. If that interests you, the terms and the risks are in our crypto lending comparison. Every one of these platforms carries a counterparty risk that a protocol loan would not, and a total loss is possible.
Default vote no: the open question in the documentation
One data point does not fit the picture, and it belongs out in the open. The amendment overview lists the default vote of the latest stable version for fixCleanup3_4_0 as a no. The default vote is what a server casts as long as its operator sets nothing else.
An amendment that reaches a majority although the default vote stands at no allows two readings: either operators set their approval individually, or the documentation page no longer reflects the state of the current server version. Which of the two applies could not be settled from the accessible sources. Also documented is that no feature from the time before the amendment is switched off; nothing disappears.
Our assessment: the order is the signal, not the date
October 23 itself is a maintenance date and worth little as news. The order of events is the interesting part. The evidence: a single majority entry in the ledger, and it belongs to a correction bundle that touches vaults and loans; five features of the same financial layer sit alongside it, supported but undecided. If you follow this development, keep an eye on the next majority entry rather than on this date.
Against reading too much into that order: correction bundles pass on the XRP Ledger regularly, and three predecessors have long been active. A majority for a fix amendment says nothing about when the large features will get one of their own. A price target certainly cannot be derived from it, and none of the figures named here is a recommendation to buy or sell.
XRPL lending: without an 80 percent majority, the credit function stays off
The amendment on October 23 does not concern the vast majority of readers. Three points are still worth a look while the timetable for the credit function stays open:
- Settle custody. Do your XRP sit on an exchange or in your own custody? That makes no difference to protocol changes, but a considerable one to your risk. The devices and how they differ are in the hardware wallet comparison.
- Look at your venue’s licence. For buying and selling in Europe, what counts is whether the provider is authorised under MiCA. Which houses meet that is shown in the overview of regulated crypto exchanges.
- Document your gains. Purchases, sales and earnings belong on record without gaps, because the tax office asks you for the evidence, not the exchange. Suitable tools are in the crypto tax software comparison.
(As of October 17, 2026. This article is not investment advice. Prices and fee structures change; check the terms with the provider before you buy.)
Be the first to comment