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 locking and issuing chains are both up and running.
- The witness servers are up and running.
- Set up a bridge between the two chains.
XChainBridgeamendment in the
rippled.cfgconfiguration file on both chains.
- You have an account on the locking and issuing chain.
Create a claim ID with
XChainCreateClaimID, using your account on the issuing chain.
Retrieve the claim ID from the transaction metadata, or use the
XChainCommittransaction with the claim ID, using your account on the locking chain.
A witness server takes note of the
XChainCommittransaction and submits an
XChainAddClaimAttestationtransaction on the issuing chain, attesting that the
XChainCommittransaction did in fact occur on the locking chain.
XChainAddClaimAttestationsignatures are submitted to reach quorum, the funds are automatically released on the issuing chain to the
OtherChainDestinationspecified by the
(Optional) If the funds aren't automatically released, you can submit an
XChainClaimtransaction with your account on the issuing chain.