XRP Ledger Proposes Confidential Transfers and Institutional Upgrades for Tokenized Assets
Table of Contents
You might want to know
1. How would a Confidential Transfers feature change visibility for tokenized institutional holdings on the XRP Ledger?
2. Which other institutional-focused amendments are included in the XRPL 3.3.0 proposal, and how might they affect operational workflows?
Main Topic
The XRP Ledger's latest software release, version 3.3.0, introduces a package of proposed amendments aimed at institutional users and issuers of tokenized real-world assets. The most prominent of these is a "Confidential Transfers" feature that would allow certain token balances and payment amounts to be encrypted while keeping account identifiers and token types visible on the ledger. The objective is to enable institutions to move Multi-Purpose Tokens (MPTs)—a token standard XRPL has been promoting for funds, bonds and other financial instruments—without publishing the exact size of positions or transfers.
Technically, Confidential Transfers are designed so the ledger can still validate transactions without learning the underlying amounts. This is achieved through cryptographic proofs that demonstrate the validity of a transfer while concealing the numeric details. As a result, the network retains the ability to verify that totals and constraints are met, even though individual balances and transfer quantities are encrypted. This key insight significantly impacts the understanding of how privacy and verifiability can coexist on a public ledger.
The proposed update is deliberately narrow in scope for its initial implementation. Participation in encrypted balances is opt-in; token holders must choose to use the encrypted format. The feature currently supports direct MPT payments between accounts but does not extend to the ledger's built-in decentralized exchange, escrow mechanisms, or check transactions. Those limitations mean Confidential Transfers targets a specific set of institutional use cases—primarily direct transfers where privacy of amounts is a priority—while leaving broader marketplace visibility and settlement mechanics unchanged.
Version 3.3.0 contains five additional amendments aimed at institutional workflows and operational convenience. "Batch" enables grouping multiple transactions (up to eight) into a single package and includes an optional all-or-nothing mode so either every step in the batch succeeds or none do. This can simplify multi-step operations and reduce the risk of partial execution in complex processes. "Sponsor" permits one account to cover another account's transaction fees and reserve requirements, removing the prerequisite for a new participant to hold the ledger's native token before transacting—this can ease onboarding for institutional clients or end customers managed by custodians.
Other amendments include "Permission Delegation," which allows an account to authorize another party to submit only specified types of transactions. This grants limited administrative capabilities—useful for fund administrators or custodial arrangements—without transferring full control of an account. "Dynamic MPT" offers issuing entities the ability to modify certain token properties after issuance, introducing flexibility for evolving contractual or operational terms tied to a token. Collectively, these tools are aimed at reducing friction for institutional issuers and managers operating on XRPL.
XRPL 3.3.0 also bundles performance improvements and bug fixes. According to XRPL Operations notes accompanying the release, the update reduces node memory usage by an estimated 10% to 15% and improves node catch-up performance. These operational efficiencies matter for institutions running validator nodes or large-scale infrastructure, as they can lower resource requirements and speed synchronization with the network.
None of the proposed changes are active yet. The XRP Ledger's amendment activation model requires at least 80% endorsement from trusted validators sustained continuously for a two-week window before an amendment can go live. Confidential Transfers and the related institutional amendments must clear that threshold before they take effect. Following activation, the more practical question will be adoption: whether issuers already on XRPL—such as Aviva Investors, Ondo, VERT Capital and others—choose to adopt encrypted balances and the related features in production.
There is already a material amount of tokenized value on the ledger for these features to serve. Onchain trackers report that roughly $1.38 billion of tokenized real-world assets have been issued on XRPL, with a large portion concentrated in several issuers. One stable token family accounts for a majority share, leaving more than $530 million of tracked tokenized assets spread among other issuers. That concentration means Confidential Transfers would initially affect a subset of assets and issuers, and its practical impact will depend on whether those issuers opt into the encrypted format and integrate the new transaction types into their operational flows.
From a governance and market-design perspective, Confidential Transfers illustrates a broader trade-off between transparency and privacy on public ledgers. For institutions, the ability to obscure amounts can protect trading strategies, portfolio allocations and client confidentiality. For the broader ecosystem, that opacity can make on-chain monitoring and market analysis more challenging. The XRPL approach tries to balance these concerns by keeping token types and account identities visible while concealing only the numeric details—preserving a degree of auditability without exposing sensitive financial information.
Key Insights Table
| Aspect | Description |
|---|---|
| Confidential Transfers | Encrypts balances and payment amounts for opt-in MPT transfers while keeping accounts and token types visible. |
| Batch Transactions | Allows grouping up to eight transactions, including an all-or-nothing mode to ensure atomic execution. |
| Sponsor | Enables one account to cover another's fees and reserves, simplifying onboarding and custodial flows. |
| Permission Delegation | Permits limited authorization for an account to submit specified transaction types on behalf of another. |
| Dynamic MPT | Lets issuers modify defined token properties after issuance to accommodate changing requirements. |
| Adoption Threshold | Amendments require 80% validator support for two continuous weeks before activation. |
Afterwards...
Looking forward, the XRPL 3.3.0 proposals point to several technology and policy areas worth further exploration. At the technical level, advancing cryptographic primitives that enable private yet verifiable transactions—such as zero-knowledge proofs or other succinct verification methods—remains a high-impact area. These methods can broaden the set of on-ledger activities that preserve confidentiality without sacrificing auditability or regulatory compliance.
Operationally, custody and identity frameworks that integrate selective disclosure and permissioning will be important. Institutions will need standards and tooling for managing key material, opting accounts into privacy features, and delegating limited authorities securely. Research into modular permissioning models and interoperable custody APIs would reduce friction for issuers and their service providers.
From a governance perspective, the industry should continue to examine how privacy features interact with regulatory obligations such as anti-money laundering and tax reporting. Developing on-chain compliance patterns—where relevant information can be disclosed to authorized parties while remaining private to the public—will be essential. Exploring privacy-preserving compliance mechanisms that satisfy both institutional confidentiality and regulatory transparency is a practical next step.
Finally, real-world adoption and market behavior will determine the long-term value of these amendments. Observing whether major issuers opt into Confidential Transfers and how that choice affects liquidity, secondary trading and market analysis will provide empirical data to guide future design. Continued collaboration between ledger developers, institutional issuers, custodians and regulators will be necessary to refine the technology and operational practices so that tokenized finance on public ledgers can scale securely and efficiently.