Back
XRPL 3.3.0 moves privacy, batching and token features closer to mainnet, but none are live yet

XRPL 3.3.0 moves privacy, batching and token features closer to mainnet, but none are live yet

The Aug. 6 release adds node software for ConfidentialTransfer, BatchV1_1, Sponsor and DynamicMPT, but each amendment still needs more than 80% validator support for two continuous weeks.

XRP

Fact Check
The official XRPL.org blog confirms v3.3.0 released 2026-08-06 with exactly six amendments (BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1, Sponsor, fixCleanup3_3_0) targeting privacy (Confidential Transfer), settlement (Sponsor/Batch) and tokenized-asset use cases (DynamicMPT). Coingape independently corroborates six amendments with the same privacy/settlement/tokenization framing and the ≥80% validator threshold over two weeks for activation. Cryptonews and U.Today cite 'five' amendments, but this reflects counting only feature amendments and excluding the fixCleanup3_3_0 bug-fix amendment — consistent with, not contradicting, the six-amendment official list. The urging to upgrade and validator-voting activation requirement are confirmed by both the official blog and secondary sources.
Summary

XRP Ledger developers released xrpld 3.3.0 on Aug. 6, adding protocol code for several proposed features but leaving any mainnet rollout subject to validator approval. The update moves ConfidentialTransfer, BatchV1_1, Sponsor and DynamicMPT closer to possible activation, while the XRP Ledger amendment process still requires more than 80% support from trusted validators for two continuous weeks. ConfidentialTransfer is designed to shield Multi-Purpose Token balances and transfer amounts while preserving compliance access for authorized parties, BatchV1_1 restores atomic transaction handling after an earlier version was halted over a signing flaw, Sponsor would let third parties cover fees and reserves without taking control of user accounts, and DynamicMPT would let issuers modify selected token properties later. The release also underlines that software availability is not the same as production deployment: earlier Batch and Permission Delegation proposals were stopped before activation after bugs were found, and claims that six upgrades are already live misread the 3.3.0 release.

Terms & Concepts
  • ConfidentialTransfer: A proposed XRPL amendment that uses cryptography to hide certain MPT balances and transfer amounts while still allowing authorized compliance checks.
  • BatchV1_1: A proposed XRPL amendment that lets multiple transactions be grouped so they execute together or fail together.
  • Multi-Purpose Token: An XRPL token format designed for flexible issuance and management features that can support business and compliance needs.