{"id":19325,"date":"2026-09-16T08:21:48","date_gmt":"2026-09-16T08:21:48","guid":{"rendered":"https:\/\/icobench.com\/fr\/?p=19325"},"modified":"2026-09-15T10:22:58","modified_gmt":"2026-09-15T10:22:58","slug":"xrp-ledger-lamendement-batch-v1-1-frole-lactivation","status":"publish","type":"post","link":"https:\/\/icobench.com\/fr\/news\/xrp-ledger-lamendement-batch-v1-1-frole-lactivation\/","title":{"rendered":"XRP Ledger : l’amendement Batch V1.1 fr\u00f4le l’activation"},"content":{"rendered":"
Selon les derni\u00e8res actualit\u00e9s XRP, l\u2019amendement Batch V1.1 du XRP Ledger a recueilli le soutien de 27 des 35 votes de validateurs de confiance lors d\u2019un instantan\u00e9 mardi, soit environ 77 %. Ce r\u00e9sultat laisse la proposition \u00e0 une seule voix du seuil de 80 % requis pour d\u00e9clencher le compte \u00e0 rebours d\u2019activation de 14 jours.<\/p>\r\n
S\u2019il est activ\u00e9, cette fonctionnalit\u00e9 permettrait aux utilisateurs et aux applications de regrouper jusqu\u2019\u00e0 huit transactions li\u00e9es en une seule op\u00e9ration. Ces transactions group\u00e9es seraient \u00ab atomiques \u00bb, ce qui signifie qu\u2019elles r\u00e9ussiraient ou \u00e9choueraient toutes ensemble.<\/p>\r\n
<\/p>
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\u2026<\/p>\u2014 Mayukha Vadari (@msvadari) September 14, 2026<\/a><\/blockquote>