Ripple Unveils XRPL Lending Protocol: Bringing Credit Infrastructure Onchain, Devnet Testing Now Available

Ripple Unveils XRPL Lending Protocol: Bringing Credit Infrastructure Onchain, Devnet Testing Now Available

N
News Editor
2026-06-29 15:01:56
Ripple推出XRPL借贷协议,旨在将传统信贷基础设施引入区块链,解决链上资产缺乏高效借贷层的痛点。该协议采用独特的架构:信用判断保留在链下由机构执行,链上仅标准化贷款执行与清算逻辑。协议由单一资产金库(XLS-65)和借贷协议(XLS-66)两个互补组件构成,支持抵押贷款、短期流动性融资、做市商库存融资等场景。目前开发者已可在测试网集成测试,最终需经验证者批准。文章深入分析了链上金融缺失的信贷层、协议层设计的优势、机构级风险结构以及XRPL公链的独特价值。
XRPL Lending ProtocolRippleonchain creditDeFiinstitutional lendingXLS-65XLS-66devnet

The XRPL Lending Protocol: Bringing Credit Infrastructure Onchain

Over the past few years, blockchain progress has largely focused on asset representation and transfer, issuing digital instruments, accelerating settlement, and reducing friction in value transfer. Yet moving an asset onchain is only half the job. Real financial markets depend on what happens next: borrowing against assets, using them as collateral, accessing liquidity without having to sell. That layer—lending and credit—barely exists onchain, and its absence prevents tokenized markets from functioning like real capital markets.

As more real-world assets move onchain, including treasuries, money market funds, stablecoins, commodities, and private credit, the question is no longer whether those assets can exist onchain. It is: How do they become productive once they are there? How does a payment provider bridge liquidity between settlement windows? How does a market maker finance inventory without selling assets? How does an institution borrow against onchain holdings using terms its treasury and risk teams can evaluate? This is the problem the XRPL Lending Protocol is designed to solve. The core design principle is deliberate: keep credit judgment off-chain, and standardize execution onchain.

The Missing Layer in Onchain Finance

Tokenization has made real progress. Assets that used to live only inside bank and fund admin systems can now be represented onchain. However, the infrastructure to issue and hold an asset is fundamentally different from the infrastructure to finance against it. In traditional markets, these are separate systems: custody and issuance in one place; financing (repo, margin lending, structured credit, working capital facilities) through another. That second layer is what makes assets productive, not just portable. Most blockchain systems blur these lines. A token gets issued, a lending application gets built around it, another protocol creates its own borrowing rules, liquidation logic, and risk model. This worked for early experimentation, but for institutions evaluating credit activity, the result is fragmented liquidity, inconsistent credit behavior, and risk that must be re-underwritten per protocol. Building a durable credit layer requires treating credit as infrastructure, not as just another application layered on top of the network.

Why Credit Should Live at the Protocol Layer

Blockchains are good at consistently enforcing rules and permanently recording what happened. What they cannot do is make credit judgments—deciding whether a borrower is creditworthy, navigating regulatory requirements, or assessing collateral like a lender would. A blockchain should not replace credit teams, legal documentation, or institution-specific compliance frameworks. Those belong off-chain. What the protocol can do is standardize what happens after a credit decision: how liquidity is pooled, how loans are originated, how interest accrues, how repayment schedules are enforced, how defaults are processed. Most onchain lending systems conflate the two by embedding underwriting assumptions directly into protocol logic, which breaks institutional usability. The XRPL Lending Protocol takes the opposite approach: institutions handle credit judgment off-chain, while the protocol standardizes execution once terms are agreed.

What the XRPL Lending Protocol Makes Possible

The XRPL Lending Protocol is built on two complementary components: Single Asset Vault (XLS-65) — a standardized structure for pooling and managing a single asset onchain; and Lending Protocol (XLS-66) — enabling that pooled liquidity to be originated into loans with defined terms, servicing, and repayment logic. Together they provide an onchain credit foundation. The vault organizes liquidity; the lending protocol puts it to work. This separation mirrors real financial infrastructure: the container holding assets is not the same as the financing mechanism. By preserving that distinction, XRPL can support a wider range of credit structures over time, rather than hard-coding one lending model into a single application. Note: Both components are subject to validator approval.

What This Looks Like in Practice

Consider a payment provider holding RLUSD reserves onchain, but a cross-border settlement won't close for another 48 hours. They need liquidity now to fund outgoing payments. Instead of drawing on an expensive bank credit line or selling assets at the wrong time, they access a short-term working capital facility through a licensed pool administrator, borrowing against expected settlement inflows. The loan terms are agreed upfront; repayment is enforced by the protocol with no manual process, no governance vote, and no ambiguity at maturity. Before access, both lenders and borrowers complete compliance checks; once approved, verifiable credentials determine participation and conditions. This is institutional-grade onchain credit, replacing a bank credit line costing 300-400bps with a transparent, auditable, programmatically enforced facility. It also enables inventory financing for market makers, underwritten facilities backed by digital assets, and more sophisticated structures built on a common execution layer.

Built for Institutional Use

The XRPL Lending Protocol is designed around a simple principle: institutions retain control over credit decisions, while the protocol standardizes execution. Underwriting stays off-chain—institutions already have credit teams, policies, legal documents, collateral agreements, concentration limits, and regulatory obligations. The protocol assumes underwriting is done off-chain; once terms are agreed, the blockchain enforces mechanics. Credit assessment and execution are separate functions and should remain so. Loan behavior is enforced natively onchain: repayment schedules, interest calculations, and default conditions follow predefined rules. Risk teams, auditors, and regulators need to understand system behavior under normal and stressed conditions; standardizing these behaviors at the protocol layer makes evaluation, operation, and trust easier. Risk is structured, not socialized. The protocol supports first-loss capital at the facility level. Pool administrators or underwriters put junior capital at risk ahead of senior liquidity providers, aligning incentives, enabling risk-based pricing, and reflecting typical institutional credit market structures.

Why XRPL: Public Network, Protocol-Level Standards

Institutional credit markets require two often-reconciled things: broad network participation and institutional-grade controls. Public lending protocols like Aave, Compound, Maple, and Clearpool have demonstrated scalability and liquidity, but many were designed around crypto-native governance and risk frameworks that don't align with institutional credit risk evaluation. When a protocol changes its risk model, institutions have no reliable way to underwrite that change in advance—a core issue. Private permissioned systems address control requirements but limit participation, cutting off liquidity and network effects. XRPL brings together both capabilities: credit infrastructure standardized at the protocol layer, a public network for liquidity and distribution, and permissioned participation through credentials when required. Credit markets sit alongside payments, collateral movements, treasury operations, and settlement flows. XRPL has handled institutional settlement at scale for over a decade; building a financing layer on the same network reduces operational complexity and allows institutions to manage more of the financial lifecycle in one place.

What This Unlocks

The lending protocol matters not because it creates another yield product, but because it makes digital assets more productive. It gives institutions a way to treat onchain assets as working capital, not static inventory. A payment provider can access short-duration liquidity to bridge settlement gaps. A market maker can finance inventory without selling core assets. A treasury team can deploy idle digital assets into underwritten facilities with clearer terms and risk allocation. A lender can build structured credit products on top of a common infrastructure layer instead of building a custom protocol from scratch.

Beyond Tokenization

The next phase of blockchain in finance will not be defined by whether an asset can be tokenized—that is becoming table stakes. The harder question is what happens once those assets are onchain. Capital markets depend not just on ownership but on financing, collateralization, liquidity management, and efficient capital movement. The challenge is whether the infrastructure around assets can make them productive. The decisions now on where credit logic lives, how obligations are enforced, and how risk is allocated will determine whether onchain capital markets develop real depth. The XRPL Lending Protocol (XLS-65, XLS-66) is subject to validator approval. Infrastructure providers and developers can begin integrating and testing on devnet today—see the Lending Protocol in action and help define how onchain credit markets take shape.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
800

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.