XRP Ledger developers released the xrpld v3.3.0 software on August 6, 2026, bundling amendments aimed squarely at institutional and tokenization use cases. As with every XRPL protocol change, releasing the software is only the first step — none of the new features take effect until validators vote them in.
What’s actually in v3.3.0
Coverage across outlets cites five to six amendments, with some variation in how individual features are grouped and named:
- Batch Transactions — lets a user bundle multiple transactions, up to eight, into a single submission instead of signing and sending each one individually. This is aimed at reducing overhead for accounts that need to execute several related operations atomically.
- Confidential Transfers — applies to Multi-Purpose Token (MPT) transactions and hides balances and payment amounts from public view while keeping them cryptographically verifiable. This is the feature most directly aimed at institutions that need transaction privacy for compliance or competitive reasons.
- Dynamic MPTs — makes the Multi-Purpose Token standard more flexible by allowing certain token properties to change after issuance, rather than being fixed permanently at creation.
- Permission Delegation — returns to the ledger after what multiple outlets describe as a security-focused refactor and audit process, following an earlier version of the feature.
- Sponsored Fees — allows a third party to cover a user’s transaction fee, aimed at reducing retail friction for users who don’t hold XRP for gas.
Some coverage also references node-level performance improvements bundled into the same release, including reduced memory usage for validators running the updated software.
The activation bar: 80% for 14 days, no exceptions
This is the detail that matters most for anyone tracking a specific date. XRPL amendments activate through validator voting, not developer fiat. Each amendment needs at least 80% of validators to signal support and hold that support continuously for 14 days before it becomes active on mainnet. If support dips below 80% at any point during that window, the clock resets.
That means the six amendments in v3.3.0 could activate on different schedules from each other, depending on how quickly validator operators upgrade their software and vote. A feature that clears 80% support in its first week could activate within a month; one that takes longer to gain validator confidence could sit in limbo for considerably longer. There is no way to predict the exact date from outside the validator set.
Why this matters beyond XRP price action
None of these six amendments are primarily price catalysts in the way a listing or an ETF flow number is. They’re infrastructure changes aimed at making XRPL more usable for the kind of institutional and tokenized-asset activity Ripple and allied builders have been courting — bank-grade privacy for token transfers, batch settlement for accounts managing multiple positions, and flexible token standards for assets whose terms need to change after issuance.
For builders evaluating XRPL as a settlement layer, Confidential Transfers and Dynamic MPTs are the two amendments worth the closest look, since they directly affect what kinds of tokenized instruments are practical to issue on the ledger. For validator operators, the immediate task is straightforward: upgrade to v3.3.0 and decide how to vote on each amendment, since that vote is what determines the activation timeline for everyone else.
What to watch next
The two numbers worth tracking are validator adoption of the v3.3.0 software itself and the amendment-by-amendment approval percentage, both of which are visible on public XRPL amendment-tracking dashboards. Until an amendment crosses 80% and holds it for 14 consecutive days, none of these features exist on mainnet in a way that affects users or applications — they exist only in the released software and in validator votes in progress.
Bottom line
XRP Ledger v3.3.0 is a real, released piece of software with a concrete set of institutional-facing features, but “released” and “active” are different things on XRPL. Confidential Transfers and Batch Transactions are the two changes most likely to matter for real usage once they clear the 80%-for-14-days bar; until then, this is a validator-adoption story rather than a live-feature story.
Advertisement
Sources and review
This article was checked against the primary or authoritative sources below .
- XRP Ledger 3.3.0 brings privacy and batch upgrades — crypto.news
- XRP Ledger 3.3.0 to launch next week with five amendments including revived Batch feature — Crypto Briefing
- XRP News Today: XRP Ledger 3.3.0 Upgrade Is Available With Six Major Features — Coinpedia
- XRP Ledger Launches Six-Amendment Vote, Unveils Major v3.3.0 Upgrade With Confidential Transfers and Institutional Tools — Brave New Coin
- XRP Ledger v3.3.0 Upgrade: What to Know About the Upcoming Release and New Features — KuCoin
Frequently asked questions
XRPL developers released the xrpld v3.3.0 software on August 6, 2026. That is a software release, not a mainnet activation — the amendments it contains still need validator approval before they take effect.
Coverage cites five to six amendments depending on the source's count: Batch Transactions (bundling up to eight transactions into one), Confidential Transfers (hiding balances and amounts on Multi-Purpose Token transfers while remaining verifiable), Dynamic MPTs (allowing multi-purpose token properties to change after issuance), Permission Delegation (returning after a security-focused refactor), and Sponsored Fees (letting a third party cover a user's transaction fee).
There is no fixed date. Each amendment needs at least 80% of XRPL validators to signal approval and hold that approval for 14 consecutive days before it activates. Activation depends entirely on validator adoption speed, which cannot be predicted precisely in advance.
Confidential Transfers apply to Multi-Purpose Token (MPT) transactions and let balances and payment amounts stay hidden from public view while still being cryptographically verifiable. The feature targets institutional users who need transaction privacy for compliance or competitive reasons without giving up on-chain verifiability.
Sponsored Fees let a third party pay a transaction's fee on a user's behalf, which is a fee-payment mechanism change rather than a fee-amount change. Separately, coverage has cited node performance improvements, including reduced memory usage, tied to the broader v3.3.0 release.
Advertisement