XRPL fixes critical pre-mainnet flaw, but client apps remain at risk
XRPL validators have conditionally scheduled the BatchV1_1 amendment for activation on Sept. 29, provided support stays above the required 80% for two weeks. The replacement follows a critical authorization flaw found in the original Batch amendment before mainnet activation; validators blocked that version, and XRPL Labs said no funds were at risk. BatchV1_1 rewrites authorization checks and adds safeguards against malformed signatures and replay. Support has shipped in xrpld 3.3.0 and compatible signing in xrpl.js 5.1.0; outdated servers may become amendment-blocked after activation. Developers must also inspect individual transaction results, since an outer batch can succeed while inner transactions fail. Activation will test software and client compatibility, but does not establish user adoption or increased XRP demand.
