This Week on the Ledger

The weeks that matter most to the XRP Ledger's long-term trajectory rarely announce themselves. This was one of them. Across protocol infrastructure, privacy architecture, and on-chain asset growth, the ledger moved in several directions simultaneously — none of it spectacular in isolation, all of it consequential in aggregate.

Protocol Infrastructure: Stability, Security, and the Long Road to Lending

Three meaningful protocol developments landed this week, each at a different stage of the amendment lifecycle.

• rippled 3.1.2 was released as the second security-focused patch in three weeks, addressing a server instability issue that had caused nodes to crash under specific conditions alongside several additional vulnerability fixes. The release includes a rotation of the GPG key used to sign rippled packages — operators installing via apt or yum repositories are required to import the new key to maintain compatibility with future upgrades. Validators and node operators are being urged to upgrade promptly. The network is carrying more institutional weight than it was a year ago, and the infrastructure is being maintained accordingly.
• The Batch amendment (XLS-56) has been permanently blocked following the discovery of a critical signature-validation flaw identified by researcher Pranamya Keshkamat and Cantina AI's autonomous audit tool Apex. A corrected replacement, BatchV1_1, has been implemented and is currently under review with no mainnet activation date set. The episode was a demonstration of the amendment review process functioning as intended — a flaw caught in the voting phase, before mainnet, with a patch published and a replacement already in development.
• The Lending Protocol (XLS-66) continues its slow passage through validator consensus, sitting at approximately 17% favorable votes against the 80% threshold required for activation. When it passes, it will allow tokenized assets already sitting on the ledger to be used as collateral in lending and borrowing arrangements — a meaningful step toward a functional DeFi layer on XRPL. The pace of validator adoption reflects the deliberate nature of XRPL governance rather than opposition to the amendment itself. These things move on the network's schedule, not the market's.

Privacy Architecture: What Confidential MPTs Actually Mean

Validator and ecosystem contributor Vet published a detailed technical breakdown this week on XLS-372, the amendment that would introduce Confidential Multi-Purpose Tokens to the XRP Ledger, and the timing is not coincidental — a U.S. Treasury report released earlier this month formally recognized the use of privacy and anonymization tools as a legal right of blockchain users, a meaningful shift in official framing after years of regulatory ambiguity. What XLS-372 proposes is the integration of zero-knowledge proof technology directly into the ledger's token infrastructure, meaning transaction amounts and counterparty details can be shielded from public view while remaining verifiable to authorized parties — regulators or compliance officers — upon formal request, a design that treats privacy not as a workaround but as a compliance-compatible feature built for the institutional environment the ledger is increasingly operating in. For any institution evaluating XRPL as settlement infrastructure, the absence of transaction confidentiality has been a legitimate barrier; XLS-372 addresses it directly, and the fact that it is being developed alongside rather than in tension with the regulatory framework gives it a different character than the privacy tools that have drawn scrutiny elsewhere in the industry.

On-Chain Growth: The Numbers Behind the Ledger

The XRP Ledger crossed 2.5 million transactions in a single 24-hour window this week, continuing a trajectory that has the network trending toward a 3 million daily average — a figure that sat around 1 million in mid-2025 — driven not by any single application category but by payment flows, AMM liquidity operations, stablecoin transfers, and tokenized asset activity accumulating across the ledger simultaneously. Total tokenized real-world asset value on XRPL has reached $2.3 billion, up from $991 million at the start of the year, with stablecoin transfer volume over the past 30 days reaching $1.19 billion across a market cap of $339 million and more than 35,000 holders. This week also marks a natural moment to note that Canada's own contribution to this story — Project Samara, the Bank of Canada's tokenized bond experiment with RBC, TD, and Export Development Canada — was published in full on March 5, documenting a $100 million CAD bond settled in wholesale central bank digital money on a distributed ledger; we covered it in full here, and its conclusions are worth reading carefully by anyone tracking where institutional DLT deployment in this country is actually headed.

In Brief

Goldman Sachs has been confirmed as the largest known institutional holder of XRP ETF products, with a $154 million position, as cumulative inflows into U.S.-listed XRP ETFs reach $1.44 billion since launch.

Ripple announced a $750 million share buyback, a move that has divided the community — critics note it uses proceeds from XRP escrow sales to benefit equity holders rather than token holders, while the implied valuation from the repurchase puts the company at approximately $50 billion, higher than the October 2025 funding round.

Tokenized commodities on the XRP Ledger have grown from $111 million in January to $1.14 billion as of this week — a tenfold increase in ten weeks — sitting within the broader $2.3 billion RWA total and underscoring that the ledger's asset growth is not concentrated in any single product category.

AUDD, the Australian dollar stablecoin operated by AUDC, became the first government-licensed stablecoin on the XRP Ledger this week after Australia's ASIC granted AUDC a full financial services license — a distinction that matters because AUDD settles directly on-chain, making it the first regulated stablecoin on XRPL to generate genuine ledger activity rather than routing through Ripple's enterprise software layer.