A proposed amendment to the XRP Ledger, Batch (XLS-56), is generating excitement among developers and validators.
A pseudonymous XRP validator, Vet, shared his experience testing the Batch functionality on the devnet, where multiple transactions, including minting and non-fungible token (NFT) payments, can be batched and executed automatically.
The amendment, according to Vet, allows for the creation of a fully peer-to-peer NFT-to-NFT trading platform, allowing users to perform barter-style NFT swaps 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, Vet said on
At the time 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 create a 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 into a single unified transaction.
It takes the all-or-nothing approach: either all transactions in the group complete successfully or none do, 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 set of transactions is either completely executed or completely rolled back to ensure data integrity.
Atomicity on XRP Ledger could be useful in complex NFT transactions or exchanges involving multiple steps, facilitating the development of sophisticated NFT markets.
“This new amendment radically changes the functionality of the
A total of four batch processing 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.
