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. The draft standard was first published Jan. 15, so the develop-branch merge landed about five months after the spec took shape.
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" — which would put it in early August.
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. The trade-off is deliberate: privacy for holders, but not a free pass on supply integrity.
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 the final article. We need to translate that to Hebrew. Also, we need to provide a meta description. Since it's not given, we can create a concise summary in Hebrew. We must respond in JSON with keys: title, content, meta.description. We need to ensure proper translation. We'll maintain HTML structure. We'll translate the text, keep proper nouns like "Rippled", "XRP Ledger", "XLS-0096", "ConfidentialMPTSend" etc. as is. We'll translate headings and paragraphs. Let's translate. Title: "Rippled Merges Confidential MPT Transfer Code, Validator Vote Next" -> Hebrew: something like "ריפלד ממזג קוד העברות סודיות עבור MPT, הצבעת מאמתים הבאה" But we need to be accurate. "Rippled" is the client name, we keep it. "Confidential MPT Transfer Code" -> "קוד העברות סודיות עבור MPT" or "קוד העברות חסויות". "Validator Vote Next" -> "הצבעת מאמתים הבאה" or "הצבעת הוולידייטורים הבאה". We'll use "מאמתים" for validators. Let's do the translation. Content translation: First paragraph: "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." Translation: "לקוח ה-rippled מיזג תמיכה בהעברות חסויות עבור אסימונים רב-תכליתיים (MPT) לענף הפיתוח שלו ב-27 ביוני, וקירב את ה-XRP Ledger צעד נוסף לאפשר למנפיקים להסתיר יתרות אסימונים מבלי לוותר על אימות על-השרשרת. הקוד מיישם את XLS-0096, תקן טיוטה שפורסם ב-15 בינואר, וכעת הוא ממתין להחלטת המאמתים האם הוא יופעל אי פעם." We need to keep "MPT" as is, maybe explain? Since it's a technical term, we can keep as MPT. "Multi-Purpose Tokens" could be translated as "אסימונים רב-תכליתיים" but we can also keep the abbreviation. Second section: "Five new transaction types" -> "חמישה סוגי עסקאות חדשים" Paragraph: "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." Translation: "המיזוג מוסיף חמישה סוגי עסקאות חדשים: ConfidentialMPTSend, ConfidentialMPTConvert, ConfidentialMPTMergeInbox, ConfidentialMPTConvertBack ו-ConfidentialMPTClawback. הוא גם משלב את ספריית mpt-crypto כך שהרשת יכולה לאמת את ההוכחות הקריפטוגרפיות על-השרשרת." Next paragraph: "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. The draft standard was first published Jan. 15, so the develop-branch merge landed about five months after the spec took shape." Translation: "אימות זה מכסה טקסטים מוצפנים מסוג EC-ElGamal, התחייבויות פדרסן, הוכחות סיגמא קומפקטיות והוכחות טווח מצטברות מסוג Bulletproof. מטרת העיצוב היא פשוטה: לשמור על יתרת אסימון פרטית תוך מתן אפשרות לפנקס לאשר שהחשבון נכון — שההיצע לא נופח ושהזרימות תואמות להוכחות. תקן הטיוטה פורסם לראשונה ב-15 בינואר, כך שהמיזוג לענף הפיתוח התרחש כחמישה חודשים לאחר גיבוש המפרט." Third section: "Activation is a two-week vote" -> "ההפעלה היא הצבעה בת שבועיים" Paragraph: "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." Translation: "מיזוג לענף הפיתוח אינו זהה לשחרור. לפי תהליך התיקון של XRPL, הפעלה דורשת רוב מיוחד — יותר מ-80% מהמאמתים המהימנים — שיאשרו ברציפות במשך
