Ripple shipped zero-knowledge privacy for tokenized assets on the XRP Ledger. The feature encrypts balances and transfer amounts while keeping accounts visible, a design that separates it from every privacy coin on the market and raises a question regulators have not yet answered.
Summary
- XRP Ledger version 3.3.0, released on August 6, 2026, includes the Confidential MPT amendment (XLS-0096), which uses EC-ElGamal encryption, Pedersen commitments, and Bulletproof range proofs to hide Multi-Purpose Token balances and transfer amounts while keeping sender and receiver accounts fully visible on the public ledger.
- The amendment sits alongside four other proposals in the same release: BatchV1_1 for atomic multi-account transactions, Sponsor for third-party fee delegation, DynamicMPT for mutable token properties, and Permission Delegation for granular account access, collectively representing the largest single protocol expansion in XRPL history.
- More than $530 million in tokenized real-world assets already live on the ledger, issued by firms including Ondo Finance ($212.6 million), VERT Capital ($116.1 million), and Archax ($55.4 million), all of which could opt into encrypted balances once validators activate the amendment.
- A $550,000 Sherlock security contest identified 96 vulnerabilities across the five amendments before any code reached mainnet, including two critical flaws: a signature-validation bypass in Batch that would have allowed unauthorized transactions, and a Permission Delegation bug enabling silent balance drainage through repeated fee charges.
- Activation requires at least 80 percent support from trusted validators, sustained continuously for two weeks, meaning the code is live in the software but not yet enforced on the network.
Ripple has spent most of 2026 building infrastructure that major financial institutions are willing to touch. JPMorgan settled a tokenized Treasury redemption on the XRP Ledger in under five seconds. Deutsche Bank deepened its integration with Ripple Payments. SBI launched RLUSD, Ripple’s dollar-pegged stablecoin, in Japan after securing regulatory approval. The stablecoin itself has grown to a $1.6 billion market cap, making it the third-largest regulated dollar stablecoin in the United States.
None of those milestones solved a problem that institutional treasurers and compliance officers keep raising: every token balance and every transfer amount on the XRP Ledger is visible to anyone with a block explorer. For a bank moving $50 million in tokenized bonds, that transparency is not a feature. It is a competitive liability.
The XRP Ledger 3.3.0 release is Ripple’s answer. It ships five amendments in a single package, but the one that matters most for institutional adoption is Confidential MPT, a cryptographic layer that encrypts token balances and transfer sizes while preserving the public, auditable nature of the ledger itself. What makes this design unusual is not just the privacy it offers, but the privacy it deliberately withholds.
What confidential MPT actually does
The Confidential MPT amendment, formally specified as XLS-0096, replaces plaintext per-account Multi-Purpose Token balances with EC-ElGamal ciphertexts. When a user sends tokens, the transfer amount is encrypted on-chain, and both the sender and receiver balances update as ciphertext values that cannot be read by third parties scanning the ledger.
Validators do not need to decrypt anything to confirm a transaction is valid. Instead, the protocol relies on a layered zero-knowledge proof system. Each confidential transfer includes a compact sigma proof binding all ElGamal ciphertexts under a single Fiat-Shamir challenge, a pair of Pedersen commitments that encode the transfer amount and the remaining balance, and an aggregated Bulletproof range proof confirming that no balance has gone negative and that the total supply remains intact.
The cryptographic payload is not trivial. A Ripple research paper authored by Murat Cenk, Aanchal Malhotra, and Joseph Ayo Akinyele, published through the International Association for Cryptologic Research (IACR) in 2026, details the mathematical foundations. The system includes a linkage proof that binds the ElGamal ciphertext used for the transfer to the Pedersen commitment used for the range proof, preventing a class of attacks where a malicious sender could submit valid proofs for a different amount than the one actually transferred.
The proof system is designed to prevent two specific attack vectors that plague simpler confidential transaction schemes. First, without the linkage proof, a sender could generate a valid range proof for one amount while the ElGamal ciphertext actually encrypts a different amount, effectively creating tokens out of thin air. Second, the protocol requires a proof of knowledge during account registration to prevent rogue key attacks, where a malicious party registers a public key derived from another user’s key to manipulate aggregate ciphertexts.
Validators process these proofs without learning anything about the underlying values. The verification cost is logarithmic in the range size thanks to Bulletproofs, keeping transaction validation efficient even as the proof payload grows. According to the IACR paper, a single confidential transfer proof adds roughly 1.5 kilobytes to the transaction, a manageable overhead for a ledger that already handles thousands of transactions per second.
Critically, the amendment is opt-in at the issuer level. A token issuer creating a new MPT can choose whether balances and transfers should be confidential. Issuers who opt in retain the ability to designate authorized parties, such as auditors, regulators, or compliance officers, who can decrypt and verify the underlying amounts. Freeze and clawback controls, the same mechanisms issuers already use for standard MPTs, remain fully functional.
What stays visible is equally important. Sender and receiver account addresses are public. The token type being transferred is public. The fact that a transaction occurred is public. Only the amount and the resulting balances are hidden.
How this differs from Monero and Zcash
The comparison to privacy coins is inevitable, but the architecture is fundamentally different in ways that matter for both regulators and users.
Monero treats privacy as a default that cannot be turned off. Every transaction hides the sender, receiver, and amount using ring signatures, stealth addresses, and RingCT. After the FCMP++ upgrade in early 2026, tracing a Monero transaction requires analyzing the entire unspent output set, more than 1.8 million outputs, making it computationally infeasible. No blockchain analytics firm has publicly shown reliable XMR tracing at scale since that upgrade.
Zcash offers privacy as an option through zk-SNARKs, but adoption has been uneven. Shielded transaction usage reached an all-time high of 59.3 percent in February 2026, meaning roughly 40 percent of ZEC transactions remain fully transparent. The network hides sender, receiver, and amount in shielded-to-shielded transfers, but the optional nature creates a metadata leakage problem: the act of choosing privacy can itself be informative.
XRPL’s Confidential MPT occupies a third category entirely. Privacy is neither mandatory nor user-selected. It is issuer-controlled. The token creator decides at issuance whether balances are encrypted, and that decision applies uniformly to all holders of that token. Individual users cannot opt in or out. This means the privacy model is determined by the entity with the compliance obligation, not the entity with the privacy preference.
The scope of concealment is also narrower. Monero and Zcash hide who is transacting. Confidential MPT does not. Account addresses remain visible on every transaction, preserving the ability to map transaction flows even when amounts are hidden. For an analytics firm or a regulator, this is a meaningful distinction: they can see that Account A sent tokens to Account B, they simply cannot see how many.
Sponsored fees and the enterprise onboarding problem
The Confidential MPT amendment gets the headlines, but the Sponsor amendment (XLS-68) may have a more immediate impact on adoption. It addresses a friction point that has blocked enterprise deployment on every account-based blockchain: the requirement that end users hold the native token before they can do anything.
On the current XRP Ledger, every account must hold a minimum reserve of XRP and pay transaction fees in XRP. For a bank onboarding thousands of customers to a tokenized money market fund, this means either distributing XRP to every participant or building a custodial layer that abstracts the requirement away. Both approaches add cost, complexity, and regulatory surface area.
The Sponsor amendment lets a third party, whether a bank, an issuer, or a platform operator, cover transaction fees and reserve requirements on behalf of its users. Sponsors can co-sign individual transactions or pre-fund a sponsorship pool that covers costs automatically. Users retain full control of their accounts and private keys throughout.
The design is straightforward. A sponsor includes a signature in the user’s transaction indicating willingness to pay. The network charges the sponsor’s account for the fee and, if the transaction creates new on-chain objects, applies the reserve requirement to the sponsor’s balance. Users can transact with zero XRP in their wallets.
For institutional tokenization, this changes the deployment calculus significantly. A fund administrator issuing tokenized shares on the XRP Ledger can now guarantee that investors never need to interact with a cryptocurrency exchange, never need to acquire XRP, and never need to understand gas mechanics. The entire fee layer becomes invisible, handled by the issuer as a cost of doing business, the same way traditional brokerages absorb settlement costs.
Combined with Confidential MPT, the picture becomes clearer. An institution can issue a token where balances are encrypted, transfers are private, and users never touch XRP. The ledger handles settlement, the cryptography handles privacy, and the sponsor handles fees.
This combination addresses a complaint that has echoed through every institutional blockchain pilot since 2017: public chains expose too much, and private chains sacrifice interoperability. The XRPL approach threads the needle by keeping the chain public and permissionless while making specific asset classes opaque at the issuer’s discretion. Whether this hybrid model satisfies the compliance teams at firms like BlackRock and BNY Mellon, both of which already work with Ripple through RLUSD partnerships, remains to be seen.
Batch transactions and atomic settlement
The BatchV1_1 amendment completes the institutional toolkit by allowing up to eight transactions across different accounts to execute atomically within a single ledger close. Every transaction in the batch either succeeds or the entire group fails.
This is a corrected version of an earlier Batch implementation that was disabled after the Sherlock security audit found 96 vulnerabilities across the five proposed amendments. The original Batch code contained a critical signature-validation flaw that could have allowed attackers to execute transactions from any account without holding its private key. The rewritten version, designated V1_1, addresses this and other issues identified during the $550,000 community security contest.
Atomic batching matters for regulated finance because it enables delivery-versus-payment, the simultaneous exchange of a security for cash that reduces counterparty risk. On traditional rails, this coordination requires intermediaries, clearing houses, and settlement windows measured in days. On a ledger with atomic batches, the swap happens in one operation: the buyer’s payment and the seller’s delivery either both complete or neither does.
The $530 million already on the ledger
These amendments are not being built for a hypothetical future. The XRP Ledger already hosts approximately $1.38 billion in tokenized real-world assets. Excluding RLUSD’s $845.7 million contribution, more than $530 million in other tokenized assets sit on the ledger today, issued by firms that have a direct commercial interest in balance privacy.
Ondo Finance leads with $212.6 million in tokenized products, followed by VERT Capital at $116.1 million and Archax at $55.4 million. These are not experimental deployments. Ondo is one of the largest tokenized Treasury issuers in the industry. Archax is an FCA-regulated digital asset exchange based in London. Their presence on the XRP Ledger represents real capital with real compliance requirements.
For these issuers, the current transparency of MPT balances creates a problem that grows with scale. When a single fund holds $200 million in tokenized Treasuries, every subscription, redemption, and rebalance is visible to competitors, front-runners, and the public. Confidential MPT gives issuers the option to encrypt those movements while retaining the ability to share decrypted data with authorized auditors.
Version 1 of the amendment supports only direct MPT payments between accounts. Decentralized exchange trades, escrow arrangements, and payment channels are excluded from the initial scope. This means privacy, for now, applies to bilateral transfers, not to on-chain trading.
The regulatory question: does privacy help or hurt
Ripple has built one of the strongest institutional partnerships in the industry, including relationships with JPMorgan, Deutsche Bank, and SBI. The company holds a full MiCA authorization through Luxembourg’s CSSF, opening regulated access across all 30 European Economic Area countries. In the United States, Ripple received conditional OCC approval for a national trust bank in December 2025 and applied for a Federal Reserve master account.
Adding privacy features to a ledger this embedded in the regulated financial system is a calculated move. The timing coincides with two regulatory developments that pull in opposite directions.
The Digital Asset Market Clarity Act, which would classify XRP as a digital commodity under CFTC jurisdiction, is scheduled for a Senate procedural vote on September 15, 2026, after delays caused by partisan disagreements over ethics rules. A March 2026 joint SEC-CFTC classification already named XRP among 16 assets classified as digital commodities, but statutory codification would provide stronger legal certainty. The Clarity Act does not specifically address privacy features on commodity-classified ledgers, leaving an interpretive gap.
In Europe, Ripple’s MiCA license does not explicitly cover privacy-enhanced tokens. MiCA’s travel rule requirements mandate that transfer information, including sender, receiver, and amount, accompany crypto-asset transactions above certain thresholds. Confidential MPT’s design, where amounts are encrypted but issuer-designated parties can decrypt them, may satisfy this requirement if the issuer grants access to the relevant financial intelligence unit. But that interpretation has not been tested.
The European Union’s Anti-Money Laundering Regulation (AMLR) adds another layer. The regulation, set to restrict privacy coins at licensed exchanges by July 2027, targets assets where sender, receiver, or amount information cannot be obtained by authorities. XRPL’s issuer-controlled disclosure model may fall outside this definition, since authorized parties can always access the underlying data, but the regulatory text has not been applied to issuer-gated confidential tokens.
A March 2026 US Treasury report explicitly backed legitimate blockchain privacy use cases, recognizing that commercial confidentiality and financial privacy are valid objectives. This report is frequently cited by Ripple’s regulatory team as evidence that privacy features, when designed with compliance controls, are not inherently suspicious.
The opposing case: why confidential MPT may not matter
The strongest argument against Confidential MPT’s significance is adoption. The feature is opt-in at the issuer level, and issuers face no penalty for ignoring it. If Ondo Finance, VERT Capital, and Archax choose not to enable encryption on their existing tokens, the amendment becomes dead code sitting on the ledger.
There are reasons they might hesitate. Encrypted balances add computational overhead to every transaction, increasing the proof-generation burden on sending clients. Compliance teams at regulated issuers may prefer the simplicity of transparent balances, where auditors can verify holdings by scanning the ledger, over a system that requires key management and authorized decryption workflows.
The privacy this amendment offers is also partial. Account addresses remain visible, which means transaction graphs, the patterns of who transacts with whom, are fully exposed. For sophisticated analytics firms, amount-hidden but graph-visible transactions can still reveal significant information through frequency analysis, timing correlation, and known-address mapping. A competitor monitoring an issuer’s on-chain activity could infer approximate volumes from transaction counts alone.
Version 1’s scope limitation, excluding DEX trades, escrow, and payment channels, further narrows the practical utility. Institutional workflows that involve secondary market trading would need to fall back to transparent mode for any on-chain exchange activity, creating a two-tier visibility system that may confuse more than it conceals.
There is also a competitive angle. Ethereum, Polygon, and Avalanche all offer confidential transaction solutions through third-party protocols like Railgun and Aztec. These solutions operate at the application layer, meaning any token on those networks can be routed through a privacy pool without issuer permission. For institutions that want compliance-friendly privacy, this permissionless approach is a liability. But for institutions that simply want to move assets without broadcasting positions, application-layer privacy on a more liquid chain may be sufficient, and it does not require waiting for a validator vote.
The invalidation criteria for the bull case are clear. If fewer than three of the top ten XRPL asset issuers enable Confidential MPT within six months of activation, the feature has failed its market test. If validators reject the amendment outright, failing to reach 80 percent support, the privacy thesis for XRPL is shelved indefinitely. And if MiCA enforcement agencies rule that issuer-gated encryption does not satisfy travel rule requirements, European issuers, the fastest-growing segment of XRPL’s RWA market, cannot use the feature at all.
What active accounts and XRP demand tell us
The broader context for these amendments is a ledger searching for renewed activity. Active XRPL accounts fell 51 percent in 2026, declining from 15,571 on January 1 to 7,630 on July 20. XRP trades near $1.00, down more than 65 percent from its January high of $3.40. Weekly net inflows into US spot XRP ETFs collapsed 93 percent in the week ending August 8, falling from $14.86 million to just $1.01 million.
Ripple continues to release 1 billion XRP from escrow monthly, re-escrowing 600 to 800 million and allowing 200 to 400 million XRP to enter circulation. This supply schedule means the escrow releases tokens two to four times faster than the entire ETF complex absorbs them.
The Sponsor amendment has a direct bearing on this dynamic. By removing the requirement for end users to hold XRP, it potentially reduces organic demand for the token. Users of sponsored accounts interact with the ledger without ever acquiring XRP. The network fees are still paid in XRP, but they flow from the sponsor’s holdings, concentrating demand among a smaller set of institutional sponsors.
For XRP as an investment asset, the combination of privacy features and sponsored fees creates a paradox. The amendments make the ledger more useful for institutions but do not necessarily make XRP more valuable. Institutional activity settles through RLUSD, not XRP. Fees are paid by sponsors, not retail holders. And the privacy features apply to MPTs, not to XRP itself, which remains fully transparent.
The most direct path to XRP price recovery, as Ripple’s own community has noted, would be requiring RLUSD transactions to settle through XRP as a bridge asset. No such requirement exists in the current protocol.
What to watch
– Validator voting threshold: the Confidential MPT amendment needs 80 percent support from trusted validators, sustained for two consecutive weeks, before activation. Track the amendment vote count at xrpl.org once the two-week window opens.
– Issuer opt-in rate: whether Ondo Finance, VERT Capital, and Archax enable encrypted balances on existing or new token issuances within the first quarter after activation signals real demand for on-chain privacy.
– MiCA enforcement guidance: the European Banking Authority’s interpretation of whether issuer-gated encrypted amounts satisfy travel rule obligations will determine whether European issuers can use Confidential MPT at all.
– Clarity Act floor vote: the Senate procedural vote scheduled for September 15, 2026, will either codify XRP’s commodity classification or leave its regulatory status dependent on executive-branch guidance that could change with administrations.
– Sponsored-account adoption: the number of accounts operating under third-party fee sponsorship will indicate whether the Sponsor amendment succeeds in lowering onboarding barriers for institutional deployments.
This article is for informational purposes only and does not constitute financial, investment, or legal advice. Cryptocurrency markets are volatile and unpredictable. Always conduct your own research and consult a qualified professional before making any financial decisions. Information is accurate as of August 16, 2026.
Be the first to comment