You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `NFTokenMint` transaction creates a non-fungible token and adds it to the relevant [NFTokenPage object][] of the `NFTokenMinter` as an [NFToken][] object. This transaction is the only opportunity the `NFTokenMinter` has to specify any token fields that are defined as immutable (for example, the `TokenFlags`).
_(Added by the [NonFungibleTokensV1_1 amendment][].)_
14
+
_([NonFungibleTokensV1_1 amendment][]により追加されました)_
15
15
16
16
17
-
## Example {% $frontmatter.seo.title %} JSON
17
+
## {% $frontmatter.seo.title %} JSONの例
18
18
19
19
20
20
```json
@@ -38,44 +38,44 @@ _(Added by the [NonFungibleTokensV1_1 amendment][].)_
38
38
}
39
39
```
40
40
41
-
[Query example transaction. >](/resources/dev-tools/websocket-api-tool?server=wss%3A%2F%2Fs1.ripple.com%2F&req=%7B%22id%22%3A%22example_NFTokenMint%22%2C%22command%22%3A%22tx%22%2C%22transaction%22%3A%22B42C7A0C9C3061463C619999942D0F25E4AE5FB051EA0D7A4EE1A924DB6DFEE8%22%2C%22binary%22%3Afalse%7D)
|`NFTokenTaxon`|Number| UInt32 |An arbitrary _taxon_, or shared identifier, for a series or collection of related NFTs. To mint a series of NFTs, give them all the same taxon.|
48
-
|`Issuer`|String| AccountID |_(Optional)_The issuer of the token, if the sender of the account is issuing it on behalf of another account. This field must be omitted if the account sending the transaction is the issuer of the `NFToken`. If provided, the issuer's [AccountRoot object][] must have the `NFTokenMinter`field set to the sender of this transaction (this transaction's `Account` field).|
49
-
|`TransferFee`|Number| UInt16 |_(Optional)_The value specifies the fee charged by the issuer for secondary sales of the `NFToken`, if such sales are allowed. Valid values for this field are between 0 and 50000 inclusive, allowing transfer rates of between 0.00% and 50.00% in increments of 0.001. If this field is provided, the transaction MUST have the [`tfTransferable` flag](#nftokenmint-flags) enabled.|
50
-
|`URI`|String| Blob |_(Optional)_Up to 256 bytes of arbitrary data. In JSON, this should be encoded as a string of hexadecimal. You can use the [`xrpl.convertStringToHex`](https://js.xrpl.org/modules.html#convertStringToHex) utility to convert a URI to its hexadecimal equivalent. This is intended to be a URI that points to the data or metadata associated with the NFT. The contents could decode to an HTTP or HTTPS URL, an IPFS URI, a magnet link, immediate data encoded as an [RFC 2379 "data" URL](https://datatracker.ietf.org/doc/html/rfc2397), or even an issuer-specific encoding. The URI is NOT checked for validity.|
|`Amount`|[Currency Amount][]| Amount |_(Optional)_ Indicates the amount expected or offered for the corresponding `NFToken`. The amount must be non-zero, except where this is an offer to sell and the asset is XRP; then, it is legal to specify an amount of zero, which means that the current owner of the token is giving it away, gratis, either to anyone at all, or to the account identified by the `Destination` field. |
52
52
|`Expiration`| Number | UInt32 |_(Optional)_ Time after which the offer is no longer active, in [seconds since the Ripple Epoch][]. Results in an error if the `Amount` field is not specified. |
53
53
|`Destination`| String | AccountID |_(Optional)_ If present, indicates that this offer may only be accepted by the specified account. Attempts by other accounts to accept this offer MUST fail. Results in an error if the `Amount` field is not specified. |
54
54
55
-
## NFTokenMint Flags
55
+
## NFTokenMintのフラグ
56
56
57
-
Transactions of the NFTokenMint type support additional values in the [`Flags` field](../common-fields.md#flags-field), as follows:
|`tfBurnable`|`0x00000001`| 1 |Allow the issuer (or an entity authorized by the issuer) to destroy the minted `NFToken`. (The `NFToken`'s owner can _always_ do so.)|
62
-
|`tfOnlyXRP`|`0x00000002`| 2 |The minted `NFToken` can only be bought or sold for XRP. This can be desirable if the token has a transfer fee and the issuer does not want to receive fees in non-XRP currencies.|
63
-
|`tfTrustLine`|`0x00000004`| 4 |**DEPRECATED**Automatically create [trust lines](../../../../concepts/tokens/fungible-tokens/index.md)from the issuer to hold transfer fees received from transferring the minted `NFToken`. The [fixRemoveNFTokenAutoTrustLine amendment][] makes it invalid to set this flag.|
64
-
|`tfTransferable`|`0x00000008`| 8 |The minted `NFToken` can be transferred to others. If this flag is _not_ enabled, the token can still be transferred _from_ or _to_ the issuer, but a transfer to the issuer must be made based on a buy offer from the issuer and not a sell offer from the NFT holder.|
If you need to specify additional information during minting (for example, details identifying a property by referencing a particular [plat](https://en.wikipedia.org/wiki/Plat), a vehicle by specifying a [VIN](https://en.wikipedia.org/wiki/Vehicle_identification_number), or other object-specific descriptions) you can use a [transaction memo](../common-fields.md#memos-field). Memos are a part of the signed transaction and are available from historical archives, but are not stored in the ledger's state data.
If you want to issue an NFT for another account there are two things you must do. Given that *Account A* is your account and *Account B* is the account for which you want to mint a NFToken:
1.Set the `NFTokenMinter` account setting on *Account B* to be *Account A*. (This says that *Account B* trusts *Account A* to create NFTs on their behalf.)
76
-
2.When you mint the NFToken, set the `Issuer` field to Account B.
@@ -100,21 +100,21 @@ If you want to issue an NFT for another account there are two things you must do
100
100
```
101
101
102
102
103
-
This transaction assumes that the issuer, `rNCFjv8Ek5oDrNiMJ3pw6eLLFtMjZLJnf2`, has set the `NFTokenMinter` field in its `AccountRoot` to `rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B`, thereby authorizing that account to mint tokens on its behalf.
Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md):
|`temDISABLED`|The [NonFungibleTokensV1 amendment][] is not enabled.|
112
-
|`temBAD_NFTOKEN_TRANSFER_FEE`|The `TransferFee` is not within the acceptable range.|
113
-
|`temINVALID_FLAG`|The `Flags` value has bits enabled that are not allowed or valid flags. If the [fixRemoveNFTokenAutoTrustLine amendment][] is enabled, the `tfTrustLine` flag causes this error. |
114
-
|`temMALFORMED`|The transaction was not validly specified. For example, the `URI` field is longer than 256 bytes.|
115
-
|`tecNO_ISSUER`|The `Issuer` refers to an account that does not exist in the ledger.|
116
-
|`tecNO_PERMISSION`|The account referenced by the `Issuer` field has not authorized this transaction's sender (using the `NFTokenMinter` setting) to mint on their behalf.|
117
-
|`tecINSUFFICIENT_RESERVE`|The owner would not meet the updated [reserve requirement](../../../../concepts/accounts/reserves.md) after minting the token. Note that new `NFToken`s only increase the owner's reserve if it requires a new [NFTokenPage object][], which can each hold up to 32 NFTs. |
118
-
|`tecMAX_SEQUENCE_REACHED`|The `Issuer`'s `MintedNFTokens` field is already at its maximum. This is only possible if 2<sup>32</sup>-1 `NFToken`s have been minted in total by the issuer or on their behalf.|
0 commit comments