XRP Ledger Activates Lending Protocol Foundation With 3.4.0 Upgrade
XRP Ledger activated version 3.4.0, introducing LendingProtocolV1_1 and closed-ended vaults alongside a bundled protocol-fix amendment. The upgrade provides infrastructure for an upcoming lending product while correcting code paths across AMM, vault, lending, and Checks features.
Written by CoinArticle’s AI Newsroom · from 2 cited sources. How we work
Lending Protocol and Core Upgrades
XRP Ledger has activated version 3.4.0, which introduces LendingProtocolV1_1 and closed-ended vaults alongside cash-basis accounting. The upgrade represents the foundation layer for a broader lending protocol feature set that the network is preparing to ship. According to reports, the version also bundles a protocol-fix amendment for server implementations, though the specific mechanics differ slightly between sources: one describes the fix as a separate activation (fixCleanup3_3_0) correcting AMM, vault, lending, Checks, and pseudo-account code paths, while another characterizes the fixes as included within the 3.4.0 release itself.
Activation and Timeline
The activation was quiet, without a major announcement coordinated across official channels, according to reporting. The upgrade is now live on the ledger, and node operators have begun running the new version. No official timeline has been announced for when the full lending product will launch beyond the foundation now in place.
Why It Matters
For Traders
Lending protocol activation removes a key development blocker for XRP Ledger DeFi, though product launch timing remains unannounced and uncertain.
For Investors
A functioning lending protocol expands XRPL's DeFi ecosystem and use cases, potentially attracting TVL that currently concentrates on Ethereum and Solana.
For Builders
Developers can now integrate closed-ended vaults and cash-basis accounting into dApps, though the full API surface for lending will likely stabilize in subsequent releases.
This article is for information only and is not financial advice. Read the full disclaimer.
