by Jake ClaverQuick answer: The XRP Ledger’s native cross-chain bridge amendment is not dead. XChainBridge, which implements the XLS-38 cross-chain bridge standard, is enabled on the XRPL Mainnet. Separately, Ripple chose Axelar as the bridge protocol for the newer XRPL EVM sidechain. These are two different pieces of interoperability, not a case of one killing the other.
Updated 07/17/2026. By Jake Claver. Educational content, not investment advice.
Interoperability, the ability to move assets and data between blockchains, has been one of the more contested engineering topics in the XRP Ledger’s development. Headlines sometimes frame it as a fight where a stalled native feature hands the lead to a third party. The verifiable record is more precise, and worth getting right.
What an XLS amendment actually is
Changes to the XRP Ledger go through a formal amendment process: a proposal is coded, tested, and then requires supermajority approval from the network’s validators, held for at least two weeks, before it activates. The XRPL known amendments page lists each amendment and whether it is enabled on Mainnet or still open for voting. That process is deliberately conservative, which is good for stability but means features can sit unactivated if they do not gather enough validator support.
The native bridge amendment is live, not dead
The cross-chain bridge standard, XLS-0038, is marked Final in the XRPL Standards repository. Its on-ledger implementation, the XChainBridge amendment, is listed as enabled on Mainnet by xrpl.org. In plain terms, the standard describes a bridge that connects a locking chain and an issuing chain: assets are locked on one side while a wrapped representation is issued on the other. So the framing that the bridge amendment is “dead” does not match the ledger’s own amendment record.
Where Axelar actually fits
Axelar’s role is a separate development tied to the XRPL EVM sidechain, an EVM-compatible chain where wrapped XRP (eXRP) is the native gas token. According to Ripple, “the XRPL EVM sidechain is set to launch with Axelar as the exclusive bridge to source the native gas token of the sidechain (eXRP),” described on the Ripple insights blog. Axelar itself confirmed it is “the first crosschain connector” for the sidechain, linking it to a large set of other blockchains, in its announcement. So Axelar is not filling a gap left by a failed amendment; it was selected to bridge a specific new EVM sidechain, which is a different piece of the stack from the XRPL Mainnet’s native XChainBridge.
Why the distinction matters
For XRP holders and developers, the practical point is that interoperability on and around the XRP Ledger now comes from more than one mechanism. There is the native XChainBridge primitive on Mainnet, and there is Axelar-based connectivity for the EVM sidechain that reaches many external chains. Conflating them, or declaring one dead to hype the other, gives a misleading picture of what is actually running. Both facts can be true at once.
What to watch instead of speculating
- The live status of any amendment on the XRP Ledger documentation, which is public and updated as amendments activate.
- Whether real transaction volume flows through native bridges versus third-party bridges like Axelar.
- Official posts from Ripple and the XRPL community on sidechain and bridge milestones, rather than social-media declarations.
A live native feature and a growing third-party integration are both facts worth knowing, and neither alone tells the full interoperability story.
Common questions
Is the XRP Ledger bridge amendment dead?
No. The XChainBridge amendment, which implements the XLS-38 cross-chain bridge standard, is listed as enabled on the XRPL Mainnet by xrpl.org, and the XLS-0038 standard is marked Final.
What does the XChainBridge amendment do?
It lets assets move between the XRP Ledger and another chain by locking assets on one side and issuing a wrapped representation on the other, following the XLS-0038 standard.
What is Axelar’s role with XRPL?
Ripple selected Axelar as the bridge protocol for the XRPL EVM sidechain, where wrapped XRP (eXRP) is the native gas token. Axelar connects that sidechain to many other blockchains. It is separate from the native XChainBridge amendment on Mainnet.
How does an XRPL amendment get activated?
A proposal must gain supermajority support from the network’s validators and hold it for at least two weeks before it activates. The process is deliberately conservative to protect network stability.
Where can I check the real status?
Use the XRPL known amendments page for on-ledger status, the XRPL Standards repository for the specification, and official Ripple and Axelar posts for sidechain and bridge news.
This content is educational only. It is not tax, legal, or investment advice. Check primary sources and speak with a qualified professional before making financial decisions.
