A proposed XRP Ledger amendment, Batch (XLS-56), is generating excitement among developers and validators alike.
One pseudonymous XRP validator, Vet, has shared his experience testing the Batch functionality on the dev net, where multiple transactions, including minting and payments for non-fungible tokens (NFTs), can be bundled and executed automatically.
The amendment, according to Vet, enables creation of a fully peer-to-peer NFT-to-NFT trading platform, allowing users to perform a barter-like NFT swaps in a single transaction.
For instance, one could trade five of their NFTs for two NFTS owned by another party, all processed simultaneously to ensure atomicity and security, Vet said on X, suggesting a game-inspired interface, similar to the classic RuneScape, to make this NFT-to-NFT trading more engaging and intuitive for users.
As of writing, the Batch amendment has achieved 68.57% consensus among validators, with 80% required for activation. XRP Ledger (XRPL) is a decentralized, open-source blockchain used by Ripple to build cross border payments solution.
What is the Batch amendment?
The Batch amendment introduces atomic transaction capabilities to the XRP Ledger, allowing multiple operations to be grouped and executed simultaneously as a single unified transaction.
It takes the all or nothing approach – either all transactions in the group are completed successfully or none are, thereby eliminating the risk of partial execution failures.
This principle of atomicity has its roots in computer science and database management, where a sequence of operations is treated as a single, indivisible unit of work. Therefore, an atomic process means that the entire set of transactions is either fully executed or entirely rolled back to ensure data integrity.
Atomicity on XRP Ledger could be valuable in complex NFT trades or swaps involving multiple steps, facilitating the development of sophisticated NFT marketplaces.
“This new amendment drastically changes the functionality of the XRP Ledger by allowing the grouping and ordering of up to 8 transactions into a single batched operation. It also introduces atomic execution via ALLORNOTHING as one of its execution modes for batched transactions,” Teucrium said in a Substack post.
A total of four batch modes are supported: ALLORNOTHING, ONLYONE, UNTILFAILURE, and INDEPENDENT. The availability of four modes will ensure flexibility in how multiple transactions are executed as a group, helping developers choose the best approach for their use case.