Ripple XRPL amendment withdrawal: Community vote to retire XChainBridge (XLS-38)
Ripple announced on 27 August 2026 that it is formally recommending the XRP Ledger community approve a withdrawal of the long-standing XChainBridge (XLS-38) amendment. The amendment was intended to enable native cross-chain bridging, but Ripple now relies on Axelar for that functionality. The recommendation, reported by U.Today, marks the first concrete step toward deprecating a feature that has lingered in the codebase for over two years without demonstrable developer demand.
Timeline of the amendment and the Axelar switch
- June 2024 – RippleX announced a partnership with Axelar to provide interoperability for the upcoming XRPL EVM Sidechain, while pledging to keep XLS-38 available for a community vote.
- 2025-2026 – Development on XChainBridge stalled; no sidechain projects publicly adopted the witness-server model required by the amendment.
- July 2026 – Internal RippleX analysis estimated that maintaining the dormant code added roughly 10,000 lines of unused source, increasing maintenance overhead and potential attack vectors.
- 27 Aug 2026 – Ripple publicly recommends withdrawal, citing Axelar’s 75-validator network and support for over 50 blockchains as a superior solution.
The chronology shows a clear shift from an in-house bridging attempt to reliance on an established third-party network. The decision aligns with Ripple’s broader strategy to reduce protocol complexity while leveraging external validators for cross-chain liquidity.
Operational consequences for developers and validators
Codebase simplification
Removing XLS-38 will excise more than 10,000 lines of rarely-executed code. Developers will see a leaner SDK, fewer compile-time dependencies, and a reduced surface for bugs. The simplification also eases audit processes, a point Ripple highlighted as a liability mitigation measure.
Validator dynamics
Ripple controls a single validator vote on the XRPL. Because amendment removal requires an 80 % supermajority of validator support, the community must rally around the proposal. Validators that have invested in the witness-server infrastructure will need to reallocate resources toward Axelar-compatible nodes or other network services.
Liquidity pathways
Axelar already routes assets across 50+ chains, offering immediate liquidity for XRP-based tokens on Ethereum, BSC, and other ecosystems. The withdrawal of XLS-38 therefore should not constrict bridge volume; instead, it consolidates liquidity onto a single, well-audited bridge. Market participants can expect a short-term adjustment period as custodial services update their routing tables, but long-term liquidity depth is likely to improve due to Axelar’s broader market reach.
Regulatory exposure and risk management
Cross-chain bridges face increasing regulatory scrutiny for AML/KYC compliance and systemic risk. By delegating bridging to Axelar, Ripple distances itself from direct bridge governance, potentially lowering its regulatory footprint. The reliance on a third-party network introduces counterparty risk: any sanction or compliance breach affecting Axelar could indirectly impact XRP-based services.
The move also aligns with recent guidance from the U.S. Treasury’s Office of Financial Research, which emphasizes transparent, auditable bridge architectures. Axelar’s public validator set and open-source bridge contracts satisfy many of those transparency criteria, whereas the proprietary XChainBridge design lacked comparable public auditability.
Market reaction and liquidity impact
Following the announcement, XRP traded marginally lower on major exchanges, slipping about 0.8 % in the hour after the news. The dip reflects short-term uncertainty rather than a fundamental valuation shift; analysts note that the bridge’s actual on-chain usage was negligible, so the market perceives the change as a net positive for protocol hygiene.
Liquidity providers on decentralized exchanges that had allocated capital to XLS-38-related pools will need to rebalance. The shift to Axelar may open new arbitrage opportunities as price differentials between XRPL-based assets and their Ethereum equivalents normalize under a single bridge.
Independent analysis corroborates the rationale
A recent report from the Blockchain Research Institute (June 2026) quantified the security benefits of removing dormant code, estimating a 12 % reduction in exploitable attack surface for ledgers that prune unused modules. The report cites Ripple’s XChainBridge as a case study, reinforcing the claim that the withdrawal improves overall network resilience.
What to watch next
- Amendment vote outcome – The XRPL amendment process requires an 80 % supermajority of validator votes. Monitoring the voting period will reveal community consensus and signal whether dissenting developers can revive XLS-38.
- Axelar performance metrics – As XRP traffic migrates, Axelar’s throughput and fee structure will become focal points for traders. Any degradation could prompt a re-evaluation of the bridge strategy.
- Regulatory statements – Watch for comments from the U.S. Securities and Exchange Commission or the European Commission on cross-chain interoperability, as these could affect the legal standing of both Axelar and Ripple’s bridge services.
- Developer activity – Track GitHub commits and SDK releases for the XRPL to see how quickly the codebase is pruned and whether new sidechain tooling emerges around Axelar.
Ripple XRPL amendment withdrawal implications for the ecosystem
Ripple’s withdrawal of XLS-38 demonstrates a maturation trend: the XRPL is moving away from bespoke, internally-maintained extensions toward modular integrations with established cross-chain providers. Ripple leads this shift by shedding dormant code and consolidating bridge liquidity. The action reduces protocol risk, improves compliance posture, and creates a more developer-friendly ledger. Investors can interpret these changes as proactive risk management that supports XRP’s long-term market positioning.
What is the XChainBridge (XLS-38) amendment?
XLS-38 was a proposed XRPL amendment designed to enable native asset transfers between the XRP Ledger and custom sidechains via a network of “witness servers” that would validate cross-chain moves.
Why did Ripple choose Axelar over its own bridge?
Axelar offers a validator set of over 75 nodes and supports interoperability with more than 50 blockchains, providing broader coverage and audited code that Ripple’s internal bridge lacked.
How will the amendment withdrawal affect XRP liquidity?
Liquidity will migrate to Axelar’s bridge, which already routes significant volume. In the short term, DEX pools tied to XLS-38 may need rebalancing, but overall bridge capacity is expected to increase.
Where can I see the impact on XRPL’s codebase?
The removal is projected to delete more than 10,000 lines of dormant code, simplifying the ledger’s core and reducing maintenance overhead.
For a broader view of scaling trends that affect bridge decisions, see the latest layer-2 scaling data.
Related coverage
- Mastercard XRPL Hackathon Signals New Settlement Push
- Bitcoin $80,000 rally breaks record as Treasury buyback expands