Ripple Reconsiders XLS 38 Strategy on XRP Ledger

You can also read this news on BH NEWS: Ripple Reconsiders XLS 38 Strategy on XRP Ledger

Ripple has recommended withdrawing the XChainBridge, known as XLS 38, from the XRP Ledger network. The company cited that the initially intended major use case for this technology is no longer essential, and the demand from developers has been insufficient.

Why is XLS 38 Being Scrapped?

XLS 38 was originally designed to offer a native interchain bridge framework for the XRP Ledger. It was aimed at facilitating asset transfers between the XRPL mainnet and associated sidechains through servers known as witness servers. However, the anticipated demand for this feature didn’t materialize as expected.

The system was initially targeted toward exclusive sidechains, encompassing both private and permissioned networks and experimental chains. It was initially supposed to serve as the bridge linking the XRP Ledger with the XRPL EVM Sidechain, highlighting its potential role in the blockchain ecosystem.

RippleX emphasizes that the primary use case leading to the development of XLS 38 is fully addressed by the Axelar integration, which offers a more suitable solution.

What’s Behind the Axelar Solution?

Ripple previously announced a partnership with the Axelar network for the XRPL EVM Sidechain. This decision, made in June 2024, intended to retain XLS 38 open for community voting. However, Ripple now sees limited demand from developers for this amendment.

Axelar stands out as a network that ensures interoperability among different blockchains. With over 75 validators and connections surpassing 50 blockchain networks, Axelar provides an extensive cross-chain connectivity solution, preferred over XLS 38 for this purpose.

• Ripple cannot unilaterally remove XChainBridge due to its limited control over XRP Ledger validator votes.
• XChainBridge, left unused, has become a technical burden, according to Ripple.
• Removing XChainBridge allows developers to eliminate more than 10,000 lines of code from the system.

Ripple is leaving some room for potential reconsideration. If developers working on XLS 38 can present substantial use cases, the company may re-evaluate its current stance on the matter.