XRPL Confidential Transfers Near Validator Vote

XRPL’s push to add privacy-preserving transfers has cleared a major engineering step and is now heading for governance. The rippled client merged support for Confidential Transfers for Multi‑Purpose Tokens into its develop branch on June 27, 2026, positioning the change for an amendment vote on mainnet if validators choose to advance it.

The functionality is specified in XLS‑0096, a draft standard created on Jan 15, 2026 that defines confidential balances and transfers for MPTs using modern cryptography and issuer opt‑in controls. The standard and code paths are public, but activation depends on validator approval under XRPL’s amendment process.

Media coverage in late July cited prominent validator “Vet” in saying a package of amendments, including Confidential Transfers and Batch transactions, was expected to reach validators for voting in mid‑to‑late July. A July 20 report said validators were expected to start a vote “in about two weeks.”

If enabled, issuers could opt into confidential circulation for specific tokens while retaining on‑chain verification of supply and flows through proofs, a design that could align with institutional privacy requirements without removing network‑level auditability.

Inside XLS‑0096 confidential transfers

The XLS‑0096 draft standard sets out how confidential balances and transfers would work for Multi‑Purpose Tokens on XRPL. It specifies EC‑ElGamal encryption for amounts, zero‑knowledge proofs, and new transaction formats tailored to private issuance and movement of MPTs. The draft also introduces issuer opt‑in flags to enable confidential circulation only where an issuer chooses to use it. The specification is published in the XRPL Standards repository.

On the implementation side, the merged rippled change adds protocol support for Confidential MPT transactions and wires in on‑chain proof checks. According to the rippled pull request that was merged into develop on June 27, 2026, the code:

Adds new confidential transaction types and fields, including ConfidentialMPTSend, ConfidentialMPTConvert, ConfidentialMPTMergeInbox, ConfidentialMPTConvertBack, and ConfidentialMPTClawback.
Integrates the mpt‑crypto library for verification on chain.
Implements proof verification for EC‑ElGamal ciphertexts, Pedersen commitments, compact sigma proofs, and aggregated Bulletproof range proofs.

These are confirmed engineering details from the public repositories. In practical terms, if the amendment is later enabled, users transacting in supported MPTs could move balances privately while nodes validate correctness via cryptographic proofs rather than revealing amounts.

Sources: the XLS‑0096 draft in the XRPL Standards repository is available here. The merged rippled implementation (PR #5860) is documented here.

Validator and media signals on timing

Multiple independent outlets reported that well known XRPL validator “Vet” expected a package containing Confidential Transfers and Batch transactions to arrive for a vote in mid‑to‑late July. Coverage on July 20 said validators were expected to start a vote “in about two weeks,” framing the change as one of the ledger’s most significant upgrades in years. That framing and the quoted timing are attributed to the media report, not to XRPL Foundation communications.

The July coverage can be read here. As with any amendment on XRPL, the appearance of the item on voting dashboards and validator declarations will be the first concrete signs that the formal process has begun.

How XRPL amendments activate

XRPL changes that affect consensus behavior are gated by the amendment process. For any amendment that opens for voting, activation on mainnet requires a supermajority of greater than 80 percent of trusted validators continuously for two weeks. If that threshold is not maintained for the full period, the amendment does not become enabled. XRPL’s official documentation lays out the process and tracks known amendments.

Details on the amendment mechanism are maintained on XRPL.org here.

Next milestones to watch

The next decision point is whether validators open an amendment vote that includes Confidential Transfers, potentially alongside Batch transactions, as reported in July. If a vote opens, the key signal will be whether support from trusted validators rises above 80 percent and holds there for two consecutive weeks, which would enable the feature on mainnet.

Until then, the merged code in the develop branch and the published XLS‑0096 draft indicate the scope of what is on the table. Market participants watching for institutional privacy on XRPL should monitor validator voting announcements and XRPL’s amendment listings for any change in status.

Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.