The BatchV1_1 proposal, introduced in version 3.3.0, seeks to allow users to bundle up to eight transactions into a single coordinated operation. According to XRPScan data, the current 68.57% support level necessitates at least five additional affirmative votes to cross the activation threshold. Because XRPL rules mandate that this support level be maintained continuously for fourteen days, any dip in validator backing resets the timer, making any specific September activation date purely speculative.
In section Cryptocurrency
XRP Ledger Batch Amendment Stalls Below 80% Threshold
With 24 of 35 validators currently backing the BatchV1_1 amendment, the XRP Ledger remains short of the 80% support required to trigger its mandatory two-week activation window. Despite anticipation surrounding the feature, the ledger’s governance process ensures no countdown will begin until a stable supermajority is reached.
Technically, the amendment introduces four execution modes—all-or-nothing, only-one, until-failure, and independent—designed to streamline complex actions like atomic token swaps and NFT minting. This proposal replaces an earlier batch implementation that was scrapped in February after researchers Pranamya Keshkamat and Cantina AI identified a critical authorization vulnerability. While that initial flaw was caught before mainnet activation, the rewritten version underwent independent audits to address signer verification errors. Beyond the vote itself, node operators must run compatible software and update Clio infrastructure to version 2.8.0 to ensure the ledger can process the new transaction formats once the amendment eventually goes live.
Comments (0)
No comments yet. Be the first!