Mayukha Vadari, a senior software engineer at RippleX, recommended the withdrawal of the XChainBridge amendment, or XLS-38, on August 27, 2026. The cross-network bridging feature remains in the voting stage among XRPL validators and has never gone live on the mainnet. Removing the amendment would allow developers to eliminate more than 10,000 lines of code from the xrpld software repository.
The primary use case for XLS-38 - connecting XRPL to the EVM sidechain - disappeared following the launch of the XRPL EVM Sidechain in June 2025. That project relies on Axelar as its mainnet bridge, which also takes on the role of connecting the sidechain to other blockchains. Ripple pointed to Axelar, Wormhole, zero-knowledge systems, and various layer-2 designs as interoperability alternatives that now dominate the market.
Maintenance Burden Without Users
Operating a native cross-chain bridge requires strict monitoring protocols. The mechanical design of XLS-38 relies on independent witness servers tasked with monitoring events across connected ledgers. These servers must submit attestations before an asset can be made available and claimed on the destination network.
This verification complexity introduces costly operational security risks, considering cross-chain bridge exploits have caused over $4 billion in losses since 2021. Maintaining tens of thousands of lines of dormant implementation code also forces development teams to conduct reviews, testing, and compatibility adjustments with every xrpld system update.
As of late August, Ripple found little evidence of active projects relying on the native XLS-38 bridge. Not a single production deployment has identified the amendment as an essential component for its operations.
Voting in the Hands of Validators
The decommissioning process began with a pull request marking XChainBridge as obsolete within xrpld. Servers running automatic updates responded by casting votes against activating the amendment.
Ripple has no unilateral control to disable the feature, as the company operates only a single validator vote. Standard XRPL rules dictate that a new amendment can only be activated if it secures over 80 percent support among the 35 trusted validators, or at least 29 affirmative votes for two consecutive weeks.
Final execution now rests on the response from the independent developer community. Ripple remains open to reconsidering its withdrawal recommendation if any organization provides concrete evidence of real-world XLS-38 usage. Without counterarguments in the form of credible active deployments, the bridge code will simply become a retired archive in XRPL’s development history.
Source: crypto.news.
Read also: What Is DeFi (Decentralized Finance)?
Read also: India Issues First $57M Tokenized Bond - Purchase Requires Digital Rupee
Disclaimer: This article is for informational and educational purposes only, not financial advice. Cryptocurrency assets are highly volatile and carry significant risk. Always do your own research (DYOR) and never invest more than you can afford to lose.
