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 also fixed a few other bugs our new AI red-teaming efforts caught along the way.

What changed and why it's ready: dev.to/ripplexdev/bat…

Atomic transactions on the XRPL, no smart contracts needed. Try it on Devnet today.

Sep 14, 2026 · 1:55 PM UTC

13
47
274
64,532
RepliesRelevant
Replying to @msvadari
@msvadari What i think when i hear AI Red Team
1
1
42
1,431
Replying to @msvadari
@msvadari 👀 👀 👀
0
1
8
557
Replying to @msvadari
@msvadari @RippleXDev Atomic transactions 👀
0
0
2
336
Replying to @msvadari
@msvadari How come XRPL labs isn’t voting ?
0
0
1
177
Replying to @msvadari
@msvadari Actively watching for this to pass 👀👀👀
0
0
0
239
Replying to @msvadari
@msvadari #XRP It's happening. Lock in XRP. Let's Go $XRP! 🚀🚀🚀🚀
0
1
2
153
Replying to @msvadari
@msvadari When Mainnet?
0
0
1
147
Replying to @msvadari
@msvadari batch is going to make user experience SO much better 🙌
0
0
1
102
Replying to @msvadari
@msvadari Waiting on the CEO @daniel_wwf
1
0
1
251
Replying to @msvadari
@msvadari @msvadari @Vet_X0

So many questions here. Guess I have to wait…

Partners, who?
Contracted use cases, for what?

“The business case is concrete: named partners, contracted use cases, and protocol-level dependencies are waiting on this capability”
0
0
0
200