diff --git a/content/references/protocol-reference/transactions/transaction-types/nftokenacceptoffer.md b/content/references/protocol-reference/transactions/transaction-types/nftokenacceptoffer.md index f1c93a0e85..db9c4d609f 100644 --- a/content/references/protocol-reference/transactions/transaction-types/nftokenacceptoffer.md +++ b/content/references/protocol-reference/transactions/transaction-types/nftokenacceptoffer.md @@ -17,9 +17,9 @@ The `NFTokenAcceptOffer` transaction is used to accept offers to `buy` or `sell` ## Brokered vs. Direct Mode -The mode in which the transaction operates depends on the presence of the `SellOffer` and `BuyOffer` fields of the transaction: +The mode in which the transaction operates depends on the presence of the `NFTokenSellOffer` and `NFTokenBuyOffer` fields of the transaction: -| `SellOffer` | `BuyOffer` | Mode | +| `NFTokenSellOffer` | `NFTokenBuyOffer` | Mode | |:------------|:-----------|:---------| | ✔️ | ✔️ | Brokered | | ✔️ | X | Direct | @@ -68,17 +68,17 @@ In brokered mode, the `NFTokenAcceptOffer` transaction fails if: | Field | JSON Type | [Internal Type][] | Description | |:----------------|:-----------------|:------------------|:--------------------| | `TransactionType` | String | UInt16 | Transaction type `NFTokenAcceptOffer`. The integer identifier is 29. | -| `SellOffer` | String | Hash256 | _(Optional)_ Identifies the `NFTokenOffer` that offers to sell the `NFToken`. | -| `BuyOffer` | String | Hash256 | _(Optional)_ Identifies the `NFTokenOffer` that offers to buy the `NFToken`. | -| `BrokerFee` | [Currency Amount][] | Amount | _(Optional)_ This field is only valid in brokered mode, and specifies the amount that the broker keeps as part of their fee for bringing the two offers together; the remaining amount is sent to the seller of the NFToken being bought. If specified, the fee must be such that, prior to accounting for the transfer fee charged by the issuer, the amount that the seller would receive is at least as much as the amount indicated in the sell offer. | +| `NFTokenSellOffer` | String | Hash256 | _(Optional)_ Identifies the `NFTokenOffer` that offers to sell the `NFToken`. | +| `NFTokenBuyOffer` | String | Hash256 | _(Optional)_ Identifies the `NFTokenOffer` that offers to buy the `NFToken`. | +| `NFTokenBrokerFee` | [Currency Amount][] | Amount | _(Optional)_ This field is only valid in brokered mode, and specifies the amount that the broker keeps as part of their fee for bringing the two offers together; the remaining amount is sent to the seller of the NFToken being bought. If specified, the fee must be such that, prior to accounting for the transfer fee charged by the issuer, the amount that the seller would receive is at least as much as the amount indicated in the sell offer. | -In direct mode, you must specify **either** the `SellOffer` or the `BuyOffer`. In brokered mode, you must specify **both** the `SellOffer` and the `BuyOffer`. +In direct mode, you must specify **either** the `NFTokenSellOffer` or the `NFTokenBuyOffer`. In brokered mode, you must specify **both** the `NFTokenSellOffer` and the `NFTokenBuyOffer`. -This functionality is intended to allow the `owner` of an `NFToken` to offer their token for sale to a third party broker, who may then attempt to sell the `NFToken` on for a larger amount, without the broker having to own the `NFToken` or custody funds. +This functionality is intended to allow the `owner` of a `NFToken` to offer their token for sale to a third party broker, who may then attempt to sell the `NFToken` on for a larger amount, without the broker having to own the `NFToken` or custody funds. If both offers are for the same asset, it is possible that the order in which funds are transferred might cause a transaction that would succeed to fail due to an apparent lack of funds. To ensure deterministic transaction execution and maximize the chances of successful execution, the account attempting to buy the `NFToken` is debited first. Funds due to the broker are credited _before_ crediting the seller. -In brokered mode, The offers referenced by `BuyOffer` and `SellOffer` must both specify the same `TokenID`; that is, both must be for the same `NFToken`. +In brokered mode, The offers referenced by `NFTokenBuyOffer` and `NFTokenSellOffer` must both specify the same `NFTokenID`; that is, both must be for the same `NFToken`. diff --git a/content/references/protocol-reference/transactions/transaction-types/nftokenburn.md b/content/references/protocol-reference/transactions/transaction-types/nftokenburn.md index ac77f2c69b..2190b28ec9 100644 --- a/content/references/protocol-reference/transactions/transaction-types/nftokenburn.md +++ b/content/references/protocol-reference/transactions/transaction-types/nftokenburn.md @@ -22,7 +22,7 @@ If this operation succeeds, the corresponding `NFToken` is removed. If this oper "TransactionType": "NFTokenBurn", "Account": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B", "Fee": 10, - "TokenID": "000B013A95F14B0044F78A264E41713C64B5F89242540EE208C3098E00000D65" + "NFTokenID": "000B013A95F14B0044F78A264E41713C64B5F89242540EE208C3098E00000D65" } ``` @@ -62,11 +62,11 @@ If this operation succeeds, the corresponding `NFToken` is removed. If this oper AccountID - The AccountID that submitted this transaction. The account must be either the present owner of the token or, if the lsfBurnable flag is set in the NFToken, the issuer account or an account authorized by the issuer, (that is, the MintAccount). + The AccountID that submitted this transaction. The account must be either the present owner of the token or, if the lsfBurnable flag is set in the NFToken, the issuer account or an account authorized by the issuer, (that is, the NFTokenMinter). - TokenID + NFTokenID Yes @@ -96,7 +96,7 @@ If this operation succeeds, the corresponding `NFToken` is removed. If this oper ## Account Root Enhancements -### MintAccount +### NFTokenMinter Issuers might want to issue NFTs from their well known account, while at the same time wanting to delegate the issuance of such NFTs to a mint or other third party. @@ -116,7 +116,7 @@ Issuers might want to issue NFTs from their well known account, while at the sam - MintAccount + NFTokenMinter @@ -124,26 +124,26 @@ Issuers might want to issue NFTs from their well known account, while at the sam AccountID - The MintAccount field, if set, specifies an alternate account which is allowed to execute the NFTokenMint and NFTokenBurn operations on behalf of the account. + The NFTokenMinter field, if set, specifies an alternate account that is allowed to execute the NFTokenMint and NFTokenBurn operations on behalf of the account. -The `SetAccount` transaction allows the `MintAccount` field to be set or cleared. +The `SetAccount` transaction allows the `NFTokenMinter` field to be set or cleared. -### MintedTokens +### MintedNFTokens -The `MintedTokens` field is used to form the `TokenID` of a new object, to ensure the uniqueness of `NFToken` objects. If this field is not present, the value is 0. +The `MintedNFTokens` field is used to form the `NFTokenID` of a new object, to ensure the uniqueness of `NFToken` objects. If this field is not present, the value is 0. -### BurnedTokens +### BurnedNFTokens -The `BurnedTokens` field provides a convenient way to determine how many `NFToken` objects issued by an account are still active (that is, not burned). If this field is not present the value 0 is assumed. The field is decremented whenever a token issued by this account is burned. +The `BurnedNFTokens` field provides a convenient way to determine how many `NFToken` objects issued by an account are still active (that is, not burned). If this field is not present the value 0 is assumed. The field is decremented whenever a token issued by this account is burned. -An account for which the difference the number of minted and burned tokens, as stored in the `MintedTokens` and `BurnedTokens` fields respectively, is non-zero cannot be deleted. +An account for which the difference in the number of minted and burned tokens, as stored in the `MintedNFTokens` and `BurnedNFTokens` fields respectively, is non-zero cannot be deleted. diff --git a/content/references/protocol-reference/transactions/transaction-types/nftokencanceloffer.md b/content/references/protocol-reference/transactions/transaction-types/nftokencanceloffer.md index 6b875ee52a..ae79215039 100644 --- a/content/references/protocol-reference/transactions/transaction-types/nftokencanceloffer.md +++ b/content/references/protocol-reference/transactions/transaction-types/nftokencanceloffer.md @@ -17,7 +17,7 @@ The `NFTokenCancelOffer` transaction can be used to cancel existing token offers { "TransactionType": "NFTokenCancelOffer", "Account": "ra5nK24KXen9AHvsdFTKHSANinZseWnPcX", - "TokenOffers": [ + "NFTokenOffers": [ "9C92E061381C1EF37A8CDE0E8FC35188BFC30B1883825042A64309AC09F4C36D" ] } @@ -29,7 +29,6 @@ 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. -* The issuer of the token identified by the `TokenUID` field in the `NFTokenOffer` object, if the token has the `lsfIssuerCanCancelOffers` flag set. * 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. @@ -39,9 +38,9 @@ This transaction removes the listed `NFTokenOffer` object from the ledger, if pr | Field | JSON Type | [Internal Type][] | Description | |:------------------|:----------|:------------------|:-------------------------| | `TransactionType` | String | UInt16 | NFTokenCancelOffer transaction type. The integer identifier is 28. | -| `TokenOffers` | 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](ledger-object-ids.html) of an [NFTokenOffer](nftokenoffer.html) object; the transaction is invalid if the array contains duplicate entries. | +| `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](ledger-object-ids.html) of an [NFTokenOffer](nftokenoffer.html) 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 `TokenOffers` field do not refer to objects that currently exist in the ledger. (For example, those token offers might already have been taken.) The transaction fails with an error if one of the IDs points to an object that does exist, but is not a [NFTokenOffer](nftokenoffer.html) object. +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 taken.) The transaction fails with an error if one of the IDs points to an object that does exist, but is not a [NFTokenOffer](nftokenoffer.html) object. diff --git a/content/references/protocol-reference/transactions/transaction-types/nftokencreateoffer.md b/content/references/protocol-reference/transactions/transaction-types/nftokencreateoffer.md index 3e369cf633..3b9a892128 100644 --- a/content/references/protocol-reference/transactions/transaction-types/nftokencreateoffer.md +++ b/content/references/protocol-reference/transactions/transaction-types/nftokencreateoffer.md @@ -19,7 +19,7 @@ If successful, the transaction creates a [NFTokenOffer object][]. Each offer cou { "TransactionType": "NFTokenCreateOffer", "Account": "rs8jBmmfpwgmrSPgwMsh7CvKRmRt1JTVSX", - "TokenID": "000100001E962F495F07A990F4ED55ACCFEEF365DBAA76B6A048C0A200000007", + "NFTokenID": "000100001E962F495F07A990F4ED55ACCFEEF365DBAA76B6A048C0A200000007", "Amount": "1000000", "Flags": 1 } @@ -31,7 +31,7 @@ If successful, the transaction creates a [NFTokenOffer object][]. Each offer cou | Field | JSON Type | [Internal Type][] | Description | |:--------------|:--------------------|:------------------|:-------------------| | `Owner` | String | AccountID | _(Optional)_ Who owns the corresponding `NFToken`. If the offer is to buy a token, this field must be present and it must be different than the `Account` field (since an offer to buy a token one already holds is meaningless). If the offer is to sell a token, this field must not be present, as the owner is, implicitly, the same as the `Account` (since an offer to sell a token one doesn't already hold is meaningless). | -| `TokenID` | String | Hash256 | Identifies the `NFToken` object that the offer references. | +| `NFTokenID` | String | Hash256 | Identifies the `NFToken` object that the offer references. | | `Amount` | [Currency Amount][] | Amount | 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. | | `Expiration` | Number | UInt32 | _(Optional)_ Indicates the time after which the offer will no longer be valid. The value is the number of [seconds since the Ripple Epoch][]. | | `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. | diff --git a/content/references/protocol-reference/transactions/transaction-types/nftokenmint.md b/content/references/protocol-reference/transactions/transaction-types/nftokenmint.md index 843b457d4e..6e3c8eee72 100644 --- a/content/references/protocol-reference/transactions/transaction-types/nftokenmint.md +++ b/content/references/protocol-reference/transactions/transaction-types/nftokenmint.md @@ -10,9 +10,9 @@ status: not_enabled [[Source]](https://github.com/ripple/rippled/blob/xls20/src/ripple/app/tx/impl/NFTokenMint.cpp) {% include '_snippets/nfts-disclaimer.md' %} -The `NFTokenMint` transaction creates an non-fungible token and adds it to the relevant [NFTokenPage object][] of the `Minter` as an [NFToken][] object. A required parameter to this transaction is the `Token` field specifying the actual token. This transaction is the only opportunity the `Minter` has to specify any token fields that are defined as immutable (for example, the `TokenFlags`). +The `NFTokenMint` transaction creates a NFToken and adds it to the relevant [NFTokenPage object][] of the `NFTokenMinter` as a [NFToken][] object. A required parameter to this transaction is the `Token` field specifying the actual token. This transaction is the only opportunity the `NFTokenMinter` has to specify any token fields that are defined as immutable (for example, the `Flags`). -If the transaction is successful, the newly minted token is owned by the account (the `minter` account) that executed the transaction. If needed, the server creates a new `NFTokenPage` for the account and applies a reserve charge. +If the transaction is successful, the newly minted token is owned by the account (the `minter` account) that executed the transaction. If needed, the server creates a new `NFTokenPage` for the account and applies a reserve charge. ## Example {{currentpage.name}} JSON @@ -24,7 +24,7 @@ If the transaction is successful, the newly minted token is owned by the account "Account": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B", "Issuer": "rNCFjv8Ek5oDrNiMJ3pw6eLLFtMjZLJnf2", "TransferFee": 314, - "TokenTaxon": 0, + "NFTokenTaxon": 0, "Flags": 2147483659, "Fee": 10, "URI": "697066733a2f2f62616679626569676479727a74357366703775646d37687537367568377932366e6634646675796c71616266336f636c67747179353566627a6469", @@ -41,7 +41,7 @@ If the transaction is successful, the newly minted token is owned by the account ``` -This transaction assumes that the issuer, `rNCFjv8Ek5oDrNiMJ3pw6eLLFtMjZLJnf2`, has set the `Minter` field in its `AccountRoot` to `rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B`, thereby authorizing that account to mint tokens on its behalf. +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. @@ -49,10 +49,10 @@ This transaction assumes that the issuer, `rNCFjv8Ek5oDrNiMJ3pw6eLLFtMjZLJnf2`, | Field | JSON Type | [Internal Type][] | Description | |:--------------|:--------------------|:------------------|:-------------------| -| `TokenTaxon` | Number | UInt32 | The taxon associated with the token. The taxon is generally a value chosen by the minter of the token. A given taxon can be used for multiple tokens. Taxon identifiers greater than `0xFFFF'FFFF` are disallowed. | -| `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 `Minter` field set to sender of this transaction (this transaction's `Account` field). | -| `TransferFee` | Number | UInt16 | _(Optional)_ 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. If this field is provided, the transaction MUST have the [`tfTransferable` flag](#nftokenmint-flags) enabled. | -| `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 [RFC2379 "data" URL](https://datatracker.ietf.org/doc/html/rfc2397), or even an issuer-specific encoding. The URI is NOT checked for validity. +| `NFTokenTaxon` | Number | UInt32 | The taxon associated with the token. The taxon is generally a value chosen by the minter of the token. A given taxon can be used for multiple tokens. Taxon identifiers greater than `0xFFFF'FFFF` are disallowed. | +| `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). | +| `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 9999 inclusive, allowing transfer rates of between 0.00% and 99.99% in increments of 0.01. If this field is provided, the transaction MUST have the [`tfTransferable` flag](#nftokenmint-flags) enabled. | +| `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 NFToken. The contents could decode to an HTTP or HTTPS URL, an IPFS URI, a magnet link, immediate data encoded as an [RFC2379 "data" URL](https://datatracker.ietf.org/doc/html/rfc2397), or even an issuer-specific encoding. The URI is NOT checked for validity. ## NFTokenMint Flags @@ -62,7 +62,7 @@ Transactions of the NFTokenMint type support additional values in the [`Flags` f | Flag Name | Hex Value | Decimal Value | Description | |:--------------|:-------------|:--------------|:------------------------------| | `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.) | -| `tfOnlyXRP` | `0x00000002` | 2 | The minted `NFToken` can only be bought or sold for XRP. This may be desirable if the token has a transfer fee and the issuer does not want to receive fees in non-XRP currencies. | +| `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. | | `tfTrustLine` | `0x00000004` | 4 | Automatically create [trust lines](trust-lines-and-issuing.html) from the issuer to hold transfer fees received from transferring the minted `NFToken`. | | `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. | @@ -73,12 +73,12 @@ If you need to specify additional information during minting (for example, detai ## Error Cases -- If the `TransferFee` field is not within the acceptable range (0 to 9999 inclusive) the transaction fails with `temBAD_TRANSFER_RATE`. +- If the `TransferFee` field is not within the acceptable range (0 to 9999 inclusive) the transaction fails with `temBAD_NFTOKEN_TRANSFER_FEE`. - If the `URI` field is longer than 256 bytes, the transaction fails with `temMALFORMED`. - If the `Issuer` field refers to an account that does not exist, the transaction fails with `tecNO_ISSUER`. -- If account referenced by the `Issuer` field has not authorized this transaction's sender (using the `Minter` setting) to mint `NFToken`s on their behalf, the transaction fails with `tecNO_PERMISSION`. -- If the owner would not meet the updated [reserve requirement](reserves.html) after minting the token, the transaction fails with `tecINSUFFICIENT_RESERVE`. 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. -- If the `Issuer`'s `MintedTokens` field maxes out, the transaction fails with `tecMAX_SEQUENCE_REACHED`. This is only possible if 232-1 `NFToken`s have been minted in total by the issuer or on their behalf. +- If account referenced by the `Issuer` field has not authorized this transaction's sender (using the `NFTokenMinter` setting) to mint `NFToken`s on their behalf, the transaction fails with `tecNO_PERMISSION`. +- If the owner would not meet the updated [reserve requirement](reserves.html) after minting the token, the transaction fails with `tecINSUFFICIENT_RESERVE`. 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 NFTokens. +- If the `Issuer`'s `MintedNFTokens` field maxes out, the transaction fails with `tecMAX_SEQUENCE_REACHED`. This is only possible if 232-1 `NFToken`s have been minted in total by the issuer or on their behalf. {% include '_snippets/rippled-api-links.md' %} diff --git a/content/tutorials/use-tokens/nftoken-tester-tutorial.md b/content/tutorials/use-tokens/nftoken-tester-tutorial.md index 526b284804..603d505a4a 100644 --- a/content/tutorials/use-tokens/nftoken-tester-tutorial.md +++ b/content/tutorials/use-tokens/nftoken-tester-tutorial.md @@ -19,7 +19,7 @@ This example builds a JavaScript test harness where you can create NFTokens and To mint a `NFToken`, you need to generate Account and Secret credentials on the NFT-Devnet (`wss://xls20-sandbox.rippletest.net:51233`). Go to the [Test XRP Faucet](xrp-testnet-faucet.html) and click **Generate NFT-Devnet credentials**. You can also obtain a second set of account credentials to try creating and accepting buy and sell offers. -You will need a URL to the token data you want to turn into a `NFToken`. You can use your own object or this example IPFS address for testing. +You need a URL to the token data you want to turn into a `NFToken`. You can use your own object or this example IPFS address for testing. ``` @@ -84,7 +84,7 @@ async function mintToken() { -2. Create a `NFTokenMint` transaction using your account address and the `URI` to your token data. Note that you must convert the token `URI` to a hexadecimal value for this transaction. The `TokenTaxon` is a required field, but if you are not using the value as a custom indexing field, you can set it to 0. +2. Create a `NFTokenMint` transaction using your account address and the `URI` to your token data. Note that you must convert the token `URI` to a hexadecimal value for this transaction. The `NFTokenTaxon` is a required field, but if you are not using the value as a custom indexing field, you can set it to 0. ```js @@ -93,7 +93,7 @@ async function mintToken() { Account: wallet.classicAddress, URI: xrpl.convertStringToHex(tokenUrl.value), Flags: parseInt(flags.value), - TokenTaxon: 0 + NFTokenTaxon: 0 } ``` @@ -283,7 +283,7 @@ async function burnToken() { const transactionBlob = { "TransactionType": "NFTokenBurn", "Account": wallet.classicAddress, - "TokenID": tokenId.value + "NFTokenID": nftokenId.value } ``` @@ -348,7 +348,7 @@ To create an offer to sell a `NFToken`: 1. Enter your **Account** and **Secret** in the appropriate fields. -2. Enter the **Token ID** of the NFToken you want to sell. +2. Enter the **NFToken ID** of the NFToken you want to sell. 3. Set the **Flags** value to 1. 4. Enter the **Amount**, the sale price in drops (millionths of an xrp). For example, if you enter 1000000, the sale price is 1 xrp. 5. Click **Create Sell Offer**. @@ -395,7 +395,7 @@ async function createSellOffer() { const transactionBlob = { "TransactionType": "NFTokenCreateOffer", "Account": wallet.classicAddress, - "TokenID": tokenId.value, + "NFTokenID": nftokenId.value, "Amount": amount.value, "Flags": parseInt(flags.value) } @@ -422,7 +422,7 @@ async function createSellOffer() { try { nftSellOffers = await client.request({ method: "nft_sell_offers", - tokenid: tokenId.value + nft_id: nftokenId.value }) } catch (err) { console.log("No sell offers.") @@ -433,7 +433,7 @@ async function createSellOffer() { try { nftBuyOffers = await client.request({ method: "nft_buy_offers", - tokenid: tokenId.value }) + nft_id: nftokenId.value }) } catch (err) { console.log("No buy offers.") } @@ -477,7 +477,7 @@ To create an offer to buy a `NFToken`: 1. Enter your **Account** and **Secret** in the appropriate fields. 2. Set the **Flags** value to `0`. -3. Enter the **Token ID** of the `NFToken` you want to purchase. +3. Enter the **NFToken ID** of the `NFToken` you want to purchase. 4. Enter your proposed purchase **Amount** in drops (millionths of an xrp). 5. Enter the **Owner** account address. 6. Click **Create Buy Offer**. @@ -487,7 +487,7 @@ The `createBuyOffer()` function steps are: -1. Connect to the devnet server. +1. Connect to the nft-devnet server. 2. Prepare a transaction blob. 3. Submit the transaction and wait for the results. 4. Request lists of current Sell Offers and Buy Offers. @@ -504,7 +504,7 @@ The `createBuyOffer()` function steps are: -1. Connect to the devnet server. +1. Connect to the nft-devnet server. ```js @@ -527,7 +527,7 @@ async function createBuyOffer() { "TransactionType": "NFTokenCreateOffer", "Account": wallet.classicAddress, "Owner": owner.value, - "TokenID": tokenId.value, + "NFTokenID": nftokenId.value, "Amount": amount.value, "Flags": parseInt(flags.value) } @@ -554,7 +554,7 @@ async function createBuyOffer() { try { nftSellOffers = await client.request({ method: "nft_sell_offers", - tokenid: tokenId.value + tokenid: nftokenId.value }) } catch (err) { console.log("No sell offers.") @@ -565,7 +565,7 @@ async function createBuyOffer() { try { nftBuyOffers = await client.request({ method: "nft_buy_offers", - tokenid: tokenId.value }) + tokenid: nftokenId.value }) } catch (err) { console.log("No buy offers.") } @@ -608,14 +608,14 @@ To create an offer to buy a `NFToken`: 1. Enter your **Account** and **Secret** in the appropriate fields. -2. Enter the **Token ID** of the `NFToken` you want to list. +2. Enter the **NFToken ID** of the `NFToken` you want to list. 3. Click **Get Offers**. The `getOffers()` function steps are: -1. Connect to the devnet server. +1. Connect to the nft-devnet server. 2. Request `nft_sell_offers` and `nft_buy_offers` for your wallet account and send the results to your console log. 3. Disconnect from the server. @@ -653,7 +653,7 @@ async function getOffers() { try { nftSellOffers = await client.request({ method: "nft_sell_offers", - tokenid: tokenId.value + tokenid: nftokenId.value }) } catch (err) { console.log("No sell offers.") @@ -664,7 +664,7 @@ async function getOffers() { try { nftBuyOffers = await client.request({ method: "nft_buy_offers", - tokenid: tokenId.value + tokenid: nftokenId.value }) } catch (err) { console.log("No buy offers.") @@ -695,7 +695,7 @@ To cancel an offer to sell or buy a `NFToken`: 1. Enter your **Account** and **Secret** in the appropriate fields. -2. Enter the **Token Offer Index** of the offer you want to cancel. (Labeled as **Index** in the responses to `nft_buy_offers `and` nft_sell_offers` requests.) +2. Enter the **NFToken Offer Index** of the offer you want to cancel. (Labeled as nft_offer_index in the responses to `nft_buy_offers `and` nft_sell_offers` requests.) 3. Click **Cancel Offer**. @@ -705,7 +705,7 @@ The `cancelOffer()` function steps are: -1. Connect to the devnet server. +1. Connect to the nft-devnet server. 2. Prepare a transaction blob. 3. Submit the transaction and wait for the results. 4. Request lists of current Sell Offers and Buy Offers. @@ -722,7 +722,7 @@ The `cancelOffer()` function steps are: -1. Connect to the devnet server. +1. Connect to the nft-devnet server. ```js @@ -740,13 +740,13 @@ async function cancelOffer() { ```js - const tokenOfferID = tokenOfferIndex.value + const tokenOfferID = nftokenOfferIndex.value const tokenOffers = [tokenOfferID] const transactionBlob = { "TransactionType": "NFTokenCancelOffer", "Account": wallet.classicAddress, - "TokenOffers": tokenOffers + "NFTokenOffers": tokenOffers } ``` @@ -772,7 +772,7 @@ async function cancelOffer() { try { nftSellOffers = await client.request({ method: "nft_sell_offers", - tokenid: tokenId.value + tokenid: nftokenId.value }) } catch (err) { console.log("No sell offers.") @@ -783,7 +783,7 @@ async function cancelOffer() { try { nftBuyOffers = await client.request({ method: "nft_buy_offers", - tokenid: tokenId.value }) + tokenid: nftokenId.value }) } catch (err) { console.log("No buy offers.") } @@ -831,14 +831,14 @@ To accept a sell offer: 1. Enter your **Account** and **Secret** in the appropriate fields. -2. Enter the **Token Offer Index** of the offer you want to accept. (Labeled as **Index** in the responses to `nft_sell_offers` requests.) +2. Enter the **Token Offer Index** of the offer you want to accept. (Labeled as `nft_offer_index` in the responses to `nft_sell_offers` requests.) 3. Click **Accept Sell Offer**. The `acceptSellOffer()` function steps are: -1. Connect to the devnet server. +1. Connect to the nft-devnet server. 2. Prepare a transaction blob. 3. Submit the transaction and wait for the results. 4. Display the results in your console log. @@ -854,7 +854,7 @@ The `acceptSellOffer()` function steps are: -1. Connect to the devnet server. +1. Connect to the nft-devnet server. ```js @@ -875,7 +875,7 @@ async function acceptSellOffer() { const transactionBlob = { "TransactionType": "NFTokenAcceptOffer", "Account": wallet.classicAddress, - "SellOffer": tokenOfferIndex.value, + "SellOffer": nftokenOfferIndex.value, } ``` @@ -927,14 +927,14 @@ To accept a buy offer: 1. Enter your **Account** and **Secret** in the appropriate fields. -2. Enter the **Token Offer Index** of the offer you want to accept. (Labeled as **Index** in the responses to `nft_sell_offers` requests.) +2. Enter the **NFToken Offer Index** of the offer you want to accept. (Labeled as `nft_offer_index` in the responses to `nft_sell_offers` requests.) 3. Click **Accept Buy Offer**. The `acceptBuyOffer()` function steps are: -1. Connect to the devnet server. +1. Connect to the nft-devnet server. 2. Prepare a transaction blob. 3. Submit the transaction and wait for the results. 4. Display the results in your console log. @@ -952,7 +952,7 @@ async function acceptBuyOffer() { -1. Connect to the devnet server. +1. Connect to the nft-devnet server. ```js @@ -971,7 +971,7 @@ async function acceptBuyOffer() { const transactionBlob = { "TransactionType": "NFTokenAcceptOffer", "Account": wallet.classicAddress, - "BuyOffer": tokenOfferIndex.value + "BuyOffer": nftokenOfferIndex.value } ``` @@ -1051,7 +1051,7 @@ The remainder of the test harness file creates a standard HTML form with 9 butto - Token URL + NFToken URL @@ -1061,16 +1061,16 @@ value = "ipfs://bafybeigdyrzt5sfp7udm7hu76uh7y26nf4dfuylqabf3oclgtqy55fbzdi" siz - Token ID - + NFToken ID + Amount - Token Offer Index - + NFToken Offer Index + Owner