From 640bb8d8103670a47b87dfbbe7e8337d4356d677 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Wed, 29 Jul 2026 17:09:51 -0700 Subject: [PATCH] Address feedback re: NFT flag renaming --- .../ledger-data/ledger-entry-types/nftokenoffer.md | 2 +- .../protocol/transactions/types/nftokencreateoffer.md | 4 ++-- docs/references/protocol/data-types/nftoken.md | 10 +++++----- .../ledger-data/ledger-entry-types/nftokenoffer.md | 2 +- .../protocol/transactions/types/nftokencreateoffer.md | 4 ++-- 5 files changed, 11 insertions(+), 11 deletions(-) diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md index 65ca530d3f..6a535b3162 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md @@ -34,7 +34,7 @@ labels: | 名前 | JSONの型 | [内部の型][] | 必須？ | 説明 | |:--------------------|:------------|:------------------|:------|:-----------| -| `Amount` | [通貨額][] | AMOUNT | はい | NFTokenに対して見込まれる、または提示される金額です。トークンに`lsfOnlyXRP`フラグが設定されている場合、金額はXRPで指定する必要があります。XRP以外の資産を指定する売却オファーは、0以外の金額を指定する必要があります。XRPを指定する売却オファーは、`無料`にすることができます（つまり、このフィールドは`"0"`とすることができます）。 | +| `Amount` | [通貨額][] | AMOUNT | はい | NFTokenに対して見込まれる、または提示される金額です。トークンに`flagOnlyXRP`フラグが設定されている場合、金額はXRPで指定する必要があります。XRP以外の資産を指定する売却オファーは、0以外の金額を指定する必要があります。XRPを指定する売却オファーは、`無料`にすることができます（つまり、このフィールドは`"0"`とすることができます）。 | | `Destination` | 文字列 | AccountID | いいえ | このオファーの対象となるAccountID。存在する場合、そのアカウントのみがオファーを受け入れることができます。 | | `Expiration` | 数値 | UInt32 | いいえ | オファーが有効でなくなる時刻。値は、リップルエポックからの秒数です。 | | `Flags` | 数値 | UInt32 | はい | このオブジェクトに関連付けられたフラグのセットで、様々なオプションや設定を指定するために使用されます。フラグは、以下の表に示すとおりです。 | diff --git a/@l10n/ja/docs/references/protocol/transactions/types/nftokencreateoffer.md b/@l10n/ja/docs/references/protocol/transactions/types/nftokencreateoffer.md index 38f3c85770..5362e0e2a5 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/nftokencreateoffer.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/nftokencreateoffer.md @@ -58,7 +58,7 @@ NFTokenCreateOfferタイプのトランザクションは、以下のように[` | エラーコード | 説明 | |:---------------------------------|:------------------------------------------| | `temDISABLED` | [NonFungibleTokensV1 Amendment][]は有効ではありません。 | -| `temBAD_AMOUNT` | `Amount`フィールドが有効ではありません。例えば、購入オファーで金額がゼロであったり、金額はトークンであるが`NFToken`で[`lsfOnlyXRP`フラグ](../../data-types/nftoken.md#nftoken-フラグ)が有効になっている場合などです。 | +| `temBAD_AMOUNT` | `Amount`フィールドが有効ではありません。例えば、購入オファーで金額がゼロであったり、金額はトークンであるが`NFToken`で[`flagOnlyXRP`フラグ](../../data-types/nftoken.md#nftoken-フラグ)が有効になっている場合などです。 | | `temBAD_EXPIRATION` | 指定された`Expiration`は無効です（例：`0`）。 | | `tecDIR_FULL` | 送信者がレジャーにすでにあまりにも多くのオブジェクトを所有しているか、またはこのトークンの売買のオファーがあまりにも多く存在しています。 | | `tecEXPIRED` | 指定された`Expiration`の時間は既に経過しています。 | @@ -67,7 +67,7 @@ NFTokenCreateOfferタイプのトランザクションは、以下のように[` | `tecNO_DST` | `Destination`に指定されたアカウントがレジャーに存在しません。 | | `tecNO_ENTRY` | `NFToken`フィールドで指定したアカウントは所有していません。 | | `tecNO_ISSUER` | `Amount`フィールドで指定した発行者が存在しません。 | -| `tecNO_LINE` | `Amount`フィールドはトークンですが、`NFToken`の発行者はそのトークンのトラストラインを持っておらず、`NFToken`は[`lsfTrustLine`フラグ](../../data-types/nftoken.md#nftoken-フラグ)が有効ではありません。 | +| `tecNO_LINE` | `Amount`フィールドはトークンですが、`NFToken`の発行者はそのトークンのトラストラインを持っておらず、`NFToken`は[`flagTrustLine`フラグ](../../data-types/nftoken.md#nftoken-フラグ)が有効ではありません。 | | `tecNO_PERMISSION` | `Destination`アカウントが着信する NFTokenOffer をブロックします。 {% amendment-disclaimer name="DisallowIncoming" /%} | `tecUNFUNDED_OFFER` | 購入オファーの場合、送信者は`Amount`フィールドで指定された通貨を利用可能です。もし`Amount`がXRPである場合、これは準備不足によるものかもしれません。もし`Amount`がトークンである場合、これは[フリーズ](../../../../concepts/tokens/fungible-tokens/freezes.md)されている可能性があります。 | | `tefNFTOKEN_IS_NOT_TRANSFERABLE` | `NFToken`は[`lsfTransferable`フラグ](../../data-types/nftoken.md#nftoken-flags)が無効になっており、このトランザクションでは`NFToken`を発行者に転送したり発行者から転送したりすることはできません。 | diff --git a/docs/references/protocol/data-types/nftoken.md b/docs/references/protocol/data-types/nftoken.md index 613f4f14b5..169230eb68 100644 --- a/docs/references/protocol/data-types/nftoken.md +++ b/docs/references/protocol/data-types/nftoken.md @@ -6,7 +6,7 @@ labels: --- # NFToken -A `NFToken` object represents a single non-fungible token (NFT) in the XRP Ledger. It is not stored on its own, but is contained in a [NFTokenPage entry][] alongside other `NFToken` objects. +An `NFToken` object represents a single [non-fungible token](/docs/concepts/tokens/nfts/index.md) (NFT) in the XRP Ledger. It is not stored on its own, but is contained in an [NFTokenPage entry][] alongside other `NFToken` objects. {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} @@ -55,7 +55,7 @@ Flags are properties or other options associated with the `NFToken` object. ### Example -The example sets three flags: `flagBurnable` (`0x0001`), `flagOnlyXRP` (`0x0002`), `flagTransferable` (`0x0008`). 1+2+8 = 11, or `0x000B` in big endian format. +The example sets three flags: `flagBurnable` (`0x0001`), `flagOnlyXRP` (`0x0002`), `flagTransferable` (`0x0008`). 1+2+8 = 11, or `0x000B` in big-endian format. ![Flags](/docs/img/nftokena.png "Flags") @@ -72,18 +72,18 @@ This value sets the transfer fee to 314, or 0.314%. ### Issuer Identification -The third section of the `NFTokenID` is a big endian representation of the issuer’s public address. +The third section of the `NFTokenID` is a big-endian representation of the issuer’s public address. ![Issuer Address](/docs/img/nftokenc.png "Issuer Address") ### NFTokenTaxon -The fourth section is a `NFTokenTaxon` created by the issuer. +The fourth section is an `NFTokenTaxon` created by the issuer. ![Diagram of `NFTokenTaxon` bits](/docs/img/nftokend.png) -An issuer might issue several `NFToken` objects with the same `NFTokenTaxon`; to ensure that `NFToken` objects are spread across multiple pages, the `NFTokenTaxon` is scrambled using the fifth section, a sequential number, as the seed for a random number generator. The scrambled value is stored with the `NFToken`, but the unscrambled value is the actual `NFTokenTaxon`. +An issuer might issue several NFTs with the same `NFTokenTaxon`; to ensure that `NFToken` objects are spread across multiple pages, the `NFTokenTaxon` is scrambled using the fifth section, a sequential number, as the seed for a random number generator. The scrambled value is stored with the `NFToken`, but the unscrambled value is the actual `NFTokenTaxon`. Notice that the scrambled version of the `NFTokenTaxon` is `0xBC8B858E`, the scrambled version of the `NFTokenTaxon` specified by the issuer. But the _actual_ value of the `NFTokenTaxon` is the unscrambled value. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md b/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md index 38fcfdca78..9f7b5854fa 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md @@ -33,7 +33,7 @@ An `NFTokenOffer` entry represents an offer to buy, sell or transfer an [NFT](.. | Name |JSON Type | [Internal Type][] | Required? | Description | |:--------------------|:---------------------|:------------------|:------------|:-----------| -| `Amount` | [Currency Amount][] | Amount | Yes | Amount expected or offered for the NFT. If the token has the `lsfOnlyXRP` flag set, the amount must be specified in XRP. Sell offers that specify assets other than XRP must specify a non-zero amount. Sell offers that specify XRP can be 'free' (that is, the Amount field can be equal to `"0"`). | +| `Amount` | [Currency Amount][] | Amount | Yes | Amount expected or offered for the NFT. If the token has the `flagOnlyXRP` flag set, the amount must be specified in XRP. Sell offers that specify assets other than XRP must specify a non-zero amount. Sell offers that specify XRP can be 'free' (that is, the Amount field can be equal to `"0"`). | | `Destination` | String - [Address][] | AccountID | No | The account for which this offer is intended. If present, only that account can accept the offer. | | `Expiration` | Number | UInt32 | No | The time after which the offer is no longer active. The value is the number of seconds since the Ripple Epoch. | | `NFTokenID` | String - Hexadecimal | UInt256 | Yes | The `NFTokenID` of the NFT referenced by this offer. | diff --git a/docs/references/protocol/transactions/types/nftokencreateoffer.md b/docs/references/protocol/transactions/types/nftokencreateoffer.md index 3a7da8ee51..857408998e 100644 --- a/docs/references/protocol/transactions/types/nftokencreateoffer.md +++ b/docs/references/protocol/transactions/types/nftokencreateoffer.md @@ -58,7 +58,7 @@ Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} | Error Code | Description | |:---------------------------------|:------------------------------------------| | `temDISABLED` | The [NonFungibleTokensV1 amendment][] is not enabled. | -| `temBAD_AMOUNT` | The `Amount` field is not valid. For example, the amount was zero for a buy offer, or the amount is denominated in fungible tokens but the `NFToken` has the [`lsfOnlyXRP` flag](../../data-types/nftoken.md#nftoken-flags) enabled. | +| `temBAD_AMOUNT` | The `Amount` field is not valid. For example, the amount was zero for a buy offer, or the amount is denominated in fungible tokens but the `NFToken` has the [`flagOnlyXRP` flag](../../data-types/nftoken.md#nftoken-flags) enabled. | | `temBAD_EXPIRATION` | The specified `Expiration` time is invalid (for example, `0`). | | `tecDIR_FULL` | The sender already owns too many objects in the ledger, or there are already too many offers to buy or sell this token.
This error is effectively impossible to receive if {% amendment-disclaimer name="fixDirectoryLimit" compact=true /%} is enabled. | | `tecEXPIRED` | The specified `Expiration` time has already passed. | @@ -67,7 +67,7 @@ Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} | `tecNO_DST` | The account specified in the `Destination` field does not exist in the ledger. | | `tecNO_ENTRY` | The `NFToken` is not owned by the expected account. | | `tecNO_ISSUER` | The issuer specified in the `Amount` field does not exist. | -| `tecNO_LINE` | The `Amount` field is denominated in fungible tokens, but the `NFToken`'s issuer does not have a trust line for those tokens and the `NFToken` does not have the [`lsfTrustLine` flag](../../data-types/nftoken.md#nftoken-flags) enabled. | +| `tecNO_LINE` | The `Amount` field is denominated in fungible tokens, but the `NFToken`'s issuer does not have a trust line for those tokens and the `NFToken` does not have the [`flagTrustLine` flag](../../data-types/nftoken.md#nftoken-flags) enabled. | | `tecNO_PERMISSION` | The `Destination` account blocks incoming NFTokenOffers. {% amendment-disclaimer name="DisallowIncoming" /%} | `tecUNFUNDED_OFFER` | For a buy offer, the sender does have the funds specified in the `Amount` field available. If the `Amount` is XRP, this could be due to the reserve requirement; if the `Amount` is denominated in fungible tokens, this could be because they are [frozen](../../../../concepts/tokens/fungible-tokens/freezes.md). | | `tefNFTOKEN_IS_NOT_TRANSFERABLE` | The `NFToken` has the [`lsfTransferable` flag](../../data-types/nftoken.md#nftoken-flags) disabled and this transaction would not transfer the `NFToken` to or from the issuer. |