EnabledTier BSecurity
fixCleanup3_4_0
The bundled fix for xrpld 3.4.0 corrects edge cases in vaults, lending, AMMs, the permissioned DEX, escrow, sponsorship, and delegation. fixCleanup3_4_0 is enabled on the XRP Ledger. xrpscan reports Nov 4, 2026 (UTC) as its activation date and xrpld 3.4.0 as its first version.
Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder
- Status
- Enabled
- XLS
- No separate XLS
- Version
- xrpld 3.4.0
- Enabled
- Nov 4, 2026 (UTC)
What does this amendment fix?
What changes compared with the predecessor?
Who is this change relevant to?
What limitations and risks remain?
Technical details: transactions, fields, codes and invariants
Transactions
- VaultDeposit
- VaultWithdraw
- VaultClawback
- VaultSet
- LoanSet
- LoanManage
- LoanBrokerCoverWithdraw
- AMMBid
- AMMClawback
- AMMDeposit
- AMMWithdraw
- OfferCreate
- Payment
- NFTokenCreateOffer
- MPTokenAuthorize
- EscrowFinish
- EscrowCancel
- SponsorshipTransfer
Ledger objects
- Vault
- Loan
- LoanBroker
- AMM
- Offer
- MPToken
- Escrow
- RippleState
Fields and flags
- SponsorSignature / CounterpartySignature (separate signing prefixes)
- CredentialIDs (new in VaultWithdraw)
- asfDisallowIncomingTrustline (also applies to OfferCreate)
- tfMPTUnauthorize
- AssetsTotal / AssetsMaximum
Result codes
- tecPSEUDO_ACCOUNT
- tecAMM_FAILED
- tecDUPLICATE
- tecNO_PERMISSION
- tecINSUFFICIENT_RESERVE
- temBAD_CURRENCY
- temMALFORMED
Invariants
- ValidVault no longer blocks VaultSet when accrued interest alone raises AssetsTotal above AssetsMaximum.
- ValidPermissionedDEX ignores deleted domains and requires an offer to match its domain's order book.
- ValidMPTBalanceChanges and ValidMPTTransfer are enforced and also apply to failed transactions.
How does this amendment relate to others?
Every direct relationship has a type, an explanation and a primary source.