ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-12-02 17:45:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

NFToken references: fix some things for consistency

Browse Source
This commit is contained in:
mDuo13
2022-01-07 20:05:01 -08:00
parent be8cb0790a
commit 2791d5de6e
17 changed files with 132 additions and 231 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/concepts/nft-concepts/nftoken.md
View File

@@ -27,7 +27,7 @@ Unlike other objects, `NFToken` has no field to identify the object type or curr
## TokenID
TokenID, optional, string, UINT256
TokenID, optional, string, UInt256
This composite field uniquely identifies a token, and consists of the following sections.

2
content/concepts/nft-concepts/nftokenburn.md
View File

@@ -77,7 +77,7 @@ If this operation succeeds, the corresponding `NFToken` is removed. If this oper
</td>
<td>string
</td>
<td>UINT256
<td>UInt256
</td>
<td>Identifies the <code>NFToken</code> object to be removed by the transaction.
</td>

12
content/concepts/nft-concepts/nftokenmint.md
View File

@@ -73,7 +73,7 @@ In executing, this transaction examines the `MintedTokens` field in the account
</td>
<td><code>string</code>
</td>
<td><code>UINT16</code>
<td><code>UInt16</code>
</td>
<td>Indicates the new transaction type <code>NFTokenMint</code>. The integer value is <code>25</code>.
</td>
@@ -85,7 +85,7 @@ In executing, this transaction examines the `MintedTokens` field in the account
</td>
<td><code>string</code>
</td>
<td><code>ACCOUNT ID</code>
<td><code>AccountID</code>
</td>
<td>Indicates the account that is minting the token. The account MUST <em>either</em>:
<ul>
@@ -104,7 +104,7 @@ In executing, this transaction examines the `MintedTokens` field in the account
</td>
<td><code>string</code>
</td>
<td><code>ACCOUNT ID</code>
<td><code>AccountID</code>
</td>
<td>Indicates the account that issues the token. This value is <em>optional</em> and should only be specified if the account executing the transaction is not the <code>Issuer</code> of the <code>NFToken</code> object. If it is present, the <code>MintAccount</code> field in the <code>AccountRoot</code> of the <code>Issuer</code> field must match the <code>Account</code>. Otherwise, the transaction fails.
</td>
@@ -116,7 +116,7 @@ In executing, this transaction examines the `MintedTokens` field in the account
</td>
<td><code>number</code>
</td>
<td><code>UINT32</code>
<td><code>UInt32</code>
</td>
<td>The taxon associated with the token. The taxon is generally a value chosen by the <code>minter</code> of the token. A given taxon can be used for multiple tokens. This implementation reserves all taxon identifiers greater than or equal to <code>0x80000000</code>; attempts to use mint tokens with such taxons should fail and a fee should be claimed.
</td>
@@ -128,7 +128,7 @@ In executing, this transaction examines the `MintedTokens` field in the account
</td>
<td><code>number</code>
</td>
<td><code>UINT16</code>
<td><code>UInt16</code>
</td>
<td>The value specifies the fee charged by the issuer for secondary sales of the Token, if such sales are allowed. Valid values for this field are between 0 and 9999 inclusive, allowing transfer rates of between 0.00% and 99.99% in increments of 0.01.
<p>
@@ -154,7 +154,7 @@ The field MUST NOT be present if <code>tfTransferable</code> is not set. If it i
</td>
<td><code>number</code>
</td>
<td><code>UINT32</code>
<td><code>UInt32</code>
</td>
<td>Specifies the flags used for the minting transaction. See the mint transaction flags in the following table.
</td>

28
content/concepts/nft-concepts/nftokenoffer.md
View File

@@ -65,7 +65,7 @@ The unique ID (`NFTokenOfferID)` of the `NFTokenOffer` object is the result of t
</td>
<td>string
</td>
<td>UINT16
<td>UInt16
</td>
<td>The type of ledger object (<code>0x0074</code>).
</td>
@@ -89,7 +89,7 @@ The unique ID (`NFTokenOfferID)` of the `NFTokenOffer` object is the result of t
</td>
<td>number
</td>
<td>UINT32
<td>UInt32
</td>
<td>Index of the ledger that contains the transaction that most recently modified this object.
</td>
@@ -101,7 +101,7 @@ The unique ID (`NFTokenOfferID)` of the `NFTokenOffer` object is the result of t
</td>
<td>string
</td>
<td>UINT256
<td>UInt256
</td>
<td><code>TokenID</code> of the <code>NFToken</code> object referenced by this offer.
</td>
@@ -127,7 +127,7 @@ Sell offers that specify assets other than XRP must specify a non-zero amount. S
</td>
<td>number
</td>
<td>UINT32
<td>UInt32
</td>
<td>The time after which the offer is no longer active. The value is the number of seconds since the <a href="https://xrpl.org/basic-data-types.html#specifying-time">Ripple Epoch</a>.
</td>
@@ -151,7 +151,7 @@ Sell offers that specify assets other than XRP must specify a non-zero amount. S
</td>
<td>string
</td>
<td>UINT64
<td>UInt64
</td>
<td>Internal bookkeeping, indicating the page inside the owner directory where this token is being tracked. This field allows the efficient deletion of offers.
</td>
@@ -163,7 +163,7 @@ Sell offers that specify assets other than XRP must specify a non-zero amount. S
</td>
<td>string
</td>
<td>UINT64
<td>UInt64
</td>
<td>Internal bookkeeping, indicating the page inside the token buy or sell offer directory, as appropriate, where this token is being tracked. This field allows the efficient deletion of offers.
</td>
@@ -175,7 +175,7 @@ Sell offers that specify assets other than XRP must specify a non-zero amount. S
</td>
<td>number
</td>
<td>UINT32
<td>UInt32
</td>
<td>A set of flags associated with this object, used to specify various options or settings. Flags are listed in the table below.
</td>
@@ -276,7 +276,7 @@ Each offer costs one incremental reserve.
</td>
<td>string
</td>
<td>UINT16
<td>UInt16
</td>
<td>Indicates the new transaction type <code>NFTokenCreateOffer</code>. The integer identifier is <code>27</code>.
</td>
@@ -346,7 +346,7 @@ The amount must be non-zero, except where this is an offer to sell and the asset
</td>
<td>number
</td>
<td>UINT32
<td>UInt32
</td>
<td>Indicates the time after which the offer will no longer be valid. The value is the number of seconds since the <a href="https://xrpl.org/basic-data-types.html#specifying-time">Ripple Epoch</a>.
</td>
@@ -372,7 +372,7 @@ If succesful, <code>NFTokenCreateOffer</code> transaction results in the creatio
</td>
<td>number
</td>
<td>UINT32
<td>UInt32
</td>
<td>A set of flags that specifies options or controls the behavior of the transaction. The flag is defined in the table below.
</td>
@@ -453,7 +453,7 @@ An `NFTokenCancelOffer` object can have the following required and optional fiel
</td>
<td>string
</td>
<td>UINT16
<td>UInt16
</td>
<td><code>NFTokenCancelOffer</code> transaction type . The integer identifier is <code>28</code>.
</td>
@@ -590,7 +590,7 @@ In brokered mode, the `NFTokenAcceptOffer` transaction fails if:
</td>
<td>string
</td>
<td>UINT16
<td>UInt16
</td>
<td>Transaction type <code>NFTokenAcceptOffer</code>. The sequence number of a previous <code>NFTokenCreateOffer</code> transaction. The integer identifier is <code>29</code>.
</td>
@@ -602,7 +602,7 @@ In brokered mode, the `NFTokenAcceptOffer` transaction fails if:
</td>
<td>string
</td>
<td>UINT256
<td>UInt256
</td>
<td>Identifies the <code>NFTokenOffer</code> that offers to sell the <code>NFToken</code>.
<p>
@@ -616,7 +616,7 @@ In direct mode this field is optional, but you must specify either the <code>Sel
</td>
<td>string
</td>
<td>UINT256
<td>UInt256
</td>
<td>Identifies the <code>NFTokenOffer</code> that offers to buy the <code>NFToken</code>.
<p>

8
content/concepts/nft-concepts/nftokenpage.md
View File

@@ -70,7 +70,7 @@ An `NFTokenPage` object can have the following required and optional fields:
</td>
<td>string
</td>
<td>UINT16
<td>UInt16
</td>
<td>Identifies the type of ledger object. The reserved ledger entry type is <code>0x0050</code>.
</td>
@@ -82,7 +82,7 @@ An `NFTokenPage` object can have the following required and optional fields:
</td>
<td>string
</td>
<td>UINT256
<td>UInt256
</td>
<td>The locator of the previous page, if any. Details about this field and how it should be used are outlined below, after the construction of the <code>NFTokenPageID</code> is explained.
</td>
@@ -94,7 +94,7 @@ An `NFTokenPage` object can have the following required and optional fields:
</td>
<td><code>string</code>
</td>
<td><code>UINT256</code>
<td><code>UInt256</code>
</td>
<td>The locator of the next page, if any. Details about this field and how it should be used are outlined below, after the construction of the <code>NFTokenPageID</code> is explained.
</td>
@@ -118,7 +118,7 @@ An `NFTokenPage` object can have the following required and optional fields:
</td>
<td><code>number</code>
</td>
<td><code>UINT32</code>
<td><code>UInt32</code>
</td>
<td>The sequence of the ledger that contains the transaction that most recently modified this <code>NFTokenPage</code> object.
</td>