Key Takeaways Cleanup sits at exactly 29 votes. Eight of about 25 fixes concern lending. Closed-ended vaults lock funds while loans run. First-loss capital may absorb little. How XRPL lending
Lending on XRPL would run through a vault, a broker and borrowers. Depositors put one asset into a Single Asset Vault, a loan broker arranges fixed-term, uncollateralised loans from that pool, and borrowers repay under agreed terms, according to the XRPL lending documentation. The ledger administers the loans, but underwriting happens off-chain, and the current design has no automated on-chain collateral liquidation. Our earlier look at XRPL native lending covers the proposal.
The XRPL Dashboard’s October 18 snapshot showed 29 of 35 monitored validators backing fixCleanup3_4_0. The ledger has recorded its majority since October 9, and the dashboard projects activation on October 23 at about 09:34 UTC if support holds for the full two-week window. It flags the amendment as having “no votes to spare.”
Validators backing each amendment, October 18
Bars show the 35 validators the dashboard monitors. The red line marks the 29 needed.
fixCleanup3_4_0 29 · at the line SingleAssetVault 21 · 8 short LendingProtocol 19 · 10 short LendingProtocolV1_1 19 · 10 shortSource: XRPL Dashboard.
The line sits at 29 because the rule needs strictly more than 80% of trusted validators, so 28 of 35 isn’t enough, the dashboard notes. PermissionDelegationV1_1 lost its majority at 28 of 35 on September 23, and BatchV1_1 lost it for one roll call on September 25, which restarted its clock before it was enabled on October 9. Under the official process, a lost majority resets the two weeks.
The lending amendments need 8 to 10 more votes, and then a 14-day hold, so none of them can activate before early November at the earliest.
One caveat applies to the counts. A report filed on October 8 on the rippled GitHub repository says version 3.4.1 stops counting a validator’s votes after it rotates its signing key and drops it from the threshold. The reporter saw 33 validations and a threshold of 26, not 35 and 28, and noted no amendment’s outcome differed, Unchained reported. A patch was open for review as of October 9.
The cleanup is not mainly a lending patch. The XRPL list for fixCleanup3_4_0 has about 25 items, and eight concern vaults and loans. The rest touch AMMs, trust lines, NFTs, Multi-Purpose Tokens, escrow, sponsorship signing and permission delegation, so it changes live behaviour for users with no interest in lending.
TRUST LINES
An issuer’s block on incoming trust lines now also applies to offers, so an account can no longer receive tokens through one.
AMM CLAWBACKS
A clawback no longer burns a holder’s pool tokens while recovering nothing when rounding floors the amount to zero.
ESCROW
Cancelling or finishing an escrow that returns tokens no longer fails when the owner sits at the reserve boundary.
SIGNATURES
Sponsor and counterparty signatures get distinct prefixes, so one made for a role can’t be replayed as the other.
Source: xrpld 3.4.0 release notes.
It also affects a feature that went live on October 8. XRPL’s documentation advises against delegating the granular PaymentBurn permission until the cleanup is enabled, because a delegate holding it may be able to create new trust-line tokens or Multi-Purpose Tokens, not just destroy them, Unchained reported. The cleanup rejects PaymentBurn-only payments that would cross a zero balance into a mint.
Vault shares are Multi-Purpose Tokens whose value follows the vault’s assets, and the ledger tracks an “unrealised loss” on loans marked impaired. In the vault documentation’s example, a $1.0 million vault with a $900,000 unrealised loss has a withdrawal exchange rate of 0.1.
The cleanup makes three changes there. Deposits, withdrawals and clawbacks round more precisely, so a vault’s total assets, available assets and share supply stay consistent. A fixed-share withdrawal from a fully impaired vault can move zero assets rather than fail, which completes without recovering any money, and the release notes don’t say why that replaced a failure. Loan lateness, impairment and default checks now require the due date to have strictly passed, so a loan can’t be flagged on the due date itself.
This is the fourth cleanup amendment aimed at that code. The vault documentation says fixCleanup3_1_3 through fixCleanup3_4_0 each made precision, rounding or correctness fixes to vault behaviour after its 2025 audit.
READ MORE:
Winning Ohio Won’t Save CLARITY – It Needs 7+ Democrats
LendingProtocolV1_1, introduced in 3.4.0, changes how a vault counts interest. Before it, a vault counted a loan’s full scheduled interest as income the moment the loan was originated, and had to unwind it if the borrower stopped paying. In the lending documentation’s example, a vault with 99,000 available tokens and a 1,000-token loan carrying 90 tokens of scheduled interest reports 100,090 in total assets. With cash-basis accounting, interest counts only when a payment delivers it, so share prices aren’t marked up on scheduled income, and losses show smaller because only principal is at risk.
The same amendment adds closed-ended vaults. They move through three phases on dates fixed at creation that can’t be changed, and once V1.1 is enabled, new loan brokers can only use them.
1 · Subscription Deposits ✓ Withdrawals ✓ The fundraising window. → 2 · Investment Deposits ✗ Withdrawals ✗ Assets are lent out. → 3 · Redemption Deposits ✗ Withdrawals ✓ Loans have matured.Source: XRPL Single Asset Vault documentation.
Which accounting model a vault gets depends on when it is created. Vaults created before V1.1 activates keep the old interest model permanently, even afterwards, the documentation says, and it allows for a gap between the two activations. LendingProtocol and V1.1 sit at the same 19 votes, but nothing guarantees they activate together.
A broker can post optional first-loss capital, but two settings cap how much of it reaches a default. CoverRateMinimum is the share of debt that must be covered, and CoverRateLiquidation limits how much of that minimum goes to the vault when a loan defaults. In the lending documentation’s example, a broker posts 1,000 tokens of cover and a 1,090-token loan defaults. With both rates at 10%, only 10.9 tokens of cover are applied, and the vault absorbs a 1,079.1-token loss.
One default, in tokens
Loan defaults 1,090 Cover posted 1,000 Cover applied 10.9 Vault loss 1,079.1Documentation example with both rates at 10%. Brokers set the rates, so real pools will differ. Source: XRPL Lending Protocol documentation.
If available cover falls below the minimum, the broker can’t issue new loans, and its fees go into the cover. That limits new exposure, but it doesn’t make an existing borrower repay.
Asset issuers hold levers too. If a vault’s asset is frozen, withdrawals can only go to the issuer, and issuers can claw back vault shares into assets sent to them. A frozen borrower can’t make payments, which doesn’t cancel the debt.
This article is provided for informational purposes only and does not constitute financial or investment advice. Amendment schedules can change, and lending involves credit and liquidity risk.
The post XRP Ledger’s Cleanup Has No Votes to Spare: Lending Is Short appeared first on Coindoo.
