What is new in version 3.3.0 of the xrpld XRP Ledger server software?

The full answer

What did XRPL.org announce on August 6, 2026?

XRPL.org announced on August 6, 2026 that version 3.3.0 of xrpld, the reference server implementation of the XRP Ledger protocol, is now available [1]. The release notes say it introduces several new amendments alongside bug fixes and build improvements [1]. They also tell anyone running an XRP Ledger server to upgrade to 3.3.0 as soon as possible to ensure service continuity [1].

Which new amendments does it add?

The Sponsor amendment (XLS-68) is the one the release notes describe most plainly. XRPL.org says it lets companies, token issuers and other entities subsidize transaction costs and reserve requirements for end users, and that sponsors can co-sign transactions or pre-fund sponsorships while the people they sponsor keep control of their accounts and keys [1].

A second amendment, fixCleanup3_3_0, is a bundle of amendment-gated bug fixes. One part unifies freeze and deep freeze checks for transfers to and from pseudo-accounts in the vault, AMM and loan broker deposit and withdraw transactions [1]. The notes also say a new amendment fixes and replaces the original Batch amendment, which version 3.1.1 had disabled [1].

That earlier disabling is the main caution in the history. XRPL.org’s blog said version 3.1.1, released February 23, 2026, superseded 3.1.0 and disabled the Batch and fixBatchInnerSigs amendments because of a severe bug [2]. The blog also lists a February 26, 2026 vulnerability report from XRPL Labs on unauthorized inner transaction execution in the Batch amendment [2].

What does the release retire?

XRPL.org says version 3.3.0 retires the long-active Clawback, fixDisallowIncomingV1, fixInnerObjTemplate, fixNFTokenReserve and fixUniversalNumber amendments, making them a permanent part of the protocol [1]. XRPL.org’s August 6, 2026 release note for xrpld 3.3.0 lists the retired amendments as Clawback, fixDisallowIncomingV1, fixInnerObjTemplate, fixNFTokenReserve and fixUniversalNumber [3]. The release also strengthened Clawback invariant checks for multi-purpose token balances [1].

Are the new amendments live?

Shipping code is not the same as enabling it. On crypto.news’s account of the 3.4.0 release, adding rules to server software did not activate them on mainnet [4]. Amendments go live only through validator voting. How that works is covered in how XRP Ledger amendments are approved. The wider picture of what is running and what is planned is in the XRP Ledger features page.

jakeclaver.com stated on August 28, 2026: “Amendment Introduced Mainnet status fixCleanup3_3_0 3.3.0 Majority reached 28 Aug 2026, activates 11 Sep ConfidentialTransfer 3.3.0 Not enabled BatchV1_1 3.3.0 Not enabled PermissionDelegationV1_1 3.3.0 Not enabled DynamicMPT 3.3.0 Not enabled Sponsor 3.3.0 Not enabled … As of today none of them are enabled on mainnet.” [5]

What came after 3.3.0, and what are the criticisms?

XRPL.org announced version 3.4.0 on September 16, 2026 [3], and its notes again told operators to upgrade as soon as possible [3]. On September 25, 2026 the blog listed version 3.4.1 as an emergency release to fix security-sensitive issues in the XRPL protocol [2].

The strongest critique concerns the Sponsor design. On September 21, 2026 XRPL.org published a vulnerability disclosure report on XLS-68 Sponsored Fees and Reserves, with a reported date of August 7, 2026, the day after 3.3.0 was announced [2]. The index entry does not say what the fix was, and no read source ties the report to a specific later release. The lending side of the upgrade path is covered in whether native lending is live.

The 3.4.1 notes credit RippleX Engineering and the XRP Ledger Foundation for the build [2].