XChainOwnedClaimID

Attention

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.

[Source]

An XChainOwnedClaimID object represents one cross-chain transfer of value and includes information of the account on the source chain that locks or burns the funds on the source chain.

The XChainOwnedClaimID object must be acquired on the destination chain before submitting a XChainCommit on the source chain. Its purpose is to prevent transaction replay attacks and is also used as a place to collect attestations from witness servers.

An XChainCreateClaimID transaction is used to create a new XChainOwnedClaimID. The ledger object is destroyed when the funds are successfully claimed on the destination chain.

Example XChainOwnedClaimID JSON

{
  "Account": "rBW1U7J9mEhEdk6dMHEFUjqQ7HW7WpaEMi",
  "Flags": 0,
  "OtherChainSource": "r9oXrvBX5aDoyMGkoYvzazxDhYoWFUjz8p",
  "OwnerNode": "0",
  "PreviousTxnID": "1CFD80E9CF232B8EED62A52857DE97438D12230C06496932A81DEFA6E66070A6",
  "PreviousTxnLgrSeq": 58673,
  "SignatureReward": "100",
  "XChainBridge": {
    "IssuingChainDoor": "rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh",
    "IssuingChainIssue": {
      "currency": "XRP"
    },
    "LockingChainDoor": "rMAXACCrp3Y8PpswXcg3bKggHX76V3F8M4",
    "LockingChainIssue": {
      "currency": "XRP"
    }
  },
  "XChainClaimAttestations": [
    {
      "XChainClaimProofSig": {
        "Amount": "1000000",
        "AttestationRewardAccount": "rfgjrgEJGDxfUY2U8VEDs7BnB1jiH3ofu6",
        "AttestationSignerAccount": "rfsxNxZ6xB1nTPhTMwQajNnkCxWG8B714n",
        "Destination": "rBW1U7J9mEhEdk6dMHEFUjqQ7HW7WpaEMi",
        "PublicKey": "025CA526EF20567A50FEC504589F949E0E3401C13EF76DD5FD1CC2850FA485BD7B",
        "WasLockingChainSend": 1
      }
    },
    {
      "XChainClaimProofSig": {
        "Amount": "1000000",
        "AttestationRewardAccount": "rUUL1tP523M8KimERqVS7sxb1tLLmpndyv",
        "AttestationSignerAccount": "rEg5sHxZVTNwRL3BAdMwJatkmWDzHMmzDF",
        "Destination": "rBW1U7J9mEhEdk6dMHEFUjqQ7HW7WpaEMi",
        "PublicKey": "03D40434A6843638681E2F215310EBC4131AFB12EA85985DA073183B732525F7C9",
        "WasLockingChainSend": 1
      },
    }
  ],
  "XChainClaimID": "b5",
  "LedgerEntryType": "XChainOwnedClaimID",
  "LedgerIndex": "20B136D7BF6D2E3D610E28E3E6BE09F5C8F4F0241BBF6E2D072AE1BACB1388F5"
}

XChainOwnedClaimID Fields

Field	JSON Type	Internal Type	Required?	Description
`Account`	`string`	`ACCOUNT`	Yes	The account that owns this object.
`LedgerIndex`	`string`	`HASH256`	Yes	The ledger index is a hash of a unique prefix for `XChainOwnedClaimID`s, the actual `XChainClaimID` value, and the fields in `XChainBridge`.
`OtherChainSource`	`string`	`ACCOUNT`	Yes	The account that must send the corresponding `XChainCommit` on the source chain. The destination may be specified in the `XChainCommit` transaction, which means that if the `OtherChainSource` isn't specified, another account can try to specify a different destination and steal the funds. This also allows tracking only a single set of signatures, since we know which account will send the `XChainCommit` transaction.
`SignatureReward`	`Currency Amount`	`AMOUNT`	Yes	The total amount to pay the witness servers for their signatures. It must be at least the value of `SignatureReward` in the `Bridge` ledger object.
`XChainBridge`	`XChainBridge`	`XCHAIN_BRIDGE`	Yes	The door accounts and assets of the bridge this object correlates to.
`XChainClaimAttestations`	`array`	`ARRAY`	Yes	Attestations collected from the witness servers. This includes the parameters needed to recreate the message that was signed, including the amount, which chain (locking or issuing), optional destination, and reward account for that signature.
`XChainClaimID`	`string`	`UINT64`	Yes	The unique sequence number for a cross-chain transfer.

XChainClaimAttestations

Field	JSON Type	Internal Type	Required	Description
`XChainClaimProofSig`	`array`	`OBJECT`	Yes	An attestation from one witness server.
`Amount`	`Currency Amount`	`AMOUNT`	Yes	The amount to claim in the `XChainCommit` transaction on the destination chain.
`AttestationRewardAccount`	`string`	`ACCOUNT`	Yes	The account that should receive this signer's share of the `SignatureReward`.
`AttestationSignerAccount`	`string`	`ACCOUNT`	Yes	The account on the door account's signer list that is signing the transaction.
`Destination`	`string`	`ACCOUNT`	No	The destination account for the funds on the destination chain.
`PublicKey`	`string`	`BLOB`	Yes	The public key used to verify the signature.
`WasLockingChainSend`	`number`	`UINT8`	Yes	A boolean representing the chain where the event occurred.

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 Field Type

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.