Ripple Recommends Withdrawal of XChainBridge Amendment (XLS-38)

Ripple has officially told the XRP Ledger community to withdraw the long-standing XChain Bridge modification (XLS-38). The company says that the Axelar integration now more efficiently addresses its original goal of allowing EVM sidechains and cross-chain transfers. Furthermore, RippleX observed years of development but little major developer interest and continuous initiatives using XChain Bridge. Keeping the sophisticated, unutilized bridge implementation is seen as a risk; therefore, its removal would help the xrpld server to be more efficient by eliminating more than 10,000 lines of code.

The withdrawal procedure is not unilateral; Ripple, running just one validator on the XRPL, cannot compel the change's approval. Rather, the planned procedures call for a pull request to mark XChain Bridge obsolete in the code base. Once validators update to this version, they will automatically vote against its activation. Later releases might then delete the XChain Bridge code and related fixXChain Reward Rounding logic. Developers with live XLS-38 projects still have a chance to show their case before the society decides on the withdrawal.

XChain Bridge is now in the validator voting phase and has not yet turned on the mainnet; no code modifications have yet been put into effect. This ruling supports XRPL's more general goal of creating native upgrades for privacy, identity, and lending capabilities therefore boosting DeFi power without depending on outside bridges or smart-contract levels. Before the amendment is officially removed, developers and community members working on XLS-38-related active projects are asked to share their participation.