Daily News 19

Tag: XLS-38

  • XRPL Native Bridge Faces Shutdown as Ripple Targets 10,000+ Lines of Dead Code

    XRPL Native Bridge Faces Shutdown as Ripple Targets 10,000+ Lines of Dead Code

    Ripple Recommends Retiring XLS-38 Cross-Chain Bridge Amendment on XRP Ledger

    Ripple has formally requested that the XRP Ledger community retire XLS-38, the long-pending native cross-chain bridge amendment. The recommendation was published on August 27, 2026, by RippleX engineer David Fuelling, signaling a strategic shift in the blockchain’s interoperability roadmap.

    Low Developer Demand Cited as Primary Reason

    According to the formal recommendation, the decision stems from insufficient developer demand for the native bridge functionality. Fuelling noted that the ecosystem has increasingly gravitated toward alternative interoperability solutions, reducing the necessity for a built-in cross-chain bridge at the protocol layer.

    Axelar Integration Reduces Need for Native Bridge

    The recommendation highlights that Axelar, a decentralized cross-chain communication network, has established a strong presence on the XRP Ledger. This external integration provides robust bridging capabilities, making the native XLS-38 amendment largely redundant for current developer needs.

    Community Governance Process Next Steps

    As with all protocol amendments on the XRP Ledger, the retirement of XLS-38 will follow the network’s established governance process. Validators and community members will review the recommendation before any formal action is taken. The proposal does not affect existing XRP Ledger functionality or other pending amendments.

    Strategic Focus Shifts to Core Ledger Enhancements

    By retiring XLS-38, RippleX aims to concentrate development resources on core ledger improvements, including transaction throughput, security enhancements, and support for emerging tokenization use cases. This aligns with the broader strategy of maintaining a lean, high-performance base layer while leveraging specialized third-party protocols for cross-chain functionality.

  • Ripple Moves to Scrap Key XRPL Amendment

    Ripple Moves to Scrap Key XRPL Amendment

    Ripple has recommended that the XRP Ledger community withdraw the long-running XChainBridge amendment, known as XLS-38, which was designed to bring native cross-chain bridging capabilities to the network. According to the company, the technology is no longer required for its primary intended use case and has failed to attract sufficient developer demand.

    Ripple Cannot Unilaterally Remove the Amendment

    Because Ripple controls only a single validator vote on the XRP Ledger, the company cannot remove the feature on its own. The withdrawal must proceed through the network’s standard amendment process, requiring broader validator consensus.

    Original Purpose of XLS-38

    XLS-38 was created to provide a native bridging framework for the XRP Ledger. The proposal would have allowed assets to move between the XRPL mainnet and connected sidechains with the assistance of “witness servers.” The system was designed to support custom sidechains, including private and permissioned networks as well as experimental chains. It was also originally intended to serve as the bridge connecting the XRP Ledger to the XRPL EVM Sidechain.

    Axelar Selected as the Alternative

    Ripple has instead selected the Axelar network to power the XRPL EVM Sidechain. Axelar’s network currently operates with more than 75 validators and supports broad interoperability with over 50 blockchain networks.

    Ripple initially decided to use Axelar for the XRPL EVM Sidechain in June 2024. At the time, the company stated it would continue leaving XLS-38 available for a community vote. However, Ripple now says there is little evidence that such demand exists.

    “The primary use case that motivated XLS-38’s development is fully addressed, and we believe better addressed, by the Axelar integration,” RippleX said.

    Code Maintenance Cited as Liability

    The company also argued that maintaining the dormant implementation has become a liability. Removing XChainBridge would allow developers to eliminate more than 10,000 lines of code from the codebase.

    Decision Remains Reversible

    Ripple indicated that its decision could be reversed. Developers who are actively building around XLS-38 have been asked to present compelling use cases that could convince the company to change its position.