申し訳ありませんが、このページはお使いの言語では提供されていません。

XRP Ledger Dev Portalをさまざまな言語で提供するよう取り組んでいますが、すべてのページがすべての言語で提供されているわけではありません。ご協力いただける場合は、ぜひ貢献をお願いいたします

NFTokenCancelOffer

The XLS-20 standard for NFTs has a preliminary implementation that can be used in test networks, but is not yet available as an amendment to the XRP Ledger protocol. An amendment may be included in a future XRP Ledger release.

The NFTokenCancelOffer transaction can be used to cancel existing token offers created using NFTokenCreateOffer.

Example NFTokenCancelOffer JSON

{
    "TransactionType": "NFTokenCancelOffer",
    "Account": "ra5nK24KXen9AHvsdFTKHSANinZseWnPcX",
    "NFTokenOffers": [
      "9C92E061381C1EF37A8CDE0E8FC35188BFC30B1883825042A64309AC09F4C36D"
    ]
}

Permissions

An existing offer, represented by an NFTokenOffer object, can be cancelled by:

  • The account that originally created the NFTokenOffer.
  • The account in the Destination field of the NFTokenOffer, if one is present.
  • Any account, if the NFTokenOffer specifies an expiration time and the close time of the parent ledger in which the NFTokenCancelOffer is included is greater than the expiration time.

This transaction removes the listed NFTokenOffer object from the ledger, if present, and adjusts the reserve requirements accordingly. It is not an error if the NFTokenOffer cannot be found: if that is the case, the transaction should complete successfully.

NFTokenCancelOffer Fields

In addition to the common fields, a NFTokenCancelOffer transaction uses the following fields:

Field JSON Type Internal Type Description
TransactionType String UInt16 NFTokenCancelOffer transaction type. The integer identifier is 28.
NFTokenOffers Array VECTOR256 An array of IDs of the NFTokenOffer objects to cancel (not the IDs of NFToken objects, but the IDs of the NFTokenOffer objects). Each entry must be a different object ID of an NFTokenOffer object; the transaction is invalid if the array contains duplicate entries.

The transaction can succeed even if one or more of the IDs in the NFTokenOffers field do not refer to objects that currently exist in the ledger. (For example, those token offers might already have been deleted.) The transaction fails with an error if one of the IDs points to an object that does exist, but is not a NFTokenOffer object.

It is important to note that if you inadvertently provide a nft_id rather than a nft_offer_index, you might receive a tesSUCCESS response. The reason is that when passed a properly formatted ID value that is not found, the system assumes that the NFTokenOffer has already been deleted.

The transaction fails with an error if one of the IDs points to an object that does exist, but is not a NFTokenOffer object.