In a recent X Spaces session hosted by XRPL dUNL validator Vet, Ripple’s Chief Technology Officer (CTO), David Schwartz, provided insights into the unfolding scenario surrounding the automated market maker (AMM) implementation delay on the XRP Ledger. Acknowledging the visible actions of XRPL validators causing the delay, Schwartz expressed satisfaction with the transparency exhibited by the broader XRPL community.
The delay stemmed from a bug discovered by RippleX, the developer arm of Ripple, on February 1. Initially anticipated to launch on February 14 after attaining the minimum validator consensus, the XLS-30D amendment faced a setback when some validators retracted their Yes votes, pushing the consensus below the crucial 80% threshold.
Schwartz, in response to these developments, commended the XRPL community for handling the bug discovery in a public and transparent manner. He stated, “Sometimes, I’m like, ‘I wish that didn’t happen,’ but overall, the process is pretty good. Everybody got to express their views. Things didn’t always go the way that I thought, and that’s good.”
Emphasizing the importance of community involvement in decision-making, Schwartz noted that a private decision-making approach would be less favorable than the current transparent process. While expressing a desire for less acrimony, he acknowledged the passionate nature of community discussions, recognizing the value of diverse opinions.
Despite the contentious atmosphere, Schwartz expressed hope that the community members would not harbor real acrimony. He reiterated Ripple’s commitment to the swift evolution of the XRPL while prioritizing safety, assuring the community that the company has no hidden agenda regarding any amendment.
The decision by some validators, including XRPL Labs, Vet, xSpectar, and Eminence, to revoke their Yes votes was prompted by the identification of a bug causing minor transaction delays of three to five seconds. In light of this discovery, these validators chose to retract their support, emphasizing the importance of not passing an amendment with known issues.
As of the latest update, major players like Ripple, Bitso, XRPScan, Bifrost, Bithomp, Alloy Networks, and 17 other notable dUNL validators have maintained their Yes votes. However, the consensus currently stands at 65.71%, falling short of the required threshold.
Explaining their actions, validators highlighted the significance of upholding the integrity of the XRP Ledger and the broader community by not endorsing an amendment with a known bug. They committed to reinstating their Yes votes once a fix is implemented.
RippleX has taken steps to address the bug, with developers reviewing the fix. The solution is anticipated to be part of the upcoming XRPL version, rippled 2.1.0, slated for release within one to two weeks. This proactive approach aims to ensure the smooth implementation of the AMM feature once the bug is effectively addressed.
In navigating this challenge, Ripple and the XRPL community exemplify a commitment to transparent communication, collaborative decision-making, and the overarching goal of advancing blockchain technology responsibly. As the bug resolution progresses, the XRPL community eagerly anticipates the realization of the AMM feature and the continued evolution of the XRP Ledger. The collaborative efforts and transparent communication within the XRPL community exemplify a commitment to ensuring a secure and efficient upgrade to the XRP Ledger, showcasing the resilience and adaptability of blockchain ecosystems in the face of unforeseen challenges.
