Ripple has asked the XRP Ledger community to retire XLS-38, its long-pending native cross-chain bridge amendment. RippleX engineer David Fuelling published the formal recommendation on August 27, 2026, citing low developer demand and the fact that Axelar already handles the primary use case the bridge was built for. XLS-38 was never activated on mainnet, and Ripple says withdrawing it would cut more than 10,000 lines from the xrpld codebase. For investors, this reads as protocol housekeeping rather than a live-bridge failure.
Why Ripple Wants XLS-38 Retired
XLS-38 was designed to move assets between XRPL mainnet and custom sidechains using a decentralized network of witness servers. Its biggest intended role was bridging XRP to the XRPL EVM Sidechain as a native gas token, a plan that changed in June 2024 when Ripple selected Axelar as the production bridge for XRPL-EVM interoperability, citing its 75-plus validators and experience spanning more than 55 connected blockchains. Ripple’s own validator switched its vote to “No” on XLS-38 at that point, giving the broader community 12 to 15 months to demonstrate real demand for a private-sidechain bridge.
That window has closed without traction. According to Fuelling’s post, only about 4 to 5 of the network’s 35 validators — roughly 11 to 14% — were voting “Yes,” far short of the 80% support required for 14 consecutive days to activate any amendment. Mayukha Vadari, an XLS-38 co-author at RippleX, confirmed on X that the amendment never existed on any production network, noting Axelar has run the live XRPL EVM bridge for more than a year.
The Withdrawal Process and What’s Next
Ripple cannot remove XLS-38 unilaterally, since the company runs only one validator on the network. The retirement follows three stages:
- Ripple opens a pull request marking XChainBridge as obsolete in the xrpld repository
- Validators that upgrade automatically stop voting for the amendment
- Once no active validator supports it, the code is deleted entirely
Ripple says it will revisit the recommendation if any team presents an active build requiring a native XLS-38 bridge, though none has surfaced so far. For existing EVM Sidechain users, nothing changes — Axelar remains the path to and from XRPL mainnet. Meanwhile, Ripple’s engineering focus has shifted toward live institutional features: XRPL 3.3.0 brought privacy and tokenization upgrades, and the team continues advancing a lending protocol and single-asset vault on the ledger.
Conclusion: Housekeeping, Not a Bridge Failure
No mainnet assets are locked in XLS-38, and this is not a live-liquidity event. The more relevant signals for XRP holders are institutional and flow-based: Goldman Sachs returned as the largest XRP ETF holder, and Ripple’s partnership with a Korean bank to replace SWIFT with real-time payments underscores where the company’s strategy is actually concentrated — payments and TradFi infrastructure, not a homemade witness-bridge. Some critics on social media have called the reversal centralizing, since Ripple voted “No” for two years before asking the network to retire the alternative entirely. That’s a fair governance debate, but for holders the practical test is simple: absent a serious builder surfacing a genuine XLS-38 use case, this withdrawal is best read as routine codebase cleanup rather than a signal about XRP’s underlying trajectory.
Sources & Methodology
Primary-source standard: Market-moving facts should link to original data releases, regulator notices, company filings or official project announcements whenever available. Secondary reporting is used for additional context, not as a substitute for original evidence.
Page last reviewed: