Rippled Adds Confidential Transfers for Multi-Purpose Tokens, Pending Validator Vote

and

tags. We'll also need to generate a meta description in Italian, summarizing the article. Typically meta descriptions are a concise summary. We'll create one. Let's proceed step by step. First, translate the title. We'll use: "Rippled aggiunge trasferimenti confidenziali per token multi-purpose, in attesa del voto dei validatori" – but note that "Multi-Purpose Tokens" is a specific term, maybe keep as "Multi-Purpose Tokens" or translate? Since it's a specific token type, we might keep it in English. The instruction says to use appropriate Italian terminology for crypto/tech terms, but proper nouns stay. "Multi-Purpose Tokens" is a proper noun? It's a specific term in the XRP Ledger context. I'll keep it as "Multi-Purpose Tokens" but maybe translate to "token multiuso"? Actually, in the original it's capitalized as a proper noun. I'll keep it as "Multi-Purpose Tokens" to be safe. Alternatively, "token multi-uso" but that might not be standard. I'll keep it as is. Title: "Rippled aggiunge trasferimenti confidenziali per token Multi-Purpose, in attesa del voto dei validatori" – but we need to be consistent. Actually, the original title says "Multi-Purpose Tokens" so we can keep that. Now content. Let's translate each paragraph. Original content:

What the merge actually does

The change adds five new transaction types — ConfidentialMPTSend, ConfidentialMPTConvert, ConfidentialMPTMergeInbox, ConfidentialMPTConvertBack and ConfidentialMPTClawback. It also pulls in the mpt-crypto library so the network can verify proofs on chain.

Under the hood, that means EC-ElGamal ciphertexts, Pedersen commitments, compact sigma proofs and aggregated Bulletproof range proofs. The point is to keep a balance private while still letting the ledger check that the amounts are consistent — that no token is being conjured out of nothing.

The vote that decides it

Merging into develop isn't activation. The feature has to clear the XRPL amendment process, which requires a supermajority — more than 80% of trusted validators — to approve continuously for two weeks.

Validator Vet expected a package that includes confidential transfers and batch transactions 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."

What issuers would get

The draft introduces issuer opt-in flags, so a token issuer could choose to enable confidential circulation for specific tokens. The trade-off the design makes: the ledger still verifies supply and flows through the proofs, but the amounts themselves stay encrypted.

The next concrete step is the validator vote. If the amendment clears the two-week supermajority threshold, the feature would be live. Until then, the code is in the develop branch and XLS-0096 remains a draft.

That's about 300 words. Let me add a bit more detail and expand a little. Maybe add a sentence about what confidential transfers mean for MPTs specifically. Let me count more carefully and expand to ~450-550. Also I need to make sure I'm not using AI tics. Let me check: no "furthermore", no "it's worth noting", no rhetorical questions. Good. I have "The point is" which is fine, human. Let me also double check the ending — it should be a concrete next thing. "The next concrete step is the validator vote. If the amendment clears the two-week supermajority threshold, the feature would be live." That works. Word count check — let me expand slightly. Final draft: Title: "Rippled Merges Confidential MPT Transfer Code, Validator Vote Next" Content:

The rippled client merged support for confidential transfers on Multi-Purpose Tokens into its develop branch on June 27, putting the XRP Ledger a step closer to letting issuers hide token balances without giving up on-chain verification. The code implements XLS-0096, a draft standard published Jan. 15, and it's now waiting on validators to decide whether it ever goes live.

Five new transaction types

The merge adds five new transaction types: ConfidentialMPTSend, ConfidentialMPTConvert, ConfidentialMPTMergeInbox, ConfidentialMPTConvertBack and ConfidentialMPTClawback. It also integrates the mpt-crypto library so the network can verify the cryptographic proofs on chain.

That verification covers EC-ElGamal ciphertexts, Pedersen commitments, compact sigma proofs and aggregated Bulletproof range proofs. The design goal is straightforward: keep a token balance private while still letting the ledger confirm the math holds — that supply hasn't been inflated and flows match the proofs.

Activation is a two-week vote

Merging into the develop branch isn't the same as shipping. Under the XRPL amendment process, activation requires a supermajority — more than 80% of trusted validators — to approve continuously for two weeks.

Validator Vet expected a package including confidential transfers and batch transactions 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."

Issuers opt in, amounts stay hidden

The draft introduces issuer opt-in flags, so an issuer could enable confidential circulation for specific tokens rather than the whole asset class. The ledger would still verify supply and flows through the proofs; it just wouldn't broadcast the amounts to every observer.

What happens next is the validator vote. If the amendment clears the two-week supermajority threshold, the feature goes live. Until then, the code sits in the develop branch and XLS-0096 remains a draft standard.

That's around 340 words. I need 450-700. Let me expand a bit more — add a bit about what this means for MPTs, or the context of the draft standard being created in January. Let me add a sentence or two. Actually let me add a short section or expand existing ones: In the first section, I could add: "The draft standard was created Jan. 15, and the develop branch merge came just over five months later." That's a fact-derived detail. In the vote section, I can add a bit about the timing. Let me also make the lead a bit richer. Final:

The rippled client merged support for confidential transfers on Multi-Purpose Tokens into its develop branch on June 27, putting the XRP Ledger a step closer to letting issuers hide token balances without giving up on-chain verification. The code implements XLS-0096, a draft standard published Jan. 15, and it's now waiting on validators to decide whether it ever goes live.

Five new transaction types

The merge adds five new transaction types: ConfidentialMPTSend, ConfidentialMPTConvert, ConfidentialMPTMergeInbox, ConfidentialMPTConvertBack and ConfidentialMPTClawback. It also integrates the mpt-crypto library so the network can verify the cryptographic proofs on chain.

That verification covers EC-ElGamal ciphertexts, Pedersen commitments, compact sigma proofs and aggregated Bulletproof range proofs. The design goal is straightforward: keep a token balance private while still letting the ledger confirm the math holds — that supply hasn't been inflated and flows match the proofs.

Activation is a two-week vote

Merging into the develop branch isn't the same as shipping. Under the XRPL amendment process, activation requires a supermajority — more than 80% of trusted validators — to approve continuously