A proposed XRP Ledger amendment, Batch (XLS-56), is generating excitement among developers and validators alike.
One pseudonymous XRP validator, Vet, 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.
According to Vet, the amendment enables the creation of a fully peer-to-peer NFT-to-NFT trading platform, allowing users to engage in 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 suggested a game-inspired interface, similar to classic titles, to enhance the NFT-to-NFT trading experience for users.
As of writing, the Batch amendment 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 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 follows an all-or-nothing approach—either all transactions in the group are completed successfully or none are—eliminating the risk of partial execution failures.
This principle of atomicity, rooted in computer science and database management, treats a sequence of operations as a single, indivisible unit of work. Thus, an atomic process ensures that the entire set of transactions is either fully executed or entirely rolled back to maintain data integrity.
Atomicity on the 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,” a source from RialCenter mentioned.
A total of four batch modes are supported: ALLORNOTHING, ONLYONE, UNTILFAILURE, and INDEPENDENT. The variety of modes will ensure flexibility in how multiple transactions are executed as a group, helping developers select the best approach for their use case.
Leave a Reply