CTO Clarifies Ripple’s Commitment to Community Input on XRPL

Last Updated:
CTO Clarifies Ripple's Commitment to Community Input on XRPL
  • Ripple CTO David Schwartz clarified the firm’s recent blog post on programmability on XRPL.
  • Ripple will introduce changes into the XRPL blockchain, sparking concerns in the community.
  • Schwartz said that Ripple will remain transparent in its moves and share the details.

David Schwartz, the chief technology officer at Ripple, took to social media platform X (formerly Twitter) to clarify the introduction of programmability and key changes coming to the XRP Ledger (XRPL).

In the X post, the executive responded to the digital asset community’s mixed reactions to Ripple’s announcement that it would add smart contract functionality to the XRP Ledger and provide “builders, entrepreneurs, and users” with enhanced customizability.

The digital asset community was concerned whether Ripple is solely leading the change in the XRP ecosystem and whether they will have a say. Schwartz said that Ripple has no intentions of unilaterally changing the XRP Ledger and added:

“The blog post is Ripple saying that we see the value in bringing programmability to XRPL Mainnet (in addition to what’s already happening with the EVM Sidechain) and are making this a priority now, and we’re committed to putting out a design proposal for community review.”

With the introduction of native smart contract capabilities on the XRP Ledger (currently in the research phase) and the upcoming debut of the Ethereum Virtual Machine (EVM) sidechain (expected to go live in the next few months), Ripple aims to enhance the programmability of the blockchain network.

According to Schwartz, instead of presenting a “fully baked” proposal to the crypto sector and the XRP community, Ripple has been transparent with its plans. The American fintech firm’s goal is to remain transparent and inform its community and shareholders where it plans to allocate resources and has also outlined its priorities.

Explaining the sudden change in the company’s plans, Schwartz said that Ripple initially believed that the introduction of programmability on the mainnet would significantly alter XRPL. Therefore, it was necessary for the company to create the EVM sidechain. However, after the response from the crypto sector and input from various individuals, Schwartz concluded that “programmability makes sense for Mainnet much earlier.”

Disclaimer: The information presented in this article is for informational and educational purposes only. The article does not constitute financial advice or advice of any kind. Coin Edition is not responsible for any losses incurred as a result of the utilization of content, products, or services mentioned. Readers are advised to exercise caution before taking any action related to the company.

CoinStats ad

Latest News