Home » Blockchain » XRP Ledger 3.3.0: New Amendments, Fixes and Status

XRP Ledger 3.3.0: New Amendments, Fixes and Status

xrpld 3.3.0 brought back Batch and Permission Delegation after both were pulled over bugs, and added the fixCleanup3_3_0 bundle of AMM, vault and lending fixes. Here is what shipped and…

Abstract network security imagery representing the XRP Ledger security upgrade

On August 6, 2026, the XRP Ledger project published xrpld 3.3.0, the reference server software for the network. The release is mostly about amendments, the voted-in protocol changes that XRP Ledger uses to add features. Two of them, Batch and Permission Delegation, return in corrected form after earlier versions were pulled over bugs. A third, fixCleanup3_3_0, bundles many small corrections.

What’s actually in xrpld 3.3.0?

According to the release notes on xrpl.org, the new amendments are:

  • BatchV1_1 (XLS-56): lets an account submit up to 8 inner transactions that succeed or fail together. It replaces the original Batch amendment, which was disabled in version 3.1.1.
  • PermissionDelegationV1_1: lets an account give limited permissions to another account. It replaces the original amendment and fixes a critical bug in that version.
  • fixCleanup3_3_0: a bundle of fixes covering the automated market maker (AMM), the permissioned DEX, Checks, Single Asset Vaults, the Lending Protocol and pseudo-accounts.
  • Sponsor (XLS-68): lets a third party cover fees and reserves for a user.
  • ConfidentialTransfer (XLS-0096) and DynamicMPT (XLS-94): new features for Multi-Purpose Tokens (MPTs).

The release also retires five long-active amendments (Clawback, fixDisallowIncomingV1, fixInnerObjTemplate, fixNFTokenReserve and fixUniversalNumber), making them permanent protocol rules. It adds hardening against oversized validator manifests and peer messages. The release notes say operators should upgrade as soon as possible but give no hard deadline.

What does fixCleanup3_3_0 change?

It’s a maintenance amendment. The release notes don’t describe it as a response to an exploit, and we found no report of one. They list these changes:

  • Freeze and deep-freeze checks are unified for transfers to and from pseudo-accounts in the vault, AMM and lending-broker deposit and withdraw transactions.
  • CheckCash and CheckCancel reject an all-zero CheckID during preflight, which is an earlier and cleaner failure.
  • Hybrid offers stay on the open order book if the placing account loses access to its permissioned domain.
  • AMM liquidity is no longer counted in quality estimates for permissioned DEX order books.
  • AMMWithdraw returns a clean error instead of dividing by zero at one specific price value.
  • A precision-loss check is added to AMMDeposit, AMMWithdraw and AMMClawback when the fixAMMv1_3 amendment is also enabled.
  • A new ObjectHasPseudoAccount invariant checks that deleting a ledger entry backed by a pseudo-account also deletes the pseudo-account.
  • Further precision and rounding fixes for Single Asset Vaults and the Lending Protocol.
  • Transactions signed by a pseudo-account fail, and pseudo-accounts are rejected as the subject of credentials or deposit preauthorizations.

The rounding checks matter because an AMM holds a pool of two assets and prices swaps from the pool’s balances. If deposits or withdrawals lose a tiny amount to rounding, repeated transactions could in principle shift value in an unintended direction. The precision-loss check makes such transactions fail instead. The release notes describe the check, not an attack, so we don’t claim anyone exploited this.

Who Benefits and How

XRP holders have nothing to do. Node operators and validators handle upgrades, and holders don’t need to move funds because of a software release. The release notes describe no change to balances or fee levels.

The benefit is mostly indirect. For people who use the XRP Ledger’s built-in features, such as the AMM, Checks or the permissioned DEX, the cleanup amendment aims to make edge-case failures cleaner and rounding safer. Batch, once live, lets an account group up to 8 inner transactions so they all succeed or none do. Permission Delegation lets one account hand limited permissions to another. Each feature only helps once its amendment is active, and the status table below shows where each stands. Nothing here is investment advice, and protocol upgrades say nothing about the price of XRP.

Which of these amendments are live?

An amendment activates only after more than 80% of the trusted validator list supports it for two weeks. With 35 validators on that list, that means at least 29 votes held for 14 days. A release shipping an amendment doesn’t mean the feature is live.

Amendment Status in sources we opened Source
PermissionDelegationV1_1 Reported live late on Oct 8, 2026 Analytics Insight (Oct 9)
BatchV1_1 Earliest activation Oct 9 after a countdown reset; a relayed disclosure summary says the related fixBatchV1_2 activated Oct 9 Cryptometer (Sept 26), AltcoinBuzz (Oct 6), KuCoin relay
fixCleanup3_3_0 Reached majority Aug 28 with 29 yes votes (82.86% of 35 validators); earliest activation Sept 11. We did not find a confirmation Analytics Insight (Sept 1)
Sponsor, ConfidentialTransfer, DynamicMPT Still in voting as of Aug 21; no later status found Coingape (Aug 21)

If support for fixCleanup3_3_0 had dropped to 80% or below, the two-week clock would have restarted. The Single Asset Vault and Lending Protocol amendments are separate. Coingape reported on August 21 that Ripple voted yes on them, but we found no source confirming they are live on mainnet. The fixes for those features may therefore apply to code that ordinary users can’t reach yet. Check the XRPL.org known amendments page or a live amendment tracker such as XRPScan for current status before you rely on any of these.

What was wrong with the earlier versions?

The release notes say the first Batch amendment was disabled in 3.1.1 and that the first Permission Delegation amendment contained a critical bug. Neither page gives exploit details in the sections we read. Secondary outlets describe the Batch problem as a signature-validation flaw found during testing and say the amendment never reached the live network. We couldn’t trace the names of researchers or audit firms that some outlets cited back to an official document, so we leave them out.

The story didn’t end with 3.3.0. A later vulnerability report, relayed by KuCoin from other news outlets, says versions 3.3.0 and 3.4.0 had a separate Batch issue involving an unenforced wrapper field, fixed by the fixBatchV1_2 amendment in 3.4.1. See our Batch explainer for that history.

Is 3.3.0 still the current version?

No. An emergency release, xrpld 3.4.1, followed on September 25, 2026 to fix a payment engine overflow bug. Operators on older versions are reported to be amendment-blocked after October 9.

What’s an amendment, and what’s a pseudo-account?

An amendment is a protocol change that the XRP Ledger enables only after more than 80% of trusted validators support it for two weeks. Batch, for example, bundles up to 8 inner transactions into one atomic group: either all succeed or none do. A pseudo-account is a system-controlled account that backs objects such as AMM pools and vaults. It has no private key that a person controls.

Was fixCleanup3_3_0 a response to a hack?

Nothing we read says so. The release notes present it as a bundle of corrections. They list the changes but don’t rank them by severity or say whether any were exploitable.

How firm are these dates and numbers?

  • Validator vote counts are snapshots. Support can drop below 80% and reset the two-week clock, as it did for Batch.
  • The 82.86% figure is validator support for fixCleanup3_3_0 as reported on Sept 1. It says nothing about how serious the fixes are.
  • Sept 11 was the earliest possible activation date for fixCleanup3_3_0. We couldn’t confirm the actual date.
  • Some details come from news outlets that rely on dashboards such as XRPScan, and we couldn’t open the XRPL.org amendments page directly. Treat dates as reported, not confirmed.
  • The release notes don’t describe the original Batch and Permission Delegation bugs in detail, so we can’t say how serious they were beyond the word “critical” used for Permission Delegation.
  • Node upgrade percentages circulated in other coverage. We couldn’t verify them against a primary source, so we don’t repeat them. We also couldn’t verify claims that fixCleanup3_3_0 is the third cleanup amendment in four months.

Sources

Related Reading