The XRP Ledger’s privacy roadmap runs through a specific technical proposal: XLS-33, the multi-purpose token (MPT) standard, and a newer draft built on top of it called XLS-0096, or “confidential MPTs.” Together they sketch out how the ledger could move tokenized value without broadcasting every balance and transfer amount to the public ledger, the same tradeoff traditional finance takes for granted and public blockchains have struggled with from the start.
What XLS-33 actually added
Ripple’s open-source documentation lays out XLS-33 as a new token type built for institutional use cases: multi-purpose tokens issued and managed with less overhead than the trust-line-based tokens XRPL has used for years. The XRPL developer docs describe MPTs as fungible tokens designed for large-scale issuance, which matters for anyone putting big volumes of tokens (tokenized funds, loyalty points, stablecoin-like instruments) onto the ledger.
The confidential layer: XLS-0096
XLS-0096 is a separate, still-draft proposal that would add confidentiality to MPTs: hiding balances and transfer amounts from public view while still letting the network validate that a transaction is legitimate. That’s the harder engineering problem. A recent paper on IACR’s ePrint archive, the field’s standard preprint repository for cryptography research, works through the zero-knowledge proof techniques this kind of confidentiality requires: proving a transaction is valid without revealing the numbers behind it.
This lines up with where the standards world is heading generally. NIST runs a dedicated Privacy-Enhancing Cryptography project and a zero-knowledge proof effort specifically because regulators, banks, and enterprise users want the same thing: proof of compliance without exposing every transaction detail to competitors or bad actors. NIST’s broader Privacy Framework gives institutions a structured way to reason about that tradeoff instead of handling it ad hoc.
Why this matters if you hold or use XRP
None of this changes how XRP or MPTs work on mainnet today. XLS-0096 is a draft amendment, and XRPL amendments require validator consensus before they go live, a process that can take months and sometimes doesn’t happen at all. Treat confidential MPTs as a research direction the ecosystem is actively working on, not a feature you can use right now. What it does signal is that Ripple and the wider XRPL developer community are building toward the kind of privacy-preserving compliance tooling that serious institutional users (banks, asset managers, payment processors) tend to require before moving real volume onto a public ledger. If you’re evaluating XRPL for a business use case, XLS-33’s multi-purpose tokens are live and usable now; confidential MPTs are something to watch, not something to plan a roadmap around yet.
Educational only, not tax, legal, or investment advice. Check primary sources and speak with a qualified professional before making financial decisions.
