The XRP Ledger (XRPL) developer community is currently buzzing about the successful return of a highly anticipated network upgrade.
The “Batch” amendment, which was previously delayed due to security concerns, has been merged back into the core repository and is now queued for validator voting.
The announcement was made by XRPL core developer Denis Angell, who confirmed the integration following a rigorous period of testing and review.
“Batch is BACK!!” Angell declared on X (formerly Twitter). “After an attack-athon, a security audit, and 4 reviews, the batch is officially merged back into the xrpld repo and will be up for voting in the next release.”
Angell accompanied his announcement with a quote from Confucius: “A man who has committed a mistake and doesn’t correct it is committing another mistake.”
The pull request has been officially merged from Angell’s branch into the development branch of the XRPLF/rippled repository.
What the amendment means for XRPL
Prominent XRPL community validator and commentator Vet praised the core development team in light of the most recent development. “Massive shoutout to Denis and the whole core dev community for prioritizing the rework with huge amounts of security audits,” Vet posted.
An “atomic” transaction means that a series of operations is executed as a single unit. Either all the transactions within the bundle succeed together.
According to Vet, this atomic bundling capability unlocks crucial new functionalities for the network.
Users can bundle a “send” and a “receive” transaction together, ensuring that a token swap only executes if both parties fulfill their end of the trade simultaneously.
Developers can bundle complex interactions into a single transaction block.
Network validators will vote on its activation in an upcoming rippled release.






Be the first to comment