Headline: Ripple recommends pulling XRPL’s XChainBridge amendment after Axelar fills main use case Ripple is recommending that the XRP Ledger (XRPL) community withdraw the long-pending XChainBridge amendment (XLS-38), saying its primary purpose is already served by Axelar and there’s little developer demand for a native bridge. What happened - On Aug. 27, Mayukha Vadari, senior software engineer at RippleX, announced Ripple’s formal recommendation to withdraw XLS-38. The amendment remains in the XRPL validator voting process and has not activated on mainnet. - Ripple estimates that removing XLS-38 would let developers delete more than 10,000 lines of inactive code from xrpld, the server software that runs the network. No code has been removed yet, and Ripple cannot unilaterally make that change—validator consensus is required. Why Ripple wants to withdraw XLS-38 - XLS-38 was designed as a protocol-level framework to move XRP and issued assets between XRPL and connected networks (public sidechains, private ledgers, permissioned networks, experimental chains). - A key intended use was linking the XRPL mainnet with an EVM-compatible sidechain. Ripple later chose Axelar as the bridge provider for the XRPL EVM Sidechain. - The XRPL EVM Sidechain launched in June 2025 with Axelar as its mainnet bridge. Axelar’s validator network now verifies cross-chain messages between the sidechain, XRPL and other supported chains. - Ripple says Axelar “better addresses” that use case and that it has found little evidence of active projects requiring a native XChainBridge implementation. No public production deployments have identified XLS-38 as essential. Operational and security considerations - Keeping the inactive XLS-38 implementation in xrpld imposes ongoing maintenance: reviews, tests and compatibility updates whenever xrpld changes. Ripple argues that this is a burdensome cost without a corresponding mainnet benefit. - Ripple also highlighted that cross-chain systems come with distinct risks. Bridge exploits have accounted for more than $4 billion in reported losses since 2021, making verification design and operational security key considerations. Process and next steps - The XRPL amendment registry currently lists XChainBridge as pending with a default “no” vote. Ripple controls one validator vote among many independent participants. - An amendment must be supported by over 80% of trusted validators for two continuous weeks to activate. With the current default configuration of 35 validators, at least 29 affirmative votes would be needed to meet that threshold. - Ripple’s recommendation does not instantly withdraw the amendment or force other validators to oppose it. Validators decide independently which amendments to support. - Ripple has proposed a staged approach: submit a pull request marking XChainBridge obsolete in the xrpld codebase. Servers upgrading to that release would automatically vote against activation, and support would drop as validators install the update. Once validators treat the amendment as obsolete, the XChainBridge implementation and related fixXChainRewardRounding code could be removed in a later release. - No deadlines, software version, or final removal date have been announced. Timing will depend on community feedback, code review and validator upgrades. Open door for use cases - Ripple has invited developers or organizations using XLS-38 to present concrete use cases. If a credible active deployment is demonstrated, Ripple says it could reconsider the recommendation before any staged withdrawal begins. Bottom line Ripple’s proposal is aimed at simplifying xrpld and avoiding needless maintenance while relying on existing cross-chain solutions like Axelar. But any formal removal of XLS-38 still requires community buy-in from XRPL’s validator set, leaving the final decision in the hands of the wider ecosystem. Read more AI-generated news on: undefined/news