Definition and scope
Cross-Chain Bridges on the XRP Ledger addresses a distinct part of compliance, identity, and interoperability. Trace locking, claiming, witnesses, and the trust model used to move value between chains.
XRPL includes tools for controlled deposits, issuer compliance, public identity, and cross-network systems. Several features in this category are amendment-dependent or evolving, so every eventual article must verify current Mainnet status and distinguish protocol capability from a particular service's legal obligations. Protocol controls can support a policy but do not establish identity, trustworthiness, regulatory compliance, or legal permission by themselves.
How it works
XChainBridge defines locking and issuing chains, door accounts, claim IDs, witness signatures, attestations, and quorum. Native assets are locked on one chain while corresponding wrapped value is released or issued on the other.
- XChainBridge: verify this field, object, or component against the cited protocol documentation.
- door account: verify this field, object, or component against the cited protocol documentation.
- witness: verify this field, object, or component against the cited protocol documentation.
- claim ID: verify this field, object, or component against the cited protocol documentation.
- attestation: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
On networks where XChainBridge is enabled, a user creates a claim ID, commits value on the locking chain, waits for witness attestations, and claims on the issuing chain after quorum.
For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.
Open the related live demo or evidence lab →Limits, risks, and common confusion
XChainBridge was not enabled on XRPL Mainnet at review time. Wrapped XRP is not native XRP, and bridge safety depends on door accounts, witnesses, quorum, chain finality, and operations.
Protocol controls can support a policy but do not establish identity, trustworthiness, regulatory compliance, or legal permission by themselves.
Current network status
Not enabled on XRPL Mainnet. Official public-server feature responses showed XChainBridge supported but not enabled on Mainnet at review time. A sidechain or bridge has independent validators and witness assumptions.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.