Cross-chain bridges functionality is part of the proposed XLS-38d extension (Not Enabled) to the XRP Ledger protocol. There isn't an official amendment yet. Until there is an amendment, the details documented on these pages are subject to change frequently. [Source]

Please use this form to report bugs, provide feedback, or share network issues you experience.


The XChainCreateClaimID transaction creates a new cross-chain claim ID that is used for a cross-chain transfer. A cross-chain claim ID represents one cross-chain transfer of value.

This transaction is the first step of a cross-chain transfer of value and is submitted on the destination chain, not the source chain.

It also includes the account on the source chain that locks or burns the funds on the source chain.

Example XChainCreateClaimID JSON

  "Account": "rahDmoXrtPdh7sUdrPjini3gcnTVYjbjjw",
  "OtherChainSource": "rMTi57fNy2UkUb4RcdoUeJm7gjxVQvxzUo",
  "TransactionType": "XChainCreateClaimID",
  "SignatureReward": "100",
  "XChainBridge": {
    "LockingChainDoor": "rMAXACCrp3Y8PpswXcg3bKggHX76V3F8M4",
    "LockingChainIssue": {
      "currency": "XRP"
    "IssuingChainDoor": "rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh",
    "IssuingChainIssue": {
      "currency": "XRP"

XChainCreateClaimID Fields

Field JSON Type Internal Type Required? Description
OtherChainSource string ACCOUNT Yes The account that must send the XChainCommit transaction on the source chain.
SignatureReward string ACCOUNT Yes The amount, in XRP, to reward the witness servers for providing signatures. This must match the amount on the Bridge ledger object.
XChainBridge XChainBridge XCHAIN_BRIDGE Yes The bridge to create the claim ID for.

XChainBridge Fields

Field JSON Type Internal Type Required? Description
IssuingChainDoor string ACCOUNT Yes The door account on the issuing chain. For an XRP-XRP bridge, this must be the genesis account (the account that is created when the network is first started, which contains all of the XRP).
IssuingChainIssue Issue ISSUE Yes The asset that is minted and burned on the issuing chain. For an IOU-IOU bridge, the issuer of the asset must be the door account on the issuing chain, to avoid supply issues.
LockingChainDoor string ACCOUNT Yes The door account on the locking chain.
LockingChainIssue Issue ISSUE Yes The asset that is locked and unlocked on the locking chain.


XCHAIN_BRIDGE is a new field type introduced by XLS-38d.

Type Name Type Code Bit Length Length-prefixed? Description
XCHAIN_BRIDGE 25 Variable No A bridge between two blockchains, identified by the door accounts and issued assets on the locking chain and issuing chain. XCHAIN_BRIDGE is serialized in this order: locking chain door, locking chain issue, issuing chain door, issuing chain issue.