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.
No Comments