- Ripple has recently faced backlash within the XRP Ledger (XRPL) developer community over an edited podcast clip.
- The edited podcast was part of Ripple’s new series called “Exploring Ripple’s New Stablecoin Ripple USD (RLUSD)”.
- Notable figures in the community have expressed their dismay and disappointment over what they see as Ripple’s lack of transparency.
The controversy over Ripple editing a podcast clip has ignited frustration among the XRPL developer community, highlighting ongoing tensions between Ripple and its developer base.
Ripple Sparks Outrage by Editing Podcast Clip
Ripple is under scrutiny for altering a segment in its recently launched podcast series, “Exploring Ripple’s New Stablecoin Ripple USD (RLUSD)”. The podcast featured Ripple’s CTO David Schwartz and President Monica Long delving into the stablecoin launch and the XRP Ledger ecosystem. However, tensions arose after a specific modification was made to Monica Long’s statement regarding the engagement of developers on the XRPL.
Community’s Reaction to the Edit
In the original podcast, Long highlighted the growing number of developers involved in the XRPL, but the phrase confirming “thousands of developers building projects” was conspicuously missing in the edited version uploaded to YouTube. This edit did not go unnoticed and drew sharp reactions from the community. Daniel “No” Keller, CTO of Eminence and an XRPL Ambassador, was among the first to voice his displeasure through a tweet questioning Ripple’s motives and expressing disappointment over the company’s perceived lack of transparency.
Growing Rift Between Ripple and XRPL Developers
Keller’s tweet underscored a broader dissatisfaction within the developer community. He pointed out the diminishing morale among developers who feel sidelined by Ripple’s corporate strategies. His comments noted the community’s significant role during challenging times, hinting at a widening gap between Ripple’s corporate objectives and the developer community’s expectations.
Community Speaks Out
Stephen Chip, co-founder of onthechain.io, also criticized Ripple for seemingly neglecting its developer community. He emphasized the importance of delivering on grant funding, suggesting that more developers have faced rejections than approvals. Chip acknowledged the recent launch of the Japan-Korea fund but stressed the need for Ripple to honor its primary commitments to grant support, which had initially attracted many developers to the ecosystem.
Defense and Support for Ripple
Conversely, some community members defended Ripple’s actions, suggesting that the edit might have been made to correct a potential overstatement. A dUNL validator, Vet (@Vet_X0), reasoned that the edit indicated internal diligence at Ripple to maintain accuracy, presuming that knowledgeable individuals corrected the statement. This view represents a segment of the community that believes Ripple’s intentions were to ensure factual correctness rather than mislead.
Conclusion
The recent podcast edit unearthed underlying tensions between Ripple and the XRP Ledger developer community. While some view the edit as a breach of transparency, others defend it as a move towards maintaining accuracy. This incident highlights the need for improved communication and engagement between Ripple and its developer base to foster a collaborative environment moving forward.