XRP Ledger, the decentralized blockchain built for global payments, is just one vote away from bundling related transactions into a single operation, making multi-step transfers seamless.
The activation of the so-called Batch V1.1 upgrade would let users combine as many as eight transactions into one operation. Such bundling transactions into a single “atomic” block means they either all succeed together or fail together, completely eliminating the risk of failed partial transfers.
Two people swapping tokens, for example, could make sure both transfers complete together instead of one person sending funds only to find the other side failed.
The upgrade had support from 27 of 35 trusted validators in a Tuesday snapshot, or roughly 77%. XRP Ledger changes need 80% backing, a threshold set so that alterations to the network only take effect when almost every trusted operator agrees. That makes a single holdout decisive at this stage, and one more vote would start the two-week countdown toward activation.
Support must remain above that threshold for the full 14 days before the change takes effect, and validators can change their votes during that period.
This push for activation follows a series of 11 critical bug fixes. On Monday, Ripple’s developer arm, RippleX, detailed the repairs in a technical review of the Batch V1.1 feature, which has not yet gone live on the main network.
The Batch V1.1 amendment shipped in xrpld 3.3.0 and is now up for voting.After the v1.0 signature bug was caught in February (pre-Mainnet, no funds at risk), we rebuilt it: root-cause fix, 4 senior reviewers, a Sherlock attackathon, and audits from Halborn and Common Prefix. We…
The latest review found 11 issues involving signatures, authorization checks and bugs that could crash servers. One flaw rated critical by security firm Common Prefix could have allowed an attacker to reuse a user's signed permission to execute more transactions than intended.
RippleX said the review involved four senior engineers, audits from Halborn and Common Prefix, a public security contest and automated testing.
Meanwhile, RippleX says commercial projects using Batch are under contract or in development, although it has not named the companies as of Tuesday. CoinDesk asked RippleX which companies are waiting to use Batch and whether the 11 additional fixes were independently reviewed against the version validators are now voting on.
Wallets and marketplaces could also use the feature to combine a customer payment with a platform fee, ensuring both are processed together.
The wait follows a much more serious problem found earlier this year. Researchers discovered a flaw in the original Batch proposal that could, under certain conditions, allow an attacker to include transactions from somebody else's account without that person's approval.
Source
This article is syndicated for educational reading. For the latest updates, visit the original publisher.
Read on coindesk.com
