XRP Ledger targets Nov. 4 fix for unauthorized token minting

cryptonews11-03 01:24

XRP Ledger has moved closer to activating a Nov. 4 fix for a flaw that can let accounts authorized only to burn issued tokens create new ones under certain conditions. Summary Developers warn ...

Source Link

Disclaimer: Investing carries risk. This is not financial advice. The above content should not be regarded as an offer, recommendation, or solicitation on acquiring or disposing of any financial products, any associated discussions, comments, or posts by author or other users should not be considered as such either. It is solely for general information purpose only, which does not consider your own investment objectives, financial situations or needs. TTM assumes no responsibility or warranty for the accuracy and completeness of the information, investors should do their own research and may seek professional advice before investing.

Comments

We need your insight to fill this gap

Leave a comment

{"i18n":{"language":"en_US"},"isChannel":false,"data":{"share":"https://ttm.financial/m/news/2680876452?lang=en_US&edition=fundamental","thumbnail":"","is_english":true,"pubTime":"2026-11-03 01:24","share_image_url":"https://static.laohu8.com/e9f99090a1c2ed51c021029395664489","id":"2680876452","market":"fut","top_or_hot":-1,"title":"XRP Ledger targets Nov. 4 fix for unauthorized token minting","media":"cryptonews","content":"<div>\n<p>XRP Ledger has moved closer to activating a Nov. 4 fix for a flaw that can let accounts authorized only to burn issued tokens create new ones under certain conditions.\n\n\nSummary\n\n\n\nDevelopers warn ...</p>\n\n<a href=\"https://crypto.news/xrp-ledger-token-minting-flaw-fix-november-4/\">Source Link</a>\n\n</div>\n","source":"crypto_news_highlight","html":"<!DOCTYPE html>\n<html>\n<head>\n<meta http-equiv=\"Content-Type\" content=\"text/html; charset=utf-8\" />\n<meta name=\"viewport\" content=\"width=device-width,initial-scale=1.0,minimum-scale=1.0,maximum-scale=1.0,user-scalable=no\"/>\n<meta name=\"format-detection\" content=\"telephone=no,email=no,address=no\" />\n<title>XRP Ledger targets Nov. 4 fix for unauthorized token minting</title>\n<style type=\"text/css\">\na,abbr,acronym,address,applet,article,aside,audio,b,big,blockquote,body,canvas,caption,center,cite,code,dd,del,details,dfn,div,dl,dt,\nem,embed,fieldset,figcaption,figure,footer,form,h1,h2,h3,h4,h5,h6,header,hgroup,html,i,iframe,img,ins,kbd,label,legend,li,mark,menu,nav,\nobject,ol,output,p,pre,q,ruby,s,samp,section,small,span,strike,strong,sub,summary,sup,table,tbody,td,tfoot,th,thead,time,tr,tt,u,ul,var,video{ font:inherit;margin:0;padding:0;vertical-align:baseline;border:0 }\nbody{ font-size:16px; line-height:1.5; color:#999; background:transparent; }\n.wrapper{ overflow:hidden;word-break:break-all;padding:10px; }\nh1,h2{ font-weight:normal; line-height:1.35; margin-bottom:.6em; }\nh3,h4,h5,h6{ line-height:1.35; margin-bottom:1em; }\nh1{ font-size:24px; }\nh2{ font-size:20px; }\nh3{ font-size:18px; }\nh4{ font-size:16px; }\nh5{ font-size:14px; }\nh6{ font-size:12px; }\np,ul,ol,blockquote,dl,table{ margin:1.2em 0; }\nul,ol{ margin-left:2em; }\nul{ list-style:disc; }\nol{ list-style:decimal; }\nli,li p{ margin:10px 0;}\nimg{ max-width:100%;display:block;margin:0 auto 1em; }\nblockquote{ color:#B5B2B1; border-left:3px solid #aaa; padding:1em; }\nstrong,b{font-weight:bold;}\nem,i{font-style:italic;}\ntable{ width:100%;border-collapse:collapse;border-spacing:1px;margin:1em 0;font-size:.9em; }\nth,td{ padding:5px;text-align:left;border:1px solid #aaa; }\nth{ font-weight:bold;background:#5d5d5d; }\n.symbol-link{font-weight:bold;}\n/* header{ border-bottom:1px solid #494756; } */\n.title{ margin:0 0 8px;line-height:1.3;color:#ddd; }\n.meta {color:#5e5c6d;font-size:13px;margin:0 0 .5em; }\na{text-decoration:none; color:#2a4b87;}\n.meta .head { display: inline-block; overflow: hidden}\n.head .h-thumb { width: 30px; height: 30px; margin: 0; padding: 0; border-radius: 50%; float: left;}\n.head .h-content { margin: 0; padding: 0 0 0 9px; float: left;}\n.head .h-name {font-size: 13px; color: #eee; margin: 0;}\n.head .h-time {font-size: 11px; color: #7E829C; margin: 0;line-height: 11px;}\n.small {font-size: 12.5px; display: inline-block; transform: scale(0.9); -webkit-transform: scale(0.9); transform-origin: left; -webkit-transform-origin: left;}\n.smaller {font-size: 12.5px; display: inline-block; transform: scale(0.8); -webkit-transform: scale(0.8); transform-origin: left; -webkit-transform-origin: left;}\n.bt-text {font-size: 12px;margin: 1.5em 0 0 0}\n.bt-text p {margin: 0}\n</style>\n</head>\n<body>\n<div class=\"wrapper\">\n<header>\n<h2 class=\"title\">\nXRP Ledger targets Nov. 4 fix for unauthorized token minting\n</h2>\n\n<h4 class=\"meta\">\n\n\n2026-11-03 01:24 GMT+8&nbsp;&nbsp;&nbsp;<a href=https://crypto.news/xrp-ledger-token-minting-flaw-fix-november-4/><strong>cryptonews</strong></a>\n\n\n</h4>\n\n</header>\n<article>\n<div>\n<p>XRP Ledger has moved closer to activating a Nov. 4 fix for a flaw that can let accounts authorized only to burn issued tokens create new ones under certain conditions.\n\n\nSummary\n\n\n\nDevelopers warn ...</p>\n\n<a href=\"https://crypto.news/xrp-ledger-token-minting-flaw-fix-november-4/\">Source Link</a>\n\n</div>\n\n\n</article>\n</div>\n</body>\n</html>\n","isBrief":false,"type":0,"news_type":1,"symbol":"XRPZ","symbol_name":"Franklin XRP ETF","start_time":0,"source_url":"https://crypto.news/xrp-ledger-token-minting-flaw-fix-november-4/","article_id":"2680876452","we_media_id":null,"thumbnails":[],"rights":{"source":"crypto_news_highlight","url":"https://crypto.news/xrp-ledger-token-minting-flaw-fix-november-4/","rn_cache_url":null,"directOrigin":true},"url":"https://stock-news.laohu8.com/highlight/detail?id=2680876452","pubTimestamp":1793640251,"columns":[],"sourceInfo":{"source_id":"crypto_news_highlight","name":"Crypto News"},"weMediaInfo":null,"summary":"XRP Ledger has moved closer to activating a Nov. 4 fix for a flaw that can let accounts authorized only to burn issued tokens create new ones under certain conditions.Developers warn issuers against delegating PaymentBurn permission until the correction becomes active.Validator backing stands at 33 of 35, with activation dependent on sustained support.The amendment includes separate repairs for trading pools, vault accounting, and loan checks.XRPL’s official documentation identifies the problem in PaymentBurn, a permission designed to let another account destroy fungible tokens on an issuer’s behalf. Until the fixCleanup3_4_0 amendment takes effect, a delegate holding that permission can sometimes mint trust line tokens or Multi-Purpose Tokens, known as MPTs.The warning specifically excludes other granular permissions from the flaw. Its recommendation is to avoid delegating PaymentBurn while the correction remains pending.XRP Ledger fix separates token burning from issuance. In the per","collect":0,"end_time":0,"defaultTopTitle":"crypto.news","property":[],"viewcount":null,"language":"en","relate_stocks":{"XRPZ":"Franklin XRP ETF","XXRP":"2倍做多XRP ETF-Teucrium","XRPK":"T-REX 2x Long XRP Daily Target ETF","BITW":"Bitwise 10 Crypto Index ETF","XRPR":"REX-OSPREY XRP ETF","XRP":"Bitwise XRP ETF","TOXR":"21shares XRP ETF","XRPI":"1倍XRP ETF-Volatility Shares","UXRP":"Proshares Ultra XRP ETF","XRPT":"2倍杠杆XRP ETF-Volatility Shares","XRPC":"Canary XRP ETF"},"translate_title":"XRP Ledger 的目标是 11 月 4 日修复未经授权的代币铸造问题","themeId":null,"isJumpTheme":false,"ttsUrl":null,"symbols_score_info":{"XRPI":1.5,"XRPT":1.5,"XRP":1.5,"XRPR":0.6,"UXRP":1.5,"XRPC":1.5,"XRPZ":1.5,"XXRP":1.5,"XRPK":0.6,"BITW":1.5,"TOXR":1.5},"content_text":"XRP Ledger has moved closer to activating a Nov. 4 fix for a flaw that can let accounts authorized only to burn issued tokens create new ones under certain conditions.\n\n\nSummary\n\n\n\nDevelopers warn issuers against delegating PaymentBurn permission until the correction becomes active.\nValidator backing stands at 33 of 35, with activation dependent on sustained support.\nThe flaw concerns issued tokens, including stablecoins, without affecting XRP’s native supply.\nThe amendment includes separate repairs for trading pools, vault accounting, and loan checks.\n\n\n\nXRPL’s official documentation identifies the problem in PaymentBurn, a permission designed to let another account destroy fungible tokens on an issuer’s behalf. Until the fixCleanup3_4_0 amendment takes effect, a delegate holding that permission can sometimes mint trust line tokens or Multi-Purpose Tokens, known as MPTs.\nThe warning specifically excludes other granular permissions from the flaw. Its recommendation is to avoid delegating PaymentBurn while the correction remains pending.\nXRP Ledger fix separates token burning from issuance\nIn the permission reference, XRPL lists PaymentMint and PaymentBurn as separate functions. PaymentMint authorizes payments that create fungible tokens, while PaymentBurn is intended to authorize their destruction without allowing a payment to cross a zero balance.\nThe Sep. 16 release notes for xrpld version 3.4.0 describe the correction directly: payments using PaymentBurn will be rejected if they cross that boundary. The change forms part of an amendment package, meaning its inclusion in server software does not by itself activate the new transaction rule across the network.\nThe documented exposure concerns accounts that have received the affected delegated permission. Neither the permission warning nor the release notes identifies an issuer whose tokens were fraudulently created.\nXRP’s native supply falls outside this issued-token permission flaw. The affected token categories are assets created on the ledger through trust lines or the MPT framework.\nValidator support puts activation on track for Nov. 4\nAccording to the XRPLWin tracker, fixCleanup3_4_0 has backing from 33 of 35 tracked trusted validators, equivalent to 94.29%. With that validator count, 29 supporting votes are needed to clear the required threshold.\nThe projected activation time is Nov. 4 at approximately 14:46 UTC, provided support remains above 80% throughout the two-week waiting period.\nVoting history shows an initial majority running from Oct. 9 until Oct. 21, when the amendment lost the backing needed to continue its countdown. A new majority began on Oct. 21, moving the projected activation into November.\nA drop to 80% or below would interrupt the waiting period again. The tracker therefore lists Nov. 4 as a conditional activation time, rather than a completed network upgrade.\nIssuers can update or revoke delegated permissions\nXRPL’s delegation guide explains that an account owner grants another account specific powers through a DelegateSet transaction. The owner can change or revoke those permissions through another transaction of the same type.\nThe system supports separate accounts for routine operations while keys carrying full control remain offline. Its documentation gives stablecoin compliance as one use case, including approving users who have completed identity checks.\nEach delegate can receive up to 10 permissions. Certain powers, particularly those involving changes to cryptographic keys or granting further permissions, cannot be delegated.\nThe guide says granular permissions are predefined and cannot be customized to cover only selected currencies. Its PaymentBurn warning appears alongside these operating instructions.\nStablecoin distribution on XRPL has continued to develop. As crypto.news previously reported, Ripple’s RLUSD Coinbase launch on Oct. 28 covered retail and institutional platforms, with network support spanning XRP Ledger, Ethereum and Base.\nRipple identifies RLUSD’s issuer as Standard Custody & Trust Company, a New York-supervised limited-purpose trust company. Its transparency page says reserves are held in segregated accounts and monthly reports compare circulating tokens with their backing assets.\nAmendment repairs extend to vaults and lending\nBeyond permission delegation, the official amendment description lists corrections to Single Asset Vault deposits, withdrawals, and clawbacks, designed to prevent assets from being over-delivered or under-delivered through rounding.\nTrading-pool repairs address clawback amounts that round to zero and cases involving the final liquidity provider’s remaining balance.\nRipple previously backed native lending proposals intended to let single-asset vaults supply funds for fixed-term loans. Those proposals have their own validator approval process.\nWithin the cleanup amendment, loan lateness, impairment, and default checks will require the due date to have strictly passed. Another change allows a withdrawal of fixed vault shares to return zero assets when the vault is fully impaired, instead of failing the transaction.\n\n\n\n\n\n                Read more:\n            \n\n                Trade.xyz restores GitBook docs but keeps link warning in place","kind":"highlight","is_publish_news":true,"is_publish_highlight":false,"is_publish_live":false,"is_publish_wemedia":false,"editions":null,"column":"","sentiment":"0","news_tag":"","news_rank":0,"isVideo":false,"video":null,"symbols":[],"gpt_button":0,"need_auth":false,"need_login_tip":false,"code":"91000000","status":"200"},"commentList":[],"isCommentEnd":true,"newsSizeData":{"likeSize":0,"commentSize":0,"repostSize":0,"favoriteSize":0,"likeStatus":false,"favoriteStatus":false},"APP":{"userAgent":"Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)","isDev":false,"isTTM":true,"isLaohu8Offline":false,"tenantId":"TBGLOBAL","deviceId":"web-server-community-laohu8-v3","version":"4.52.1","shortVersion":"4.52.1","platform":"web","vendor":"web","appName":"ttm","isIOS":false,"isAndroid":false,"isTiger":false,"isTHS":false,"isWeiXin":false,"isWeiXinMini":false,"isWeiBo":false,"isQQ":false,"isBaiduSwan":false,"isBaiduBox":false,"isDingTalk":false,"isToutiao":false,"isOnePlus":false,"isHuaWei":false,"isXiaomi":false,"isXiaomiWebView":false,"isOppo":false,"isVivo":false,"isSamsung":false,"isMobile":false},"href":"/m/news/2680876452","isCrawlerRequest":true}