$XRP had a critical bug that could theoretically mint tokens out of thin air.
RippleX patched it first, details dropping in 2 weeks.
They claim they reproduced it on isolated servers and found zero evidence of exploitation on mainnet.
The fix (xrpld 3.4.1) shipped Sept 25 and went live immediately—skipping the usual amendment activation process.
Real question: when you emergency-patch a live chain, how do you manage consensus risk across validators running different versions?
This is the kind of supply-side risk most people ignore until it's too late.
RippleX patched it first, details dropping in 2 weeks.
They claim they reproduced it on isolated servers and found zero evidence of exploitation on mainnet.
The fix (xrpld 3.4.1) shipped Sept 25 and went live immediately—skipping the usual amendment activation process.
Real question: when you emergency-patch a live chain, how do you manage consensus risk across validators running different versions?
This is the kind of supply-side risk most people ignore until it's too late.