← Back to News SurferX Updates
tokenizationprivacyxrplcryptographyblockchain

Zero-Knowledge Proofs Explained: How XRPL Is Designing Privacy Without Hiding Everything

SurferX HubNovember 5, 20268 min read
Zero-Knowledge Proofs Explained: How XRPL Is Designing Privacy Without Hiding Everything

Why public blockchains struggle with confidentiality, and what the proposed Confidential Transfers amendment would change

XRPL’s proposed Confidential Transfers aim to hide token amounts while keeping auditors able to verify them.

Key facts: Combines EC-ElGamal encryption with zero-knowledge proofs (XLS-96, “Confidential MPT”) · Applies to Multi-Purpose Tokens, not XRP · Hides balances and transfer amounts, not sender and receiver accounts · Not live on mainnet: it is in validator voting and has not reached the required 80% support

The Problem

Public blockchains are transparent by design. Anyone can look up an address, see its balance and trace its transfers. As covered in Learn.SurferX.io’s cryptocurrency guide, that is pseudonymous, not anonymous: addresses aren’t names, but the activity is visible. For an individual, that can be a privacy concern. For a fund or a company, it can be a business problem, because competitors can read positions and payment amounts straight off the ledger. At the same time, regulators and auditors need to be able to verify what happened. Privacy and accountability look like opposing goals.

Why It Matters

As covered in Learn.SurferX.io’s guides on real-world assets and institutional adoption, tokenized securities and treasury-style assets are a major focus for XRPL. Institutions holding those assets often can’t operate where every balance is public. XRPL’s proposed answer is Confidential Transfers, which relies on a branch of cryptography called zero-knowledge proofs. Understanding the idea helps readers separate real privacy technology from marketing, and see what this proposal does and doesn’t do.

How Zero-Knowledge Proofs Work and Where XRPL Fits

The core idea. A zero-knowledge proof is a way to prove that a statement is true without revealing the information behind it. A simple picture: proving you know the solution to a puzzle without ever showing the solution. As covered in Learn.SurferX.io’s digital identity guide, selective disclosure, such as proving you are over a certain age without sharing your birthdate, follows a similar spirit. Zero-knowledge proofs apply that idea to math, so someone can prove a calculation was done correctly without showing the numbers that went into it.

Encryption plus proof. According to XRPL.org documentation and the XLS-96 specification, the proposal combines two tools. EC-ElGamal encryption hides balances and transfer amounts. Zero-knowledge proofs then let the network confirm the transaction is valid, for example that the amounts are consistent and nothing is created from nothing, without anyone seeing the figures. The encryption hides the numbers, and the proof shows the arithmetic still works. (Sources: XRPL.org — Confidential Transfers documentation; XLS-0096 specification)

What it covers. The proposal is for Multi-Purpose Tokens (MPTs), XRPL’s token standard for assets such as tokenized securities and treasury bills. It does not apply to XRP itself, and it isn’t meant to turn XRPL into a fully private chain. According to the documentation, confidential transfers work only for direct payments between accounts, not through the XRPL DEX, escrows or checks.

It is opt-in at two levels. The issuer must enable confidential transfers on the token and register its keys, and can choose to lock that setting permanently, though some of those issuer controls depend on a companion amendment, DynamicMPT, which is also still in voting. Each holder must then opt in by converting some balance, even a zero amount, which registers their encryption key. Public and confidential balances can coexist for the same token.

What stays visible. This is amount privacy, not identity privacy. Per the XLS-96 specification, sender and receiver accounts and the token involved remain visible. Conversion amounts, when a holder moves tokens between public and confidential form, are public as well. The issuance also tracks the total amount held in confidential balances. The specification works through a low-volume example and notes that these public elements can reveal patterns when activity is thin.

Auditability by design. Issuers can register an auditor’s encryption key. That key lets the auditor decrypt the balances and amounts for that issuance while the public cannot. This is closer to a designated viewing key than to a zero-knowledge proof of a single fact, so it differs from the selective disclosure described in the digital identity article. The design also includes an issuer-only clawback that burns a holder’s entire confidential balance, permanently removing those tokens from circulation. XRPL describes these features as built to keep compliance access in place for authorized parties. That is a design intent, and it doesn’t mean any regulator has endorsed the approach.

How a holder uses it. In the documented flow, a holder first converts a public balance into an encrypted one (ConfidentialMPTConvert). Incoming confidential funds arrive in an inbox and are merged into the spendable balance with a separate step. A holder can convert back to a public balance from the spending balance. That detail shows this is a distinct set of transaction types, not a setting that is switched on globally.

Keys matter even more. The encryption keys used here are separate from an account’s normal XRPL signing keys. The XLS-96 specification is direct about the consequence: a holder who loses their encryption key can no longer decrypt or spend their confidential balance, which stays on the ledger but is effectively locked and irrecoverable by that holder. A separate draft proposal, XLS-99, would add key rotation and a recovery path, though recovery would depend on the issuer completing it. As covered in Learn.SurferX.io’s self-custody guide, losing a key can mean losing access, and that logic extends to a second set of keys. The specification also notes that this encryption method isn’t considered quantum-safe. (Sources: XLS-0096 specification; XLS-0099, ElGamal Key Rotation for Confidential MPTs)

Where things stand. The Confidential Transfer amendment shipped in the xrpld 3.3.0 release in August 2026, and validator voting has been open since. The most recent reporting available, from early September, said it had not reached a validator majority, and it is not live. Activation would require more than 80% of trusted validators for two consecutive weeks. The XLS-96 specification is now marked Final, which describes the specification itself and is not the same as network activation. Track the live vote on XRPL’s amendment page. (Sources: XRPL.org — xrpld 3.3.0 release notes and Known Amendments)

Example

Imagine an asset manager holding tokenized treasury bills on XRPL. With public balances, any observer can see how large the position is and when it changes, which can reveal strategy. With confidential balances, the manager first converts part of the holding, and that conversion amount is visible. After that, confidential transfers hide the amount: outsiders see that a transfer occurred between two accounts but not how much moved. The issuer’s registered auditor can still verify the figures, and compliance access is preserved through that structure. The ledger can confirm the books balance without outsiders reading the numbers, though the visible pieces, such as accounts and conversions, still leave a trail.

Common Mistakes

Confusing private with anonymous. In the documented design, accounts remain visible. The amounts are what get hidden.

Assuming the whole path is hidden. The step of converting into or out of confidential form shows the amount publicly.

Assuming it is already live. The amendment is still in the voting process. A specification marked Final is not the same as an enabled amendment.

Assuming it applies to XRP. The proposal is for Multi-Purpose Tokens, not the XRP asset.

Assuming auditors and issuers are locked out too. The design intentionally keeps access for the issuer and any configured auditors, which is what separates it from full privacy chains.

Underestimating key management. A lost encryption key leaves a confidential balance effectively locked. The proofs are mathematical and checkable, so the practical risks sit in implementation bugs and key handling.

FAQ

What is a zero-knowledge proof? A method of proving a statement is true without revealing the underlying information.

What are XRPL Confidential Transfers? A proposed amendment (XLS-96) that would let holders of Multi-Purpose Tokens keep balances and transfer amounts encrypted, while validators still verify transactions using zero-knowledge proofs.

Would this make XRPL a private blockchain? No. It is opt-in, applies to MPTs, and keeps access for issuers and configured auditors. Sender and receiver accounts remain visible, and so do conversion amounts.

Who can see a confidential balance? The holder, the issuer, and any auditor the issuer has configured. The public cannot.

What happens if a holder loses their encryption key? According to the XLS-96 specification, the confidential balance is effectively locked and irrecoverable by that holder. XLS-99, a draft proposal, would add key rotation and a recovery path that depends on the issuer.

Is it live on the XRP Ledger? Not at the time of writing. It is in validator voting and needs more than 80% support for two consecutive weeks.

Why do institutions want this? Public balances can reveal positions and strategy, while regulated assets still need to be auditable.

Continue Learning

This article builds on Learn.SurferX.io’s guides on What Is Digital Identity?, Real-World Assets on the Blockchain and What Is Cryptocurrency?, which cover selective disclosure, tokenized assets and the pseudonymous nature of public ledgers. Learn.SurferX.io will keep explaining new XRPL proposals as they move through the amendment process.

To see where this fits in the bigger picture of tokenized assets, revisit Learn.SurferX.io’s guide on Real-World Assets on the Blockchain.

← Back to News
View original on Medium ↗