The amendment was still being considered by validators and had not activated, meaning the vulnerable code never governed the live ledger and no funds were exposed.
Meanwhile, RippleX did more than patch the individual error before returning the feature for another vote, Akinyele said.
“We used it as an opportunity to go much deeper on the implementation, redesign parts of the signing and authorization model, and significantly expand the security review,” he said.
The replacement shipped in xrpld version 3.3.0, released Aug. 6. That implementation is the same code validators are now voting to activate, according to Akinyele.
The review included internal adversarial testing, AI-assisted analysis, a Sherlock attack contest and assessments by security firms Halborn and Common Prefix.
“The bigger point is that we established a very high bar,” Akinyele added. “We found a serious issue in V1.0 before activation, stopped it, redesigned and hardened the implementation, expanded the review considerably, and only then put V1.1 back in front of validators.”
The amendment will remain in its countdown through Sept. 29. If validator support drops below 80% before then, the clock stops and a new 14-day window must begin after the proposal regains the required majority.
Powered by WPeMatico
