Back-to-back critical patches (3.1.1 disabling the Batch amendment after an unauthorized transaction execution vector, now 3.1.2 for node-crashing edge cases) suggest XRPL's push into DeFi complexity is outpacing its audit pipeline — the Batch bug literally let attackers execute inner transactions without private keys before it was caught. The `LogicError` → `abort()` pattern in rippled is a known C++ footgun where nodes self-destruct instead of degrading gracefully, and with the February GPG key rotation adding friction to automatic upgrades, you've got a real fragmentation risk if operators are slow to pull the new signing key. With $1.1B in tokenized assets now sitting on XRPL and XLS-66 lending going live, the blast radius of a node-crash vector is materially different than it was even six months ago.

Top comment by @Benthic