Ripple has recommended withdrawing the XRP Ledger’s XChainBridge amendment, saying the feature is no longer needed because its main purpose is already being handled by Axelar, while developer interest in the proposal has remained limited.
The proposal, known as XLS-38, was originally designed to allow XRP and other assets to move between the XRP Ledger and connected blockchains through a native bridge system. One of its key goals was to support the XRP Ledger’s EVM-compatible sidechain.
However, Ripple later chose Axelar as the bridge solution for the XRPL EVM Sidechain. Since that sidechain is already operating with Axelar, Ripple believes the original need for XChainBridge has largely disappeared.
According to RippleX engineer Mayukha Vadari, keeping the unused feature in the codebase creates extra maintenance work for developers. Ripple estimates that removing XChainBridge could eliminate more than 10,000 lines of code from the XRP Ledger server software, making the system simpler to maintain.
Ripple also noted that it has seen little evidence of active projects planning to use XLS-38. While the feature could still have been useful for private or specialized networks, the company says broader demand has not materialized.
Importantly, Ripple cannot remove the amendment on its own. The XRP Ledger is governed by independent validators, and any decision to withdraw or reject the proposal must go through the network’s normal voting process.
The recommendation does not mean XRP Ledger is moving away from cross-chain connectivity. Ripple pointed to alternatives such as Axelar, Wormhole, zero-knowledge solutions, and layer-2 technologies as other ways to connect XRPL with external networks.
For now, Ripple is asking developers who may still need XLS-38 to come forward with real-world use cases before the community decides whether to officially retire the proposal. If strong demand emerges, the company could reconsider its position before any final removal takes place.
