NEWS
XRPL Closes a Burn Permission That Could Also Mint
A November 4 XRP Ledger vote would stop burn-only partners from minting issued tokens, after a two-hour dip reset the clock and lending still lags.
A November 4 XRP Ledger upgrade would stop burn-only partners from minting issued tokens without a separate mint right. On November 2, 33 of 35 trusted validators backed the fixCleanup3_4_0 amendment, four votes above the 29 it needs.
The hole hits issued tokens, including stablecoins and multi-purpose tokens. Native XRP supply does not run through this permission. The feature that created the hole has been live since October 8.
Permission Delegation Went Live With One Unsafe Switch
On October 8 at 9:29 PM UTC, ledger 107,524,865 enabled PermissionDelegationV1_1. An account can now grant another account up to 10 specific powers without sharing its keys, which is the model a stablecoin issuer wants for a payments desk, a compliance desk, or a redemption desk.
One of those powers is PaymentBurn, value 65546, meant for payments that destroy issued tokens. PaymentMint, value 65545, is the separate power to create them. Official docs still tell operators to do not delegate the PaymentBurn permission until fixCleanup3_4_0 is on, because a burn-only helper can also mint trust line tokens or MPTs in some cases. Other granular permissions are not affected.
THE PAYMENTBURN WARNING
Until the fixCleanup3_4_0 amendment is enabled, it is recommended not to delegate the PaymentBurn granular permission. Before the fix, a delegate with the PaymentBurn granular permission can also mint new fungible tokens (trust line tokens or MPTs) in certain circumstances. Other granular permissions are unaffected.
XRP Ledger Permission Values documentation, xrpl.org
That warning has been sitting on a live mainnet feature for weeks. Issuers who wanted a partner to redeem tokens during cash-outs were told, in the same pages that sell the helper-account model, to leave the redemption switch off. Minting and burning belong on two keys. Until the amendment takes effect, they do not.
How a Burn Crosses Zero and Becomes a Mint
The failure is not a stolen issuer key. It is a balance boundary. When a holder sends an issued token back to its issuer, the payment engine redeems what the holder actually has. If the payment is larger than that balance and the issuer is willing to hold the holder’s own IOUs, the engine can cross zero and issue new tokens in the holder’s name. That second step is a mint.
Developers wrote the case into the protocol tests. Alice holds 50 units of a gateway USD. Bob is granted only PaymentBurn on Alice’s account. Bob then sends 100 of that USD back to the gateway. Before the fix, the engine redeems Alice’s 50 and then mints 50 Alice-issued USD. After the fix, the same payment fails with terNO_DELEGATE_PERMISSION. A 20-unit burn is allowed. A burn of the remaining 30 is allowed and settles at zero. One more unit is refused.
THE UNIT TEST THAT SHOWS THE HOLE
| Action | Before fixCleanup3_4_0 | After the fix |
|---|---|---|
| Alice holds 50 gateway USD; Bob has PaymentBurn only | 50 held | 50 held |
| Bob pays 100 USD to the gateway | Redeems 50, then mints 50 Alice USD | Rejected, terNO_DELEGATE_PERMISSION |
| Bob pays 20 USD | Not the failing path | Allowed; Alice left with 30 |
| Bob then pays the remaining 30 | Not the failing path | Allowed; balance settles at zero |
| Bob pays 1 more | Would mint | Rejected; nothing left to burn |
The patched code rejects a burn that crosses zero unless the same delegate also holds PaymentMint. A helper that is supposed to destroy tokens during a redemption cannot print a matching pile on the way through. There is no public claim that anyone used the path on mainnet. The docs treated it as a reason not to grant the permission at all.
Two Hours on October 21 Restarted the Clock
Bug fixes that change how transactions process still need an amendment. More than 80% of trusted validators must back the change for 14 days in a row. With 35 validators in the tracked Unique Node List, that is 29 yes votes, checked at flag ledgers about every 15 minutes. One miss, even a short one, and the two weeks start over.
The code was bundled into the 3.4.0 release published on September 16. Validators opened a first majority on October 9, which pointed at October 23. On October 21 support fell to 26 of 35, under the 29-vote line, then recovered the same day. XRPLWin records the new majority at ledger 107,807,489. That reset moved the earliest switch from October 23 to November 4 at 14:46 UTC, a 12-day slip caused by a same-day dip.
THE ROAD TO NOVEMBER 4
- September 16, 2026: xrpld 3.4.0 is published with fixCleanup3_4_0 and LendingProtocolV1_1.
- October 8, 2026: PermissionDelegationV1_1 activates at 9:29 PM UTC on ledger 107,524,865, with the PaymentBurn warning still in the docs.
- October 9, 2026: fixCleanup3_4_0 first reaches majority, putting October 23 on the calendar; the Batch amendment went live in the same window after its own security resets.
- October 21, 2026: support drops to 26 of 35, then returns; a second 14-day clock starts at ledger 107,807,489.
- November 2, 2026: XRPLWin shows 33 yes votes and two not voting; the amendment is not yet enabled.
- November 4, 2026: earliest activation at 14:46 UTC, only if the majority never falls to 80% or below.
A two-hour slip should not cost a security patch 12 extra days, and that is the rule the network wrote for itself. The same process that stops a bad feature also stops a small permission fix. On November 2 the tracker showed 33 of 35 trusted validators, 94.29%, which is four votes above the floor. That is a cushion the first attempt did not have.
The Same Bundle Also Fixes Vaults and Loans
fixCleanup3_4_0 is not a minting patch with a few extras. Amendment ID 98433DD001A5737F773D74F8CA2A25A065089C73B2E611C760BAF369E4FECA76 is a collection of transaction-rule fixes from the 3.4.0 server for vaults, lending, AMMs, the permissioned DEX, trust lines, NFTs, MPTs, escrow, sponsorship, signing, and permission delegation. The PaymentBurn change is one line in that list.
WHAT ELSE THE BUNDLE CHANGES
- Incoming trust lines: The asfDisallowIncomingTrustline flag now also blocks OfferCreate, so an issuer’s block cannot be walked around by posting an offer.
- AMM clawback: A clawback can no longer burn a holder’s pool tokens while recovering zero after integer MPT rounding floors the amount, and it can bypass an owner-reserve check when it must create the paired holding.
- Vault totals: Deposit, withdraw, and clawback rounding is tightened so tracked total assets, available assets, and share supply stay in line.
- Loan arrears: Checks for overdue, impaired, or defaulted loans now require that the contractual due date has already passed, so a record cannot look late before it is due.
- Sponsor signatures: Counterparty and sponsor signatures get distinct hash prefixes, so a signature made for one role cannot be copied into the other.
Several of those vault and loan transaction types cannot even be delegated. The cleanup is patching math on a lending stack that validators have not turned on. That is the other half of the 3.4.0 release talking: the network is willing to correct accounting in code that is still waiting for its own vote.
Lending Still Needs 10 More Validator Votes
LendingProtocolV1_1 shipped in the same 3.4.0 notes as the cleanup. It adds closed-ended vaults with subscription, investment, and redemption phases, and it moves vault books to cash-basis accounting so interest is recognized when it is paid, not when a loan is originated. After that amendment, new loan brokers can only be created against closed-ended vaults.
That is not live. On November 2 the tracked votes sat well under 29.
VALIDATOR VOTES ON NOVEMBER 2
| Amendment | Votes of 35 | Short of 29 | Status |
|---|---|---|---|
| fixCleanup3_4_0 | 33 | 0 (4 above) | Activating Nov 4, 14:46 UTC if it holds |
| Single Asset Vault (XLS-65) | 21 | 8 | Voting, no 14-day clock |
| LendingProtocol (XLS-66) | 19 | 10 | Voting, no 14-day clock |
| LendingProtocolV1_1 | 19 | 10 | Voting, no 14-day clock |
Vaults are the dependency. Lending is the product. Both still need a supermajority before their own two-week wait can start. A cleanup that prepares loan records not to show arrears early is not the same thing as turning lending on. Issuers who wanted helper accounts for redemptions got the permission system in October and a warning instead of a working burn switch. Credit desks are still looking at 19 votes.
Native XRP Got a Same-Day Patch
The PaymentBurn hole is the second minting problem XRPL engineers closed in this cycle, and the first one did not wait 14 days. On September 22, Cayden Liao and Veria AI reported an integer overflow in the payment engine through the bug bounty program. RippleX reproduced a path that could create spendable XRP from nothing by summing too many offers, raised the finding to critical, and shipped xrpld 3.4.1 on September 25. More than 80% of default UNL validators ran that build the day it came out. The public write-up on October 9 said the project found no evidence the overflow was used on any public network.
That overflow could have touched native XRP, so operators upgraded and the rule changed with the binary. PaymentBurn cannot touch native XRP, so it goes through the amendment table, the 29-vote line, and a clock that already ran down to two days, broke, and started again. The helper-account model for banks and stablecoin issuers is what made the second hole reachable on mainnet. Closing it still depends on the same 14-day hold that a two-hour dip already spent once.
If the 33 yes votes hold through every flag ledger, fixCleanup3_4_0 takes effect at 14:46 UTC on November 4 and the docs can drop the PaymentBurn warning. If support touches 80% or less even once, the wait starts over, and issuers keep leaving redemption rights off a feature that has been on since October 8.
Disclaimer: This article is news reporting on XRP Ledger protocol votes and documentation. It is informational only and is not investment, trading, or legal advice. It does not recommend buying, selling, or holding XRP or any issued token, and it does not tell issuers, validators, or payment firms how to configure accounts. Readers who operate servers, issue tokens, or allocate capital should consult a qualified securities lawyer, compliance officer, or licensed financial adviser before acting. Vote counts, activation times, and software status reflect the cited trackers and docs as dated in this piece and can change at the next flag ledger.
-
BUSINESS5 months agoAramco Crash Kills 14 Two Days After Oil Restart
-
NEWS6 months agoSalah Captained Egypt to Their First World Cup Win
-
GAMING2 months agoZelda’s 40th Switch 2 Ships Without a Zelda Game
-
NEWS3 months agoApple Labor Day Deals Hide June’s Memory Price Hike
-
NEWS4 months agoEl Niño Puts Israel’s Needed Winter Rain on a Flood Clock
-
GAMING2 months agoPalworld 1.0.4 Adds Palpedia Search After the 1.0 Launch
-
NEWS4 months agoSaudi Visa Routes Split Nigerian Travelers Into Two Speeds
-
BUSINESS9 months agoBAE’s 60-Year Saudi Franchise Now Runs Through Taif
