“RippleX Recommends Withdrawal of XLS-38”
Ripple has recommended withdrawing an amendment for XLS-38, a pending operational proposal for constructing a native bridge between XRPL mainnet and custom side chains. Ripple’s XRPL engineer, David Fuelling, published the proposal on August 27, 2026, stating there is no demand for developers to build bridges, and Axelar is currently handling the primary use case for XLS-38. XLS-38 was never activated on the XRPL mainnet, which means proposing withdrawal would not fail with a live bridge and would not impact assets in the protocol.
It is possible withdrawing XLS-38 could simplify XRPL’s technology. Ripple estimates that after withdrawal, almost 10,000 lines of superfluous code would be removed from the xrpld codebase. Removing unused code reduces the length of time a bridge needs to be supported, and allows developers to shift their focus to supporting tools which are demanded by the rest of the network.
Why Ripple Is Recommending the Withdrawal of XLS-38
XLS-38 was intended for moving assets across the XRPL mainnet and sidechains through a decentralized system of witness servers. It was also intended as a bridge to move XRP and facilitate its use as a native XRPL EVM Sidechain gas token.
In June 2024, Ripple changed its interoperability strategy by providing Axelar with the production bridge for XRPL–EVM interoperability. With Axelar already having developed a validator network and having broader experience with cross-chain connectivity, the case for a native bridge was greatly diminished.
As it stands, voting data for XLS-38 shows extremely low community interest. At most, around 4-5 of the 35 UNL validators, or 11-14% respectively, showed support for XLS-38 by voting. This is of little consequence for XRP Ledger as it requires a minimum of 80% of validators supporting an amendment for 14 continuous days to be activated.
The amendment will, therefore, remain inactive, per RippleX co-author Mayukha Vadari, and was ‘never’ deployed on a production network.
How the XLS-38 Withdrawal Process Could Work
Ripple will not remove the amendment, but a proposed removal process starts with a pull request to obsolete XChainBridge in the xrpld repository. With this software, validators would stop voting for the amendment.
Once there are no active validators supporting XLS-38, the code for the amendment could be removed. Ripple is also open to reconsidering the proposal if developers come with a new project that displays a need for the native bridge.
What XLS-38’s Retirement Means for XRP Investors
Most XRP investors treat XLS-38’s possible retirement as a first-tier maintenance event for its protocol as opposed to a first tier market event or a liquidity event. No mainnet assets are locked inside the bridge since it was never activated.
The most important events for XRP holders could be the increase in institutional ownership of XRP, incorporation of XRP into ETFs, tokenization, real-world payments, and lending. Ripple’s engineering work or efforts have increasingly been on the live network to complete various features such as adding tokenization, improvements in privacy, and new single-asset vaults.
Some community members see Ripple’s opposition to XLS-38 as a governance debate, but the real question is whether developers need the technology. If there are no significant use cases, removing over 10,000 lines of dead code could be considered a routine protocol cleanup, and it would not be considered negative from an XRP or XRPL ecosystem standpoint.
