The $XRP Ledger is getting one of its biggest updates in a long time, moving from version 3.2.1 to version 3.3.0. The upgrade brings six new features, though not all of them are as new or exciting as they sound.
How XRPL Updates Actually Work
The $XRP Ledger runs on a network of computers called nodes, all connected to each other and all running the same software, known as $XRP Ledger D. The “D” stands for daemon, which is just a technical term for a background service.
Version numbers follow a simple pattern: major changes update the first number, new features update the second number, and small bug fixes update the third number. Going from 3.2.1 to 3.3.0 means new features are being added, not a fundamental overhaul of how the network works.
Batch: Bundling Transactions Together
The new Batch feature lets users bundle up to eight transactions into one now, rather than signing each one individually. One version of this feature, called all-or-nothing mode, ensures a group of transactions either all succeed together or none of them happen at all, a concept known as atomic settlement.
This matters most for two use cases: letting retail apps monetize more easily, and enabling what’s called delivery versus payment for institutions, where two parties can exchange cash and assets with complete certainty that the trade either fully completes or doesn’t happen at all.
Permission Delegation: Sharing Control Without Losing It
This feature lets institutions hand over specific transaction permissions to other parties without giving up overall control. For example, Ripple could use this to let partner banks help mint its $RLUSD stablecoin, similar to how Circle already allows partners to help mint USDC. That could expand how much $RLUSD gets issued without Ripple handling every transaction itself.
Sponsor: Removing a Technical Barrier for New Users
Right now, doing almost anything on the $XRP Ledger requires locking up some amount of $XRP, whether that’s activating an account, creating a trading offer, or holding tokens and NFTs. The Sponsor feature lets companies cover $XRP reserve costs for their users now, meaning a business like a neobank could pay these technical costs on a customer’s behalf, making it possible for everyday users to interact with the XRPL without needing to understand its underlying reserve requirements.
Confidential Transfers: Limited Privacy, Not Full Anonymity
Confidential Transfers hides balances only for the multi-purpose token standard, the newer token type built for tokenizing real-world assets like stocks and bonds. This does not hide $XRP balances, $NFT holdings, or standard IOU tokens.
With this feature, the fact that a transfer happened remains visible, but the actual amount being sent, and how much someone held beforehand, stays hidden. Institutions can still selectively disclose that information for tax or compliance purposes when needed. Broader privacy features covering entire accounts, and potentially $XRP itself, are expected to arrive later, likely next year.
Two Features That Are Less Than They Sound
Dynamic MPT simply makes the multi-purpose token standard more flexible by allowing its properties to change after a token is created, a useful but fairly minor enhancement. Fix Cleanup isn’t really a feature at all. It’s simply a bundle of software and security fixes rolled into the update. Two of the six announced features are actually less significant than the others, based on how the update was framed.
Of everything included in version 3.3.0, Batch is expected to have the most impact on everyday users, since it directly improves how transactions feel to use on the network.
