The XRP Ledger has taken another step toward expanding its financial functionality with the rollout of XRPL version 3.1.0. Shortly after the update went live, the network formally pushed its native on-chain lending feature into the validator voting phase, a feature that could boost the ledger’s capabilities and attract more institutional use.
A Technical Fix With Multiple Implications
The XRP Ledger has had major improvements with the latest release of RippleD (xrplD) v3.1.0. According to notes of the release, the latest release contains the fix of fixBatchInnerSigs and new amendments of SingleAssetVault and LendingProtocol, both of which must be enabled for the Lending Protocol to be fully usable.
Among the elements included in the v3.1.0 release, one stands out for its potential impact on lending protocols. The “fixBatchInnerSigs” amendment corrects a signature validation flaw in the batch transaction mechanism of the Ledger. Since lending operations often involve multiple steps, such as checking collateral, moving funds, and updating balances, there is a need to make sure that these actions run securely.
The fixBatchInnerSigs amendment seeks to make these batch processes safe and dependable, clearing a technical hurdle that might have deterred larger lending applications until now. The new protocol will include fixed-rate, fixed-term credit at the ledger level, using Single Asset Vaults to isolate risk and replicate TradFi lending protocols.
As noted by the Ledger validator Vet on the social media platform X, the lending protocol will allow for native on-chain lending and borrowing for XRP, RLUSD, and any other issued asset on-chain. This approach would allow users and institutions to access credit using XRP or RLUSD, while reducing the complexity and additional risk layers that often come with third-party contract systems.
That said, the amendment has not yet been activated. It is currently open for validator voting, a process that requires more than 80% of trusted validators to vote in favor and maintain that level of support for two consecutive weeks before activation can occur. As of the time of writing, the approval threshold has not yet been reached, meaning there isn’t a defined timeline for the amendment to go live.
XRPL’s Continued Path Of Network Upgrades
Developers are always rolling in updates and amendments as part of efforts to bolster the XRP ecosystem and its real-world utility. Notably, these recent amendments come on the heels of five other amendments that were announced in December 2025. Node operators running versions earlier than 3.0 have been advised to upgrade to version 3.1.0, as remaining on older software will eventually prevent them from maintaining communication with the network.
Validators are still in the process of voting on the permissionless domains proposal. Current voting trends show validators are already voting for approval. If momentum holds, the amendment is expected to pass on February 4, 2026.
