The XRP Ledger (XRP Ledger·XRPL) is preparing to activate a batch feature that processes multiple transactions as a single bundle.
The feature was withdrawn once after a signature-validation flaw was discovered in February, then regained validator support after being revised.
However, activation on September 29 will take place only if the approval rate remains at the required level for the remaining period.
3-Line Summary
1. The batch feature processes transactions together
2. 29 of 35 validators support it
3. Activation on September 29 is still scheduled
Bundling Up to 8 Transactions, With All Canceled if One Fails
The batch amendment, XLS-56, creates a single bundle of up to 8 transactions originating from different accounts and processes them within the same ledger close. The key principle is “all or nothing.” If even one transaction in the bundle fails or slippage caused by a price difference occurs, the network rolls back the entire bundle.
This structure can be used to complete interdependent transactions simultaneously, such as asset transfers and payments. Examples under discussion include delivery-versus-payment, in which ownership of tokenized securities and payment are processed at once, and directly exchanging different NFTs. It has also been proposed for decentralized-exchange use cases in which multiple orders are sent together and the remaining orders are canceled if only the first order succeeds.
The important point is that this is not simply a feature for increasing the number of transactions. Rather, it confirms the success or failure of interdependent transactions together. It is designed to reduce situations in which only one side is processed, leaving assets or orders mismatched.
The February Signature-Validation Flaw Was Discovered Before Mainnet Activation
The first batch V1.0 was halted after a flaw in the signature-validation logic was discovered on February 19. According to reports, the error could cause the system to skip checking the remaining signers when it encountered a signature from an account not yet registered on the ledger. In that case, there was a risk that arbitrary transactions could be executed without the private keys of the other accounts.
However, because the feature had not been activated on mainnet at the time, no actual financial losses occurred. After reproducing the issue, Ripple’s engineering team stopped supporting the existing batch amendment and related amendment proposals.
RippleX (RippleX·the XRP Ledger development organization) subsequently redesigned the structure and said it had undergone reviews by security firms Halborn and Common Prefix, as well as public stress testing. The revised code was included in node software xrpld 3.3.0.
82.86% Support Does Not Equal Confirmed Activation
According to XRPScan, as of September 15, 29 of the total 35 validators supported the batch amendment, recording 82.86%. XRP Ledger amendments are automatically activated when support above 80% is maintained for 14 days.
Wikitree reported that, if this support level remains in place, the batch feature will be activated at 2:06 p.m. UTC on September 29 local time, or 11:06 p.m. Korea Standard Time on the same day. Therefore, these figures do not mean that the feature is already live; they mean that it has entered the process of meeting the activation requirements.
On September 11, the error-correction amendment fixCleanup3_3_0 was already activated on the XRP Ledger. However, this amendment improved transaction pathways related to lending protocols, vaults, and automated market makers; it does not mean that a native lending service was launched. The batch feature should likewise be evaluated by distinguishing its proposed use cases from its actual activation status.
References
Tags #XRP레저 #XRPL #XRP #리플 #배치기능 #XLS56 #블록체인 #검증인 #원자적정산 #xrpld #XRPScan #암호화폐 #토큰화증권