XRPL Lists Expected Sept. 11 Activation for fixCleanup3_3_0

WHO, WHAT, WHEN, WHERE

On August 6, 2026, xrpl.org published release notes for xrpld 3.3.0, the reference server for the XRP Ledger. The matching GitHub tag on XRPLF/rippled is signed. The version-bump commit is 00a178fb92ca49521b937ae1a99d863765ea8a90, titled “Bump version to 3.3.0.” [1] [2]

The 3.3.0 notes list six new amendments, including fixCleanup3_3_0, described as an amendment-gated bundle of bug fixes. Publishing a server version does not enable those amendments on the public network. An amendment enables only after more than 80 percent of trusted validators support it continuously for two weeks. [1] [3]

As of September 6, 2026, the official Known Amendments page lists an expected activation date of 2026-09-11 for fixCleanup3_3_0. The official livenet amendments dashboard shows the same expected date, records the amendment as not enabled, and reports 29 of 35 votes (82.86 percent) against a 28-of-35 threshold. [4] [5]

CONFIRMED EVIDENCE

The 3.3.0 blog post identifies xrpld 3.3.0 as the current reference server and states that operators should upgrade to 3.3.0 for service continuity. Installer packages and SHA-256 checksums are published with the notes. Installation instructions point to the XRPL installation documentation. [1] [7]

The six new amendments named in the 3.3.0 notes are BatchV1_1 (XLS-56), ConfidentialTransfer (XLS-0096), DynamicMPT (XLS-94), PermissionDelegationV1_1, Sponsor (XLS-68), and fixCleanup3_3_0. The same notes say 3.3.0 retires several long-active amendments: Clawback, fixDisallowIncomingV1, fixInnerObjTemplate, fixNFTokenReserve, and fixUniversalNumber. [1]

The 3.3.0 notes describe fixCleanup3_3_0 as covering these protocol-code changes:

• Unify freeze and deep-freeze checks for pseudo-account transfers in VaultDeposit and VaultWithdraw, AMMDeposit and AMMWithdraw, and LoanBrokerCoverDeposit and LoanBrokerCoverWithdraw.
• CheckCash and CheckCancel reject an all-zero CheckID as temMALFORMED in preflight.
• Hybrid offers are no longer dropped from the open book when the placer loses permissioned-domain access.
• AMM liquidity is no longer included in permissioned DEX quality estimates.
• AMMWithdraw returns tecAMM_FAILED instead of a divide-by-zero tefEXCEPTION for one EPrice case.
• A precision-loss check on AMMDeposit, AMMWithdraw, and Clawback when fixAMMv1_3 is also enabled.
• A ValidAMM invariant: an AMM is deleted only by AMMWithdraw, AMMClawback, or AMMDelete.
• An ObjectHasPseudoAccount invariant.
• Further vault and lending precision and rounding fixes.
• Pseudo-account-signed transactions fail tefBAD_AUTH, including when LendingProtocol or BatchV1_1 is enabled.
• CredentialCreate and DepositPreauth reject pseudo-accounts with tecPSEUDO_ACCOUNT.

That list is the release note’s own description of the gated fixes. It is not independent proof that each item has already taken effect on mainnet. [1]

XRPL amendment documentation states that an amendment becomes permanently enabled after more than 80 percent of trusted validators support it continuously for two weeks. The network checks this on a flag ledger every 256 ledgers, about every 15 minutes. Votes appear in validations. EnableAmendment pseudo-transactions can carry tfGotMajority, tfLostMajority, or, when the two-week window completes, an unflagged enable. If support falls to 80 percent or below, the two-week clock resets. Servers that lack the amendment’s code become amendment blocked: they cannot validate, submit transactions, or vote. [3]

On the Known Amendments page as retrieved on September 6, 2026, fixCleanup3_3_0 shows Expected: 2026-09-11. The other 3.3.0 feature amendments remain listed as Open for Voting, with these support figures: BatchV1_1 65.71 percent, ConfidentialTransfer 22.86 percent, DynamicMPT 22.86 percent, PermissionDelegationV1_1 31.43 percent, and Sponsor 14.29 percent. The same page records fixCleanup3_2_0 as enabled on 2026-07-29 and fixCleanup3_1_3 as enabled on 2026-05-27. [4]

The official livenet explorer lists fixCleanup3_3_0 with amendment ID 3298D47E1F3A8A24FECAA30F699B8FE1DD234E072834BA099AD8180FFCE0FEC4. It reports 29 UNL voters, a 28-of-35 threshold, 82.86 percent consensus, enabled: No, and an eta of 9/11/2026. The same dashboard reports BatchV1_1 at 23 of 35 (65.71 percent), ConfidentialTransfer at 8 of 35, DynamicMPT at 8 of 35, PermissionDelegationV1_1 at 11 of 35, and Sponsor at 5 of 35. Those figures match the Known Amendments percentages. They do not show those five amendments in a majority window. [5] [5]

A later xrpl.org post, dated August 20, 2026, announces Clio 2.8.0 built with libxrpl 3.3.0. It states that if any of the six 3.3.0 amendments enable and a Clio instance is older than 2.8.0, that ETL path becomes amendment blocked. The post points operators to the livenet amendments dashboard. [6] [5]

CONTEXT AND TIMELINE

xrpld is the reference server maintained in the XRPLF/rippled repository. The 3.3.0 notes are published on xrpl.org. Those protocol records are distinct from statements by Ripple the company. This article reports server, amendment, and operator records, not a company announcement. [1] [2]

Cleanup amendments of this kind have a recent pattern on the Known Amendments page: fixCleanup3_1_3 enabled on May 27, 2026, and fixCleanup3_2_0 enabled on July 29, 2026. That history shows how prior cleanup amendments reached enablement. It does not prove that fixCleanup3_3_0 will complete its window. [4]

Operators running pre-3.3.0 servers face a documented risk if an amendment they do not support becomes enabled: amendment blocking. The 3.3.0 notes therefore treat the upgrade as service continuity, not as a network-governance vote. Clio operators have a parallel continuity requirement at 2.8.0 if any of the six new amendments enable. [1] [3] [6]

WHAT REMAINS UNKNOWN OR DISPUTED

The September 11, 2026 date is an expected activation listed by official XRPL pages. It is not a confirmed enablement. If trusted-validator support falls to 80 percent or below, the two-week clock resets and the date moves. [3] [4]

This article does not record the exact ledger or timestamp when fixCleanup3_3_0 first gained a majority. Third-party explorers have published such timestamps. Those timestamps do not appear on the official Known Amendments page or the official livenet dashboard reviewed for this draft, so they are not treated as confirmed here.

Vote counts change as validators update. The 29-of-35 snapshot is the official livenet dashboard reading as of September 6, 2026. It is not a forecast of the September 11 tally. XRPScan’s amendments list, retrieved the same day, showed the same 29 of 35 support figure; its amendment detail page did not load for this review and is used only as corroboration. [5] [8]

The other five 3.3.0 amendments remain below 80 percent in the official counts. This article does not infer if or when they will enter a majority window.

WHAT READERS SHOULD WATCH NEXT

Watch the Known Amendments page for a change from an expected date to an enabled date for fixCleanup3_3_0. Watch the livenet amendments dashboard for the enabled flag, the 29-of-35 count, and any drop that would reset the two-week clock. Watch whether BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1, or Sponsor crosses the 80 percent threshold. Operators should confirm their xrpld and Clio versions against 3.3.0 and 2.8.0 before any of those amendments enable, because servers without the new code become amendment blocked. [4] [5] [6]

SOURCES AND DISCLOSURES

[1] xrpl.org blog, “xrpld 3.3.0,” published August 6, 2026, including the six new amendments, retired amendments, operator upgrade note, packages, and SHA-256 checksums:
https://xrpl.org/blog/2026/xrpld-3.3.0

[2] GitHub signed tag 3.3.0 on XRPLF/rippled, including commit 00a178fb92ca49521b937ae1a99d863765ea8a90 (“Bump version to 3.3.0”):
https://github.com/XRPLF/rippled/releases/tag/3.3.0

[3] XRPL documentation, “Amendments,” including the two-week >80 percent rule, flag ledgers, EnableAmendment flags, clock reset, and amendment blocking:
https://xrpl.org/docs/concepts/networks-and-servers/amendments

[4] XRPL Known Amendments page, retrieved September 6, 2026, listing fixCleanup3_3_0 expected 2026-09-11 and the Open for Voting percentages for the other 3.3.0 amendments:
https://xrpl.org/resources/known-amendments

[5] Official livenet amendments dashboard and fixCleanup3_3_0 record (ID 3298D47E1F3A8A24FECAA30F699B8FE1DD234E072834BA099AD8180FFCE0FEC4), retrieved September 6, 2026, showing 29 of 35 votes, 82.86 percent consensus, enabled: No, eta 9/11/2026:
https://livenet.xrpl.org/amendments
https://livenet.xrpl.org/amendments/3298D47E1F3A8A24FECAA30F699B8FE1DD234E072834BA099AD8180FFCE0FEC4

[6] xrpl.org blog, “Clio 2.8.0,” published August 20, 2026, built with libxrpl 3.3.0 and warning that older Clio becomes amendment blocked if any 3.3.0 amendment enables:
https://xrpl.org/blog/2026/clio-2.8.0

[7] XRPL installation documentation, linked from the 3.3.0 release notes:
https://xrpl.org/docs/infrastructure/installation

[8] XRPScan amendments list, retrieved September 6, 2026, used only to corroborate the 29 of 35 figure. The amendment detail page did not load for this review:
https://xrpscan.com/amendments

Disclosure: This is a sourced protocol and process report, not investment advice, not a recommendation to buy, sell, or hold XRP, and not an instruction to upgrade or delay an upgrade as a market decision. The September 11, 2026 date is an expected activation on official XRPL pages, not confirmed enablement. Votes can fall and reset the two-week clock. No paid placement, sponsorship, or affiliate relationship with the XRP Ledger Foundation, Ripple, or the cited sources was used. The featured illustration was generated for CryptoWorkPro and is not a documentary photograph of a ledger event or a copy of project artwork.