Skip to content
Open for votingTier AInteroperability

XChainBridge XLS-38

XLS-38 defines asset bridges between XRPL-based networks. XChainBridge is open for Mainnet voting but is not enabled yet. The latest response reports support from 4 of 35 tracked validators.

Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder

Status
Open for voting
XLS
XLS-38
Enabled
Not enabled

What is the current Mainnet vote?

4 of 35 yes votes; minimum: 29 (current 11%; support >80%)

What does this amendment change?

Why does this amendment exist?

Assets need to be transferable between two XRPL-based ledgers even though each validates its own state independently.

How does the mechanism work?

A bridge connects a locking chain and an issuing chain with separate consensus systems. A transfer commits assets on the source side under the bridge's asset rules. Independent witness servers sign attestations, and the destination releases the corresponding value when the signer quorum is reached. Claim objects ensure a publicly visible attestation can be redeemed only once.

What changes compared with the predecessor?

BeforeAfter
Two XRPL-based ledgers had no shared on-ledger objects for quorum attestations, claims, and coordinated asset releases.Door accounts, bridge objects, and witness attestations support transfers and optional account creation across both ledgers.

Who is this change relevant to?

XRP holders and users

A bridge transfer adds witness, door, and counter-ledger risks. It is not a single atomic transfer within one ledger.

Wallets and app developers

Apps must track both ledgers, ClaimID, commitments, attestations, the quorum, and possible manual claim paths.

Exchanges and issuers

Bridge operators configure door accounts, the SignerList, witnesses, rewards, and asset treatment. IOU bridges cannot use an asset with clawback enabled.

Node operators

An xrpld (formerly rippled) node validates only local bridge objects and attestations. Separate witness servers observe the other ledger.

What limitations and risks remain?

  • A cross-chain transfer consists of multiple transactions on two independent ledgers and is not globally atomic.
  • A colluding witness quorum can steal funds from the door account.
  • A door account can support multiple bridges, but no more than one for a given currency type on that ledger. A bridge's identity cannot be changed later.
  • IOU-to-IOU bridges are incompatible with lsfAllowTrustLineClawback because clawback would break the backing invariant.
  • XChainAccountCreateCommit is intended only for XRP-to-XRP bridges.
  • If cross-chain account creation fails after the commitment, there is no automatic refund. Recovery depends on a manual payment from the witness-controlled door account.
  • The bridge does not give the two ledgers a shared consensus system.

What fee and performance figures does the specification provide?

  • Each attestation is a separate transaction requiring a fee. SignatureReward distributes an incentive to valid witness signers.
Technical details: transactions, fields, codes and invariants

Transactions

  • XChainCreateBridge
  • XChainModifyBridge
  • XChainCreateClaimID
  • XChainCommit
  • XChainAddClaimAttestation
  • XChainClaim
  • XChainAccountCreateCommit
  • XChainAddAccountCreateAttestation
  • SignerListSet

Ledger objects

  • Bridge
  • XChainOwnedClaimID
  • XChainOwnedCreateAccountClaimID
  • SignerList

Fields and flags

  • XChainBridge
  • LockingChainDoor / IssuingChainDoor
  • LockingChainIssue / IssuingChainIssue
  • XChainClaimID
  • XChainClaimAttestations
  • SignatureReward
  • MinAccountCreateAmount
  • OtherChainSource / OtherChainDestination
  • AttestationSignerAccount / AttestationRewardAccount
  • tfClearAccountCreateAmount 0x00010000

Result codes

  • tecDUPLICATE
  • tecNO_PERMISSION

What does a concrete workflow look like?

The user reserves a ClaimID on the destination chain and then commits on the source chain. Once enough witnesses confirm that commitment on the destination chain, the corresponding value is paid automatically or through XChainClaim.

How does this amendment relate to others?

Every direct relationship has a type, an explanation and a primary source.

What happens next for this amendment?

XChainBridge is open for Mainnet voting but is not enabled yet. The latest response reports support from 4 of 35 tracked validators.

Activation requires support strictly above 80 percent for two uninterrupted weeks. A reported raw cutoff is not the minimum yes-vote count: with 35 tracked validators and a cutoff of 28, at least 29 yes votes are required.

Where does it sit within its amendment family?

Cross-Chain Bridges: protocol progression

  1. XChainBridgeOpen for voting · from rippled 2.0.0
  2. fixXChainRewardRoundingOpen for voting · from rippled 2.2.0

Which primary sources support this information?

← All XRPL amendments and XLS specifications