A proposed XRP Ledger change, Batch (XLS-56), is generating excitement among developers and validators alike.
A pseudonymous XRP validator, Vet, has shared his experience testing the Batch functionality on the dev network, where multiple transactions, including minting and payments for non-fungible tokens (NFTs), can be aggregated and executed automatically.
The change, according to Vet, enables the creation of a fully peer-to-peer NFT-to-NFT trading platform that allows users to perform a barter-like NFT swap in a single transaction.
For example, one could trade five of their NFTs for two NFTS owned by another party, all processed simultaneously to ensure atomicity and security, said Vet at X, who suggested a game-inspired interface similar to the classic RuneScape to make this NFT-to-NFT trade more engaging and intuitive for users.
At the time of writing, the Batch plugin has achieved 68.57% consensus among validators, with 80% required for activation. The XRP Ledger (XRPL) is a decentralized, open source blockchain used by Ripple to build cross-border payment solutions.
What is the batch surcharge?
The batch addition introduces atomic transaction capabilities to the XRP Ledger, allowing multiple operations to be grouped together and executed simultaneously as a single aggregated transaction.
It takes the all-or-nothing approach – either all transactions in the group complete successfully or none do, eliminating the risk of partial execution errors.
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 committed or completely rolled back to ensure data integrity.
Atomicity on the XRP Ledger can be valuable in complex NFT trades or swaps involving multiple steps, facilitating the development of sophisticated NFT marketplaces.
“This new change drastically changes the functionality of the XRP Ledger by allowing the grouping and ordering of up to 8 transactions in a single batch operation. It also introduces atomic execution via ALLORNOTHING as one of its execution modes for batch 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 performed as a group, helping developers choose the best approach for their use case.
