Ripple

Ripple Moves to Scrap XRP Ledger’s XChainBridge

By /

Key Insights

  • Ripple sees Axelar as a more established bridge for the XRPL EVM Sidechain.
  • Removing XLS-38 could cut more than 10,000 lines from the xrpld codebase.
  • Developers can still challenge Ripple’s recommendation with active XLS-38 use cases. 

Ripple has urged the XRP Ledger community to withdraw its pending XChainBridge amendment after finding limited demand. The recommendation could remove more than 10,000 lines from XRPL’s core server code.

RippleX senior software engineer Mayukha Vadari announced the recommendation on Aug. 27. XChainBridge, also known as XLS-38, remains inactive and has not reached mainnet activation.

The proposal would create a native framework for moving XRP and issued assets across connected ledgers. However, Ripple now argues that its main public use case already has another solution.

Axelar Changes the Original Bridge Strategy

XLS-38 emerged as a protocol-level approach for connecting XRPL with other networks. Its design relied on independent witness servers that monitor activity across connected ledgers.
Those witnesses would attest to events before assets became available on another network. The design targeted public sidechains, private chains, permissioned networks and experimental environments.

The XRPL EVM Sidechain represented one of its most important potential applications. Ripple and its partners eventually chose Axelar instead after evaluating security, decentralization and operational requirements.

The decision was made in June 2024. Ripple kept XLS-38 open for community consideration but gave developers 12-15 months to prove demand. The XRPL EVM Sidechain launched with Axelar in June 2025.

Axelar operates a validator network supporting cross-chain messaging across numerous blockchain networks. Ripple now considers that integration better suited to the sidechain’s needs. The assessment removes much of the original justification for keeping XLS-38 active.

Limited Adoption Raises Maintenance Concerns

During the review period, Ripple said it monitored developer discussions and projects involving XLS-38. The company found little evidence of meaningful production demand.

That finding changed the economics of maintaining the dormant implementation. Developers must continue testing and reviewing unused code as the wider xrpld software evolves.

Ripple estimates that withdrawing XLS-38 could eventually remove more than 10,000 lines. The related fix XChain Reward Rounding amendment could also leave the codebase.
Now, factors that influence the choice

The EVM Sidechain connection is supported by Axelar already.
There was no noteworthy demand from private-sidechain activity in the vicinity of XLS-38.
When the bridge code is inactive, there will be extra engineering work.

The move doesn’t indicate that XRPL interoperability has come to an end. Ripple has mentioned the alternate solutions like Axelar, Wormhole, zero-knowledge systems and layer-2 designs.
But they have different security and trust assumptions. There have been extensive hacks in the Bridge world as well.

Validators Still Control the Outcome

Ripple cannot remove XChainBridge alone, as it has just one vote on one XRPL validator. Other validators need to be involved in the amendment process.

The changes that would occur while the withdrawal is proposed to start with a change in the software xrpld. XChainBridge would be put in obsolescence by a pull request by a developer.

That software would result in automatic rejection of that amendment by validators running that software. If the number of operators continued to update, then the support for XLS-38 would decrease.

If the bridge is considered obsolete by validators, it might be removed in a later software release. The corresponding reward-rounding code could then be eliminated from the code by the developers. The final date for removal has not yet been determined. The process relies on code review, validator upgrades and community feedback.

Ripple has also invited developers to submit proofs of active XLS-38 projects. In the case of strong use cases, the company might take a second look.

The implications of the Decision for XRPL

This is a sign of a bigger issue that blockchain networks are now grappling with as they move toward greater interoperability infrastructure. There are more bridge options for developers, making the need for overlapping systems less important.

There is minimal impact for XRPL users as no XLS-38 was launched on mainnet. The current EVM sidechain connection over Axelar would still work.

The proposal leaves validators with a dilemma as to whether to use software that would make the amendment redundant. For developers it puts pressure on them to show demand before the implementation no longer exists.

The decision also represents a change from “build-it-for-people-who-may-use-it” to “maintain-it-for-people-who-already-use-it.

Conclusion

The recommendation by Ripple puts the long-standing XChainBridge proposal on a critical juncture. The company no longer believes there is an adequate demand for XLS-38 on XRP Ledger’s live development roadmap.

Axelar has already assumed the main bridging task of EVM Sidechain. In the meantime, Ripple hasn’t seen much evidence developers need XLS-38 for private, specialized networks.

However, the proposal will still go through the XRPL’s decentralised governance process. Ripple has no right to impose the withdrawal, and the developers can provide the evidence before the process moves forward.

The result will therefore rely on the decisions of the validators and the level of demand of the developers. XLS-38 may eventually be completely removed from the XRPL codebase if no major projects come about.

It would be a significant shift in XRPL’s interoperability approach. It would also demonstrate that mature blockchain networks are willing to get rid of excess infrastructure rather than keeping it alive for eternity.

 

Related Posts

Scroll to Top