> loading_
Critical Web3 & AI signals, curated weekly for builders and researchers.
> _
What shipped, what broke, and what you can run today.
> This update improves the developer experience by standardizing tooling, fixing a critical import path bug for new projects, and initiating research into `anyref` API support.[ read more → ]
This release focuses on enhancing the developer experience and unblocking new users. We've integrated standard development tools, including Prettier for consistent code formatting and a stricter ESLint configuration to catch potential issues early. This establishes a higher code quality standard and streamlines the contribution process. Additionally, we've initiated a formal investigation into creating a stable API for `anyref` imports, a crucial step towards seamless interoperability with JavaScript. The most critical fix addresses a build error that new users encountered when following the wiki instructions. The AssemblyScript compiler couldn't resolve the library's import paths (`~lib/as2d/*`) outside of the example repository, effectively blocking adoption. This was caused by a missing path mapping in the `tsconfig.json` configuration. Without this fix, developers were unable to integrate `as2d` into their own projects, creating a significant barrier to entry. With these changes, developers can now expect a smoother and more predictable development workflow. The standardized tooling ensures code consistency across the project, making it easier to read, maintain, and contribute to. Most importantly, the fix to the import path resolution error, along with updated wiki documentation, unblocks the community and makes it trivial for anyone to start a new project with `as2d`. The ongoing `anyref` research signals our commitment to improving WebAssembly and JavaScript integration in the future.
> What is a Single Asset Vault?
XLS-65 introduces a native on-ledger liquidity primitive: a Single Asset Vault. It aggregates capital from many depositors into one unified pool while issuing MPT shares to represent each depositor's ownership stake. The single-asset constraint — one vault, one token type — deliberately prevents cross-asset risk contagion common in multi-asset pools.
# VaultCreate · transaction anatomy
Asset
XRP, IOU (e.g. RLUSD), or MPT — locked to one type
ShareMPTID
The MPT token ID minted to represent vault shares
> leo-playbook · built for builders
_
AssetsAvailable
Liquid balance depositors can withdraw right now
AssetsTotal
Full pool size including unrealized losses from loans
LossUnrealized
Paper losses from outstanding defaulted loans
WithdrawalPolicy
Rules that govern when and how redemptions are allowed
Scale (0–18)
Precision factor preventing rounding errors at high volume
DomainPolicy
Public (open) or Permissioned Domain (KYC-gated)
# key mechanics
Proportional share issuance
Deposits mint MPT shares at the current exchange rate. Shares are transferable — you can trade them, use them as collateral, or redeem them for the underlying asset at any time (subject to WithdrawalPolicy).
Dual-algorithm exchange rate
Regular deposits use a proportional rate. Withdrawals during unrealized losses use an adjusted rate that prevents arbitrage — late withdrawers cannot front-run bad-debt events to drain the vault.
Private vs public vaults
Public vaults allow anyone to deposit. Private vaults use Permissioned Domains — on-chain credential gates — so institutions can restrict access to KYC-verified counterparties only.
VaultClawback
IOU or MPT issuers (e.g. Ripple for RLUSD) can recover assets from a vault in compliance scenarios, making this structure compatible with regulated asset frameworks.
# AffectedNodes · what the ledger emits
When VaultCreate executes, the transaction metadata's AffectedNodes array contains a CreatedNode entry with "LedgerEntryType": "Vault". Each subsequent deposit, withdrawal, or loss event appends ModifiedNode entries to the same array, giving indexers a tamper-proof audit trail of every pool state change.
> What is the XRPL Lending Protocol?
XLS-66 brings uncollateralized fixed-term loans natively on the XRP Ledger. Liquidity comes directly from XLS-65 vaults. Off-chain underwriting decides who qualifies; on-ledger logic handles disbursement, repayment schedules, and default enforcement. No external smart contract runtime required.
# LoanSet · transaction anatomy
LoanBroker
Protocol instance address that sources vault liquidity
Borrower
Counter-party receiving the loan principal
Principal
Loan amount in RLUSD, XRP, or an MPT — excluding fees
InterestRate
Fixed percentage locked at origination (no floating rate)
PaymentSchedule
Amortization intervals (daily/weekly, 30–180 day terms)
Status
Active → Repaid (or Defaulted) — updated on-chain
Multi-sign
Both LoanBroker.Owner AND Borrower must sign LoanSet
DebtTotal
Principal + accrued interest owed back to the vault
# First-Loss Capital · risk architecture
A LoanBroker can voluntarily deposit a First-Loss Capital buffer (CoverAvailable). When a borrower defaults, losses are deducted from this buffer first — protecting vault depositors from immediate impairment.
LoanBroker deposits cover via LoanBrokerCoverDeposit
Borrower + LoanBroker multi-sign LoanSet; principal transfers instantly
Borrower calls LoanPay on schedule; vault's AssetsAvailable grows
On default: LossUnrealized rises; cover absorbs loss; vault depositors are protected
# full transaction suite (8 ops)
> How they scale the XRPL ecosystem
Institutional-grade yield without leaving the ledger
YIELDXLS-65 vaults give institutions a native place to park capital and earn fixed-rate returns. XLS-66 draws from those vaults to fund borrowers — creating a full credit market loop on a single ledger with 3–5 second settlement finality. Evernorth (institutional asset manager) has publicly signaled it is preparing to use XLS-66 to generate institutional-grade yield on XRP holdings.
RWA tokenization backbone
RWAXRPL now carries $118M+ in tokenized Real World Assets (up 2,260% since January 2025). XLS-65 vaults provide the pooling layer for tokenized T-bills, trade finance, and treasury funds. Archax (UK FCA-regulated exchange) and OpenEden (tokenized US Treasury Bills) both target XRPL as their tokenization rail — directly enabled by XLS-65's permissioned vault infrastructure.
Capital efficiency for payment service providers
PAYMENTSMarket makers can borrow RLUSD for 1–3 days to bridge card-network and banking settlement gaps — without locking up inventory capital. Payment processors pre-fund merchant payouts via short-term XLS-66 loans, then repay after settlement clears. This compresses working capital requirements by hours or days per transaction cycle.
Regulatory-compatible design
COMPLIANCEPermissioned Domains on XLS-65 vaults allow private pools gated by on-chain KYC credentials — a requirement for any regulated financial institution. Off-chain underwriting plus on-ledger enforcement creates a hybrid model that satisfies both TradFi compliance teams and DeFi composability. Dubai DFSA has already recognised XRP and RLUSD as regulated assets inside the DIFC.
Composability: vaults as DeFi lego bricks
DEFIMPT shares issued by XLS-65 vaults can circulate freely — they can be collateralised in other protocols, listed on the XRPL DEX, or bridged via LayerZero. A vault deposit is no longer a dead-end position; it is a liquid, tradeable representation of pooled capital. This composes with every other XRPL primitive from AMMs to NFT royalties.