---
title: "XRPL Activates fixCleanup3_4_0 Amendment to Resolve Permission Delegation Flaw"
description: "The ledger patch fixes an issue where delegates assigned to burn tokens could inadvertently mint new fungible assets."
url: https://basisdesk.news/news/xrpl-activates-fixcleanup-amendment-permission-delegation-mint-bug
published: 2026-11-05T10:06:31.521Z
modified: 2026-11-05T10:06:31.521Z
section: Tech & Protocols
author: Basis Desk Newsroom (AI-generated, source-verified)
sentiment: neutral
tickers: [XRP]
tags: [XRPL, Smart Contracts, Governance, Tokenomics]
license: Quote with attribution to Basis Desk (basisdesk.news). Not financial advice.
---

# XRPL Activates fixCleanup3_4_0 Amendment to Resolve Permission Delegation Flaw

The ledger patch fixes an issue where delegates assigned to burn tokens could inadvertently mint new fungible assets.

## At a glance

- **What happened:** XRPL activated the fixCleanup3_4_0 amendment on Nov. 4, 2026, resolving multiple protocol issues across decentralized finance modules and permission delegation.
- **Why it matters:** The fix closes a loophole where accounts with PaymentBurn permissions could mistakenly mint fungible tokens or Multi-Purpose Tokens.
- **Who is affected:** XRPL node operators, token issuers using granular permission delegation, and users of XRPL AMMs and Single Asset Vaults.
- **Takes effect:** Nov 4, 2026
- **What's next:** Issuers can safely grant PaymentBurn permissions to delegate accounts following amendment activation.
- **Status:** in-effect
- **Primary source:** [Permission Values](https://xrpl.org/docs/references/protocol/data-types/permission-values) — xrpl.org

## Key points

- The XRPL fixCleanup3_4_0 amendment was enabled on Nov. 4, 2026, at ledger 108,112,129 after a 14-day voting period.
- The patch resolves a flaw allowing delegates with PaymentBurn permission to mint fungible tokens under specific conditions.
- The amendment also bundles maintenance fixes for Single Asset Vaults, Lending Protocol, AMMs, NFTs, and MPTs.

## Editorial remark

- **Context:** The fixCleanup3_4_0 amendment was introduced in xrpld 3.4.0 on Sept. 17, 2026. It initially lost validator majority on Oct. 21, 2026, before regaining support and finishing a 14-day activation period.
- **Impact:** XRPL accounts delegating granular permissions can now safely delegate PaymentBurn without the risk of unauthorized token creation, stabilizing access controls for token issuers.
- **Watch:** Validator stability and operational status of dependent features, including Single Asset Vaults, Lending Protocol modules, and Multi-Purpose Tokens.

The XRP Ledger activated the fixCleanup3_4_0 amendment on Nov. 4, 2026, at ledger index 108,112,129, introducing a bundle of technical corrections across multiple core protocols [2]. The amendment reached activation after sustaining validator majority across a mandatory two-week voting window [2].

A critical correction within the update addresses the ledger's permission delegation engine [1], [2]. According to XRPL documentation, users were previously advised against delegating the granular "PaymentBurn" permission [1]. Before the activation of fixCleanup3_4_0, accounts granted the PaymentBurn permission could inadvertently mint new fungible assets, such as trust line tokens or Multi-Purpose Tokens (MPTs), under certain transaction conditions [1]. The activation removes this risk, restricting PaymentBurn delegates exclusively to transactions that destroy tokens without dropping balances below zero [1].

## Broad Protocol Maintenance

Beyond fixing permission delegation logic, fixCleanup3_4_0 delivers targeted cleanups across several ledger features introduced in the `xrpld` 3.4.0 software release [2]. Explorer data records that the amendment includes fixes for Single Asset Vaults, the native Lending Protocol, automated market makers (AMMs), the permissioned decentralized exchange (DEX), trust lines, NFTs, escrow, sponsorship mechanisms, and cryptographic signing functions [2]. Earlier network discussions also focused on validator reliability; for instance, core developers recently addressed an [XRPL bug dropping rotated validators from amendment votes](https://basisdesk.news/news/xrpl-bug-amendment-voting-signing-key-rotation) to maintain consensus stability.

Network data shows the amendment originally entered validator voting after being introduced in `xrpld` 3.4.0 on Sept. 17, 2026 [2]. An initial voting attempt lost its required validator majority on Oct. 21, 2026, before regaining consensus the same day to begin its successful 14-day activation countdown [2]. At the time of writing, native asset $XRP traded at $1.32.

## Sources

1. [Permission Values](https://xrpl.org/docs/references/protocol/data-types/permission-values) — xrpl.org, 2026-11-05
2. [fixCleanup3_4_0 amendment on XRPL: enabled Nov 4, 2026 - XRPLWin Explorer](https://xrplwin.com/amendment/fixCleanup3_4_0) — xrplwin.com, 2026-11-04

---
Basis Desk Newsroom · AI-generated, source-verified · https://basisdesk.news/about/how-we-use-ai