Key Highlights
- XRP Ledger’s developer committee launched the Confidential MPT standard through XLS-0096 for private token transactions.
- The framework extends XLS-33 capabilities by integrating EC-ElGamal encryption alongside zero-knowledge proof technology.
- Transaction amounts and account balances remain hidden from public blockchain observers.
- Network validators maintain the ability to confirm OutstandingAmount stays within MaxAmount limits.
- Issuer authorities retain full control over account freezing and clawback mechanisms.
The XRP Ledger (XRPL) developer committee has unveiled a privacy-oriented token framework designed to attract institutional participants. Through the XLS-0096 specification, Confidential MPTs enable encrypted balance storage and private transfer execution. This development addresses financial institution requirements while maintaining regulatory compliance mechanisms.
Confidential MPT Framework Arrives on XRP Ledger
Contributor Shawn Xie published XLS-0096 titled “Confidential Transfers for Multi-Purpose Tokens” on GitHub during the previous week. This specification enhances the established XLS-33 Multi-Purpose Token system with encrypted balance capabilities and confidential transaction processing. The framework leverages EC-ElGamal encryption combined with zero-knowledge proof technology for data protection.
The current XLS-33 standard enables versatile token creation while displaying all balance and transfer information publicly. The proposed enhancement maintains the fundamental accounting model while encrypting sensitive financial data. According to Xie, public transparency under the existing framework has restricted adoption among institutional participants. The contributor explained that Confidential MPTs “bring encrypted balances and confidential transfers without abandoning XLS-33 rules.”
Validator nodes retain the capacity to verify supply constraints under this architecture. The MaxAmount parameter establishes total supply ceilings. The protocol enforces that OutstandingAmount must not exceed MaxAmount. This verification occurs while keeping individual account balances private.
GitHub documentation details four fundamental characteristics of the specification. The initial characteristic addresses confidentiality through balance encryption and concealed transfer values. XRPL validator Vet noted this architecture prevents both validators and public observers from accessing individual account holdings.
The second characteristic preserves public verification of aggregate supply metrics. The protocol confirms OutstandingAmount compliance while maintaining encrypted confidential balances. Validators can therefore enforce supply regulations with transparency.
The third characteristic enables selective information disclosure via view keys. This design accommodates both trust-minimized on-chain auditor frameworks and issuer-managed disclosure protocols. The fourth characteristic ensures interoperability between public and confidential balance types for identical tokens.
Regulatory Tools and Enterprise Strategy for XRP Ledger
The specification preserves issuer control mechanisms within the confidential architecture. Token issuers retain account freezing capabilities and clawback execution rights when circumstances require. The protocol handles a designated issuer’s secondary account identically to standard holder accounts.
OutstandingAmount maintains its function as the aggregate of all non-issuer account balances. Issuers therefore preserve supply oversight and reserve administration capabilities. The architecture retains all XLS-33 issuance protocols while incorporating privacy enhancements.
The XRP Ledger deployed Permissioned Domains and Permissioned DEX features during the prior month. These instruments enable institutions to function within established compliance boundaries. Developer efforts currently concentrate on privacy improvements alongside these regulatory tools.
Financial institutions have historically avoided public blockchain infrastructure due to complete transaction visibility. The proposed standard aims to resolve this challenge through encrypted token balance systems. The specification applies exclusively to issued tokens and does not encompass XRP itself.
Currently, developers maintain active discussions regarding XLS-0096 on GitHub. The proposal awaits submission to the XRPL validator poll as a formal amendment. The committee has yet to establish a schedule for subsequent voting procedures.





