
Locking and issuing
4 minDifficulty Checked 2026-11-10- A bridge does not swap assets. It locks them on one chain and wraps them on another.
- Each side of a bridge is run through a door account.
- The two chains never talk directly. Witness servers report what happened.
A blockchain cannot reach into another blockchain. XRP lives on the XRP Ledger and nowhere else. To use its value on a second chain, you need a bridge.
A bridge does not trade one asset for another. The XLS-38 spec offers a good picture: a box with an endless supply of wrapped coins.
- Put a real coin into the box. A wrapped coin comes out on the other chain.
- Put a wrapped coin back. A real coin comes out again.
- There is no other way in or out of the box.
The chain where the real asset lives is the locking chain. The chain that gets the wrapped copy is the issuing chain. For XRP, the XRP Ledger would be the locking chain and a sidechain would be the issuing chain.
A sidechain is its own ledger. It has its own validators, its own rules and its own list of trusted validators. Nodes on one chain know nothing about the other.
Each end of the bridge is a special account called a door account. The door on the locking chain holds the locked assets. The door on the issuing chain issues the wrapped ones.
Since the chains cannot see each other, someone has to carry the news. Witness servers watch both doors. When assets are locked on one side, witnesses sign a statement saying so and deliver it to the other side.
This bridge design is part of the protocol itself, not an app. It is not enabled on mainnet. Validators have been able to vote on it since January 2024.
The XChainBridge amendment (XLS-38) adds three ledger entry types and eight transactions.
| Ledger entry | Purpose |
|---|---|
Bridge | One end of a bridge: doors, assets, reward, counters |
XChainOwnedClaimID | One pending transfer and its attestations |
XChainOwnedCreateAccountClaimID | One pending account creation |
A bridge is identified by an XChainBridge object with four fields:
| Field | Meaning |
|---|---|
LockingChainDoor | Door account on the locking chain |
LockingChainIssue | Asset locked and unlocked there |
IssuingChainDoor | Door account on the issuing chain |
IssuingChainIssue | Asset minted and burned there |
Two bridge types exist:
- XRP-XRP. The issuing chain's door must be its genesis account, which holds all of that chain's XRP.
- IOU-IOU. For a token bridge, the issuing-chain door must be the issuer of the wrapped token.
XChainCreateBridge creates the Bridge entry. Each door account sends it on its own chain. It sets SignatureReward, the total paid to witnesses per transfer, and optionally MinAccountCreateAmount. XChainModifyBridge can change only those two values.
A Bridge entry cannot be removed, so a door account cannot be deleted.
For testing, xrpl.org lists a Sidechain-Devnet. Devnet acts as the locking chain and the sidechain as the issuing chain.
Related: XRPL EVM sidechain, Hooks and Xahau.
Live count: Amendments page.
- Cross-Chain BridgesRead 2026-11-10
- XRPL SidechainsRead 2026-11-10
- XLS-38 Cross-Chain BridgeRead 2026-11-10
- XChainCreateBridgeRead 2026-11-10
- Known AmendmentsRead 2026-11-10
- Introducing XRP Ledger version 2.0.0Read 2026-11-10
- Parallel NetworksRead 2026-11-10
- Deleting AccountsRead 2026-11-10
