Confidential Transfers on the XRP Ledger (XLS-96): what they hide, what stays public, and where the validator vote stands on 17 November 2026
EC-ElGamal encryption, zero-knowledge proofs, an inbox and a spending balance. Addresses and total supply stay public; amounts do not. On 17 November, 21 of 35 validators vote yes; the threshold is 28.
On the XRP Ledger (XRPL), every token balance and every transferred amount is public today. The ConfidentialTransfer amendment would change that for Multi-Purpose Tokens (MPTs): balances and amounts would be encrypted, while validators could still check that nobody spends more than they hold (xrpl.org, Confidential Transfers). The code has been open for voting since server release 3.3.0 (xrpl.org, 6 August 2026). On 17 November 2026, 21 of 35 validators support it, against a threshold of 28 (XRPScan). It is not active on Mainnet.
This article explains how the design works, what remains visible, and what today's vote data does and does not show.
| Data sheet | |
|---|---|
| Standard | XLS-0096, Confidential Transfers for Multi-Purpose Tokens |
| Standard status | Final (created 15 January 2026, updated 22 October 2026) |
| Amendment name | ConfidentialTransfer |
| Shipped in | xrpld 3.3.0 (6 August 2026) |
| Default vote | "No" (per Known Amendments) |
| Yes votes, 17 November 2026 | 21 of 35 validators (60%) |
| Threshold shown by XRPScan | 28 of 35 (80%), held for two weeks |
| Live on Mainnet? | No |
Sources: XLS-0096, Known Amendments, XRPScan API.
What is hidden, and what stays public
The xrpl.org concept page is explicit that confidential mode does not make a transaction invisible.
Encrypted:
- transfer amounts;
- holder balances, readable only by the holder, the issuer and an optional auditor;
- how the confidential supply is spread across holders.
Still public:
- sender and receiver addresses;
- the transaction type;
- total supply, through the plaintext
OutstandingAmountandConfidentialOutstandingAmountfields, so validators can enforce the issuance cap; - amounts moved between public and confidential form.
The page also notes that low activity can expose patterns. Privacy gets stronger as more people use the feature.
The cryptography in brief
- EC-ElGamal encryption over the secp256k1 curve. Users generate keys off-ledger.
- Zero-knowledge proofs let a validator accept a transaction without seeing the amount. A Schnorr proof shows key ownership, sigma proofs show the encrypted values are consistent, and Bulletproofs range proofs show that the amount and the remaining balance are not negative.
- The documentation states that the scheme is not quantum-safe, and that a later migration is an open research question (xrpl.org).
Roles and transaction types
Issuer. Turns on confidential balances with a one-way flag, registers an ElGamal public key and keeps an encrypted mirror of every holder's balance. It cannot hold confidential balances itself and must use a separate account. Confidential mode requires a zero transfer fee (XLS-0096).
Holder. Converts public tokens to confidential form and spends with their own key. xrpl.org warns that a holder who loses the private key loses the confidential balance permanently.
Auditor (optional). Receives an encrypted copy of each balance under its own key, so it can verify independently of the issuer.
There are five new transaction types: ConfidentialMPTConvert (public to confidential), ConfidentialMPTSend (transfer), ConfidentialMPTMergeInbox (merge received funds), ConfidentialMPTConvertBack (back to public) and ConfidentialMPTClawback (issuer reclaims the full confidential balance).
Split balance. Each account has an inbox and a spending balance. Incoming funds land in the inbox and become spendable only after a merge. That way, an incoming payment cannot invalidate a proof the holder has already built. A version counter increases with every change, and the ledger rejects proofs tied to an old version.
Confidential transfers cover direct payments only. They do not work with the built-in DEX, escrows or checks (xrpl.org).
Where the vote stands
An amendment activates when at least 80% of trusted validators support it for two consecutive weeks (xrpl.org, Amendments).
| Date | ConfidentialTransfer yes votes | Source |
|---|---|---|
| Late September 2026 | 14 | KuCoin / 528btc, 15 October 2026 |
| 15 October 2026 | 22 | KuCoin / 528btc |
| 17 November 2026 | 21 of 35 | XRPScan |
Two related MPT amendments on the same day (XRPScan API):
| Amendment | Standard | Yes of 35 |
|---|---|---|
DynamicMPT | XLS-94 | 16 |
Sponsor | XLS-68 | 10 |
DynamicMPT matters here because switching on confidential mode for an existing issuance also requires it. A new issuance does not (xrpl.org).
What the data does not show
- It is not a date. 21 votes do not say when, or whether, the amendment will activate. Validators can change their vote at any time.
- Sources state the threshold differently. XRPScan shows 28 of 35; some press reports say 29. The network's own calculation is what counts.
- The press time series is secondary. The September and October figures come from a news summary, not a direct query.
- It is not full anonymity. Addresses and transaction types stay visible. The amendment covers MPTs only, not XRP payments.
- It is not price analysis. This article describes technical status and says nothing about price.
Summary
- XLS-96 would bring encrypted balances and amounts to MPTs, with public addresses and public total supply.
- The standard is marked Final, and the code has been in the server since 3.3.0.
- On 17 November 2026: 21 of 35 yes votes; not active on Mainnet.
Related: The XRP Ledger Lending Protocol (XLS-66), Blog archive.
Sources
- xrpl.org, Confidential Transfers (concept page): https://xrpl.org/docs/concepts/tokens/fungible-tokens/confidential-transfers
- XLS-0096, Confidential Transfers for Multi-Purpose Tokens (updated 22 October 2026): https://xls.xrpl.org/xls/XLS-0096-confidential-mpt.html
- xrpl.org, Introducing XRP Ledger version 3.3.0 (6 August 2026): https://xrpl.org/blog/2026/xrpld-3.3.0
- xrpl.org, Known Amendments: https://xrpl.org/resources/known-amendments
- xrpl.org, Amendments (activation rule): https://xrpl.org/docs/concepts/networks-and-servers/amendments
- XRPScan, Amendments (retrieved 17 November 2026): https://xrpscan.com/amendments
- XRPScan API, amendments (retrieved 17 November 2026): https://api.xrpscan.com/api/v1/amendments
- KuCoin / 528btc (15 October 2026): https://www.kucoin.com/news/flash/xrp-ledger-lending-and-privacy-proposals-still-lack-validator-approval
Educational content. Not financial or investment advice, and not a forecast. Data Analytic Investments is not affiliated with Ripple Labs Inc., the XRP Ledger Foundation, XRPScan or the other organisations cited; names are used for identification only.
Continue on DAI
Explore Topics
Written by
Data Analytic Investments
Content creator and writer sharing insights and stories.
Related tools & research
This article is a companion piece to the book.
RIPPLE — the book
An Unofficial Documentary Study of Ripple and the XRP Ledger
22 chapters · every claim with a named source · numbered first edition · $29