XRPL sets conditional activation of fixed BatchV1_1 amendment after critical flaw
- —30 of 35 trusted validators backed BatchV1_1, above the 28-vote threshold
- —Support must stay above 80% for two weeks or activation is cancelled
- —The original Batch amendment never activated after a February authorization flaw
- —xrpld 3.3.0 shipped BatchV1_1 support on Aug. 6; older servers become amendment-blocked
Why it matters: The activation will test whether XRPL's amendment process can safely ship critical changes and keep servers, wallets and libraries in sync.
Source: Cryptonews.net