XRPL may upgrade tomorrow night: Why will it take two weeks to plug a loophole that turns “burn permission” into minting?
If the majority holds, the XRP Ledger could activate an amendment called fixCleanup3_4_0 as early as around 22:46 tomorrow night (Beijing time). Why that specific time?
I didn’t rely on screenshots of breaking news—I went straight to the amendment data on xrpscan and the official XRPL documentation. As of before posting tonight: there are 35 trusted validators, 33 in support, and 28 required; the amendment is not yet active. The more-than-80% majority has been in effect since 22:46 on October 21, Beijing time.
The rules of the XRPL (paraphrased from the official documentation):
1. New features and fixes are rolled out as “amendments” and put to a validator vote.
2. They take effect only after support exceeds 80% and remains above that threshold continuously for two weeks; once active, they apply permanently.
3. If the majority falls below the threshold at any point during those two weeks, the clock resets and starts over.
4. After an amendment takes effect, nodes that haven’t upgraded their software will be “amendment blocked”—unable to validate the ledger or process transactions.
So “as early as tomorrow night” isn’t a launch date someone picked; it’s when the two-week countdown naturally runs out.
What does this fix? According to the official description, it’s a collection of fixes involving vaults, lending protocols, AMMs, permissioned DEXs, trust lines, NFTs, MPTs, escrow, signatures, and delegated permissions. The last item is the one most people should understand:
If a delegated account is authorized only to “pay to burn,” then, under certain circumstances, a payment could cause the balance to cross zero and become a “mint.” After the fix, this kind of payment will be rejected unless the account also has “pay to mint” permission.
To put it bluntly: when an account is supposed to have permission to “burn only” but can actually “print,” that loophole should be plugged as soon as possible. But the fix has to make its way through a two-week voting process—that’s the price of decentralized upgrades.
A few reminders:
· This is a fix to the protocol rules, not an airdrop, and you don’t need to do anything. Anyone telling you to “migrate your wallet for the upgrade” or “claim new coins” is a scammer.
· If you run your own node, make sure your software version supports this amendment.
· Whether the majority holds until tomorrow night is up to the on-chain data; I can’t guarantee it.
Do you usually keep an eye on on-chain upgrade votes?
$XRP #XRPL #OnChainUpgrade
If the majority holds, the XRP Ledger could activate an amendment called fixCleanup3_4_0 as early as around 22:46 tomorrow night (Beijing time). Why that specific time?
I didn’t rely on screenshots of breaking news—I went straight to the amendment data on xrpscan and the official XRPL documentation. As of before posting tonight: there are 35 trusted validators, 33 in support, and 28 required; the amendment is not yet active. The more-than-80% majority has been in effect since 22:46 on October 21, Beijing time.
The rules of the XRPL (paraphrased from the official documentation):
1. New features and fixes are rolled out as “amendments” and put to a validator vote.
2. They take effect only after support exceeds 80% and remains above that threshold continuously for two weeks; once active, they apply permanently.
3. If the majority falls below the threshold at any point during those two weeks, the clock resets and starts over.
4. After an amendment takes effect, nodes that haven’t upgraded their software will be “amendment blocked”—unable to validate the ledger or process transactions.
So “as early as tomorrow night” isn’t a launch date someone picked; it’s when the two-week countdown naturally runs out.
What does this fix? According to the official description, it’s a collection of fixes involving vaults, lending protocols, AMMs, permissioned DEXs, trust lines, NFTs, MPTs, escrow, signatures, and delegated permissions. The last item is the one most people should understand:
If a delegated account is authorized only to “pay to burn,” then, under certain circumstances, a payment could cause the balance to cross zero and become a “mint.” After the fix, this kind of payment will be rejected unless the account also has “pay to mint” permission.
To put it bluntly: when an account is supposed to have permission to “burn only” but can actually “print,” that loophole should be plugged as soon as possible. But the fix has to make its way through a two-week voting process—that’s the price of decentralized upgrades.
A few reminders:
· This is a fix to the protocol rules, not an airdrop, and you don’t need to do anything. Anyone telling you to “migrate your wallet for the upgrade” or “claim new coins” is a scammer.
· If you run your own node, make sure your software version supports this amendment.
· Whether the majority holds until tomorrow night is up to the on-chain data; I can’t guarantee it.
Do you usually keep an eye on on-chain upgrade votes?
$XRP #XRPL #OnChainUpgrade
