Batch (XLS-56), a proposed fix for the XRP Ledger, is generating excitement among developers and validators alike.
A pseudonymous XRP validator, Vet, shared his experience on devnet testing a batch feature that can bundle and automatically execute multiple transactions, including non-fungible token (NFT) minting and payments.
According to Vet, this modification will enable the creation of a fully peer-to-peer NFT-to-NFT trading platform, allowing users to perform barter-like NFT swaps in a single transaction.
For example, five NFTs can be exchanged for two NFTS owned by another party, all processed simultaneously to ensure atomicity and security, the veterinarian said in X, proposing a game-inspired interface similar to the classic RuneScape to make this NFT-to-NFT transaction more appealing and intuitive for users.
At the time of writing, the proposed batch fix 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 payment solutions.
X Posts of XRP Validator Vet. (×)
What is Bulk Fix?
The Batch fix introduces atomic transaction functionality to the XRP Ledger, allowing multiple operations to be grouped and executed simultaneously as a single unified transaction.
It takes an all-or-nothing approach where either all transactions in the group complete successfully or none complete, which eliminates the risk of partial execution failures.
This principle of atomicity has its roots in computer science and database management, where a set of operations is treated as a single, indivisible unit of work. Therefore, an atomic process means that the entire set of transactions is fully executed or completely rolled back to ensure data integrity.
The atomicity of the XRP Ledger is valuable in complex NFT transactions and swaps that involve multiple steps, facilitating the development of sophisticated NFT marketplaces.
“This new fix significantly changes the functionality of the XRP Ledger by allowing up to eight transactions to be grouped and ordered into a single batch operation. It also introduces atomic execution with ALLORNOTHING as one of the 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 provides flexibility in how multiple transactions are executed as a group, allowing developers to choose the approach that best suits their use case.