source avatarLeviathan News

Share

Ripple says asset managers are preparing for the XRP Ledger's Batch V1.1 amendment, which would let up to eight transactions settle atomically. The upgrade could also let exchanges, wallets and marketplaces attach service charges directly to a customer transaction, processing a payment and the platform's fee as one operation rather than through separate transfers. "Some projects are already being built with Batch in mind, so activation would allow that work to move closer to production," Akinyele said, adding that more on specific partners and launch timing will be shared as plans are finalized. The amendment has support from 30 of the XRP Ledger's 35 tracked validators, above the 28 votes required to enter its activation countdown, which began Sept. 15 at 14:06:41 UTC. Batch V1.1 is projected to activate shortly after the same time on Sept. 29, provided support remains at or above 80% for the full 14-day window. Validators can change their votes, making the date conditional. The approaching activation follows a security failure that caused developers to withdraw the original version. Researchers found a critical flaw in Batch V1.0's signature-validation process in February. Under certain conditions, the code could stop checking signatures early and allow an attacker to include transactions from another account without its owner's authorization.

No.0 picture
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.