The XRP Ledger (XRPL) released version 3.3.0 of its reference server implementation, bringing several new amendments to validator voting. Among the six proposed changes are ConfidentialTransfer (privacy-preserving MPT transfers), BatchV1_1 (atomic batch transactions), DynamicMPT (immutable token properties), PermissionDelegationV1_1, Sponsor, and fixCleanup3_3_0. None of these amendments has yet reached the required 28‑validator consensus threshold for activation. Current voting participation is low—for example, BatchV1_1 has only two votes (5.71%), and Sponsor shows zero.
Earlier amendments, however, demonstrate successful governance: fixCleanup3_2_0 was enabled on July 29, 2026 with 85.71% consensus, and fixCleanup3_1_3 achieved 100% consensus and activated in May 2026. The release also retired five long‑active amendments—Clawback, fixDisallowIncomingV1, fixInnerObjTemplate, fixNFTokenReserve, and fixUniversalNumber—making them permanent protocol parts. RippleX software engineer Mayukha Vadari clarified that retirement is purely a codebase cleanup, removing pre‑amendment code after two years, and will not affect users.
Separately, a social media post linked development speed to a $589 XRP projection, but the amendment registry provides no support for that valuation; it only records governance data. Market analysts stress that XRP’s price depends on demand, liquidity, and broader conditions, not on voting activity. Nonetheless, the continued protocol work and rigorous amendment process highlight active, measurable development on the XRP Ledger.
