Ripple has advised the XRP Ledger community to withdraw the long-running XChainBridge (XLS-38) amendment, which aims to deliver native cross-chain bridging for the network.
Shifting priorities for XRP Ledger
Ripple, a blockchain-based payments company best known for developing solutions centered on the XRP Ledger, stated that the XLS-38 bridging technology is no longer required for its primary use case. The company attributed this to a lack of sufficient developer interest and demand for the amendment’s intended functions.
According to Ripple, the original goal behind XLS-38 was to allow seamless asset transfers between the XRPL mainnet and various custom sidechains, including private, permissioned, and experimental networks. The framework involved using “witness servers” to facilitate these transfers.
The amendment was also envisioned to act as the foundational bridge between the XRP Ledger and the XRPL EVM Sidechain, expanding the ecosystem’s interoperability.
ETH
SOL
BSC
ROBINHOOD
USDT
AAPLAxelar integration replaces XLS-38
Ripple revealed that it has instead chosen the Axelar network as the bridge solution for the EVM Sidechain. Axelar offers interoperability with more than 50 blockchain networks and employs a network of over 75 validators, positioning it as a robust alternative to the natively built XLS-38 approach.
The company made the decision to use Axelar in June 2024, while still allowing the community to vote on XLS-38 at that time. Ripple now maintains that Axelar’s integration effectively addresses, or even improves upon, the use case previously targeted by XLS-38.
Mini dictionary: Axelar, a cross-chain communication network, enables interoperability across multiple blockchain protocols by facilitating secure asset and data transfers between different chains. It is designed to connect decentralized applications and ecosystems, allowing seamless transfers without centralized intermediaries.
| Feature | XLS-38 XChainBridge | Axelar Network |
|---|---|---|
| Integration | Native to XRP Ledger | External interoperability protocol |
| Supported Networks | XRPL + sidechains | 50+ blockchains |
| Validator Count | Dependent on XRPL | 75+ validators |
Community response and next steps
Ripple clarified that it does not have the authority to unilaterally remove XLS-38 from the XRP Ledger. The company runs only one validator on the protocol, so any withdrawal of the amendment must proceed through the network’s established amendment process, which requires broad consensus among validators and community stakeholders.
Despite the recommendation, Ripple indicated it is open to reconsidering its decision if developers can present compelling use cases that demonstrate significant community value.
“The primary use case that motivated XLS-38’s development is fully addressed, and we believe better addressed, by the Axelar integration,” RippleX indicated. In addition, the company noted that deleting the dormant code would remove more than 10,000 lines, reducing complexity and potential security liabilities.
Ripple also called on those still developing around XLS-38 to share real-world applications or demands that could justify retaining the amendment.
Ultimately, Ripple sees Axelar’s integration as fulfilling the objectives that prompted the original XLS-38 proposal, citing both community feedback and ecosystem needs in its reasoning.
