("https://yourhost/metadata.json"));
-
+
vectorAttributes.push_back(nameAttribute1);
vectorAttributes.push_back(nameAttribute2);
vectorAttributes.push_back(nameAttribute3);
@@ -433,9 +433,9 @@ Take note of these data points:
- **`description`**: This field provides a human-readable description of the asset. It's a text description that helps users understand the nature or significance of the asset.
-- **`media`**: The `media` field contains a URL pointing to an image representation of the asset. It supports PNG, GIF, and JPG file formats.
+- **`media`**: The `media` field contains a URL pointing to an image representation of the asset. It supports PNG, GIF, and JPG file formats.
-- **`external_url`**: The "external_url" field is a URL pointing to an external application or website where users can view additional information or interact with the asset.
+- **`external_url`**: The "external_url" field is a URL pointing to an external application or website where users can view additional information or interact with the asset.
- **`attributes`**: This is an object array where each object should contain an `title` and `value` fields. The attribute `title` defines the type of trait or attribute associated with the asset, while `value` can be a string or a number, representing the value of that trait or attribute.
diff --git a/docs/02-guides/01-platform/01-managing-tokens/04-minting-a-token.md b/docs/02-guides/01-platform/01-managing-tokens/04-minting-a-token.md
index da72c33..9f33619 100644
--- a/docs/02-guides/01-platform/01-managing-tokens/04-minting-a-token.md
+++ b/docs/02-guides/01-platform/01-managing-tokens/04-minting-a-token.md
@@ -8,15 +8,15 @@ import GlossaryTerm from '@site/src/components/GlossaryTerm';
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
-Now that you've got your tokens created, it's time to start minting them into player wallets as they are earned.
+Now that you've got your tokens created, it's time to start minting them into player wallets as they are earned.
-We call this "Play-to-Mint," giving players the power to create tokens themselves, which feels more rewarding.
+We call this "Play-to-Mint," giving players the power to create tokens themselves, which feels more rewarding.
Plus, it keeps your processes more efficient by delivering tokens right to players' wallets without any unnecessary `transfer` transactions.
:::info What you'll need:
-- Some [ Enjin Coin](/06-enjin-products/02-enjin-coin.md) on Enjin Matrixchain to pay for and a deposit of 0.01 ENJ is required for the , for each new token holder.
-If the token has , each new unit minted will require the same amount of ENJ to be infused.
+- Some [ Enjin Coin](/06-enjin-products/02-enjin-coin.md) on Enjin Matrixchain to pay for and a deposit of 0.01 ENJ is required for the , for each new token holder.
+If the token has , each new unit minted will require the same amount of ENJ to be infused.
You can obtain cENJ (Canary ENJ) for testing from the [Canary faucet](https://faucet.canary.enjin.io/).
- An [Enjin Platform Account](/01-getting-started/04-using-the-enjin-platform.md).
- A [Collection](/02-guides/01-platform/01-managing-tokens/01-creating-collections.md) and a [Token](/02-guides/01-platform/01-managing-tokens/02-creating-tokens/02-creating-tokens.md) to mint.
@@ -29,7 +29,7 @@ You can obtain cENJ (Canary ENJ) for testing from the [Canary faucet](https://fa
## Option A. Using the Enjin Dashboard
-In the Platform menu, navigate to "**[Tokens](https://platform.canary.enjin.io/tokens)**".
+In the Platform menu, navigate to "**[Tokens](https://platform.canary.enjin.io/tokens)**".
**Locate the token** you wish to mint, click the **3 vertical dots** (**⋮**) to it's right, then click the "**Mint**" button.

@@ -66,7 +66,7 @@ mutation BatchMint {
recipients: [
{
account: "0xaa89f9099742a928051c41eadba188ad4e863539ff96f16722ae7850271c2921" #The recipient of the mint
- mintParams: {
+ mintParams: {
amount:1 #Amount to mint
tokenId: {integer: 6533} #Token ID to mint
}
diff --git a/docs/02-guides/01-platform/01-managing-tokens/05-transferring-tokens.md b/docs/02-guides/01-platform/01-managing-tokens/05-transferring-tokens.md
index 5f830d4..325d7bc 100644
--- a/docs/02-guides/01-platform/01-managing-tokens/05-transferring-tokens.md
+++ b/docs/02-guides/01-platform/01-managing-tokens/05-transferring-tokens.md
@@ -15,7 +15,7 @@ You will need to transfer tokens for:
- Providing a seamless user experience by allowing token transfers without leaving the game environment.
:::info What you'll need:
-- Some [ Enjin Coin](/06-enjin-products/02-enjin-coin.md) on Enjin Matrixchain to pay for and a deposit of 0.01 ENJ is required for the , for each new token holder.
+- Some [ Enjin Coin](/06-enjin-products/02-enjin-coin.md) on Enjin Matrixchain to pay for and a deposit of 0.01 ENJ is required for the , for each new token holder.
You can obtain cENJ (Canary ENJ) for testing from the [Canary faucet](https://faucet.canary.enjin.io/).
- An [Enjin Platform Account](/01-getting-started/04-using-the-enjin-platform.md).
- A [Collection](/02-guides/01-platform/01-managing-tokens/01-creating-collections.md) and a [Token](/02-guides/01-platform/01-managing-tokens/02-creating-tokens/02-creating-tokens.md) to mint.
@@ -28,7 +28,7 @@ You can obtain cENJ (Canary ENJ) for testing from the [Canary faucet](https://fa
## Option A. Using the Enjin Dashboard
-In the Platform menu, navigate to "**[Tokens](https://platform.canary.enjin.io/tokens)**".
+In the Platform menu, navigate to "**[Tokens](https://platform.canary.enjin.io/tokens)**".
**Locate the token** you wish to transfer, click the **3 vertical dots** (**⋮**) to it's right, then click the "**Transfer**" button.

@@ -37,7 +37,7 @@ In the Platform menu, navigate to "**[Tokens](https://platform.canary.enjin.io/t
Click on the "**Batch**" button, followed by "**Batch Transfer**".
:::
-Fill in the recipient, amount, and other optional arguments in the corresponding fields.
+Fill in the recipient, amount, and other optional arguments in the corresponding fields.
Once you're satisfied with the options, click on the "**Transfer**" button at the bottom right corner to create the request.
@@ -56,7 +56,7 @@ Since this request requires a , it'll need to b
- If a **Wallet Daemon is running and configured**, the transaction request will be **signed automatically**.
- If **a wallet is connected** such as the Enjin Wallet or Polkadot.js, the transaction must be **signed manually** by clicking the "**Sign**" button and **approving the signature request** in your wallet.
-If you're looking to distribute tokens to your community or players, but don't have their account addresses, don't worry! Our solution is Enjin Beam.
+If you're looking to distribute tokens to your community or players, but don't have their account addresses, don't worry! Our solution is Enjin Beam.
Proceed to the [Distributing Tokens via QR](/02-guides/01-platform/01-managing-tokens/06-create-qr-drops.md) tutorial to learn more.
## Option B. Using the Enjin API & SDKs
@@ -474,7 +474,7 @@ mutation TransferKeepAlive(
variables = {
'recipient': "cxLU94nRz1en6gHnXnYPyTdtcZZ9dqBasexvexjArj4V1Qr8f", #Specify the recipent address
'amount': 1 #Specify the amount of tokens to transfer
-
+
}
response = requests.post('https://platform.canary.enjin.io/graphql',
@@ -488,10 +488,10 @@ print(response.json())
:::info **Notes:**
- `amount` argument
- - In the `TransferBalance` mutation, the `amount` argument is denoted in `u128`. This means that the number you specify is divided by 10^18 to determine the actual amount of ENJ to be transferred.
+ - In the `TransferBalance` mutation, the `amount` argument is denoted in `u128`. This means that the number you specify is divided by 10^18 to determine the actual amount of ENJ to be transferred.
In the example above, an `amount` of `5000000000000000000` will actually send 5 ENJ. Keep this in mind when specifying the `amount` in your mutations.
- `keepAlive` argument
- - Set to true if you want to make sure the account doesn't get reaped.
+ - Set to true if you want to make sure the account doesn't get reaped.
Learn more about keepAlive argument [here](/03-api-reference/04-important-arguments.md#keepalive)
:::
@@ -708,12 +708,12 @@ print(response.json())
A WebSocket event will also be fired so you can pick up the transfer transaction in real time by listening to the app channel on the WebSocket.
:::tip Need to send a transaction request to user's wallet?
-This can be done using Enjin Platform API & WalletConnect!
+This can be done using Enjin Platform API & WalletConnect!
To learn more, check out the [Using WalletConnect page](/02-guides/01-platform/02-managing-users/01-connecting-user-wallets/01-using-wallet-connect.md).
:::
:::info Explore More Arguments
-For a comprehensive view of all available arguments for queries and mutations, please refer to our [API Reference](/03-api-reference/03-api-reference.md). This resource will guide you on how to use the GraphiQL Playground to explore the full structure and functionality of our API.
+For a comprehensive view of all available arguments for queries and mutations, please refer to our [API Reference](/03-api-reference/03-api-reference.md). This resource will guide you on how to use the GraphiQL Playground to explore the full structure and functionality of our API.
For instance, you'll find settings such as `continueOnFailure` to skip data that would cause the whole batch to fail, or the ability to sign using a managed wallet with the `signingAccount` argument.
:::
diff --git a/docs/02-guides/01-platform/01-managing-tokens/06-create-qr-drops.md b/docs/02-guides/01-platform/01-managing-tokens/06-create-qr-drops.md
index e5a5df6..306a541 100644
--- a/docs/02-guides/01-platform/01-managing-tokens/06-create-qr-drops.md
+++ b/docs/02-guides/01-platform/01-managing-tokens/06-create-qr-drops.md
@@ -11,7 +11,7 @@ import TabItem from '@theme/TabItem';
is a simple way to distribute digital assets like tokens and collectibles using QR codes. Users just need to scan a Beam QR code with their Enjin Wallet to receive tokens directly. It's a great tool for marketing campaigns, events, or promotions to give away items and easily bring new users into your ecosystem.
:::info What you'll need:
-- Some [ Enjin Coin](/06-enjin-products/02-enjin-coin.md) on Enjin Matrixchain to pay for and a deposit of 0.01 ENJ is required for the , for each new token holder.
+- Some [ Enjin Coin](/06-enjin-products/02-enjin-coin.md) on Enjin Matrixchain to pay for and a deposit of 0.01 ENJ is required for the , for each new token holder.
You can obtain cENJ (Canary ENJ) for testing from the [Canary faucet](https://faucet.canary.enjin.io/).
- An [Enjin Platform Account](/01-getting-started/04-using-the-enjin-platform.md).
- A [Collection](/02-guides/01-platform/01-managing-tokens/01-creating-collections.md) and a [Token](/02-guides/01-platform/01-managing-tokens/02-creating-tokens/02-creating-tokens.md) to mint.
@@ -58,7 +58,7 @@ Now, you'll fill out the details for your Beam:
- **Why use Single-use?** It gives you precise control over which specific claim (and thus which token) goes to which person. It's also more secure for private distributions; you can share individual QR codes with specific users without worrying about a main QR code being leaked publicly.
:::
-Once you're satisfied with the options, click on the "**Create**" button at the bottom right corner to create the request.
+Once you're satisfied with the options, click on the "**Create**" button at the bottom right corner to create the request.
If a signature request is needed, approve it.
Once the Beam is created, locate it in the "**Beams**" menu, click the **3 vertical dots** (**⋮**) to it's right, then click the "**Claim**" button to view the QR code.
@@ -66,12 +66,12 @@ Once the Beam is created, locate it in the "**Beams**" menu, click the **3 verti

:::warning Need to get all of the "Single-Use" QR codes?
-Please note, viewing all of the "Single-Use" QR codes is currently not available in the Platform User Interface.
+Please note, viewing all of the "Single-Use" QR codes is currently not available in the Platform User Interface.
For the time being, it can be viewed programmatically only via [Enjin API & SDKs](#option-b-using-the-enjin-api--sdks)
:::
-The Enjin Beam is now ready to be shared to distribute tokens. Users can scan the QR code and instantly receive your token!
-Next skillset to learn is mutating a collection / token.
+The Enjin Beam is now ready to be shared to distribute tokens. Users can scan the QR code and instantly receive your token!
+Next skillset to learn is mutating a collection / token.
Proceed to the [Freezing & Thawing](/02-guides/01-platform/01-managing-tokens/07-freezing-thawing.md) tutorial to learn more.
## Option B. Using the Enjin API & SDKs
@@ -403,7 +403,7 @@ query GetBeam {
start
end
isClaimable
- claimsRemaining
+ claimsRemaining
qr {
url
payload
@@ -415,7 +415,7 @@ query GetBeam {
forceSingleMint
frozen
network
- }
+ }
}
}
```
@@ -551,7 +551,7 @@ int main() {
std::cout << error.GetMessage().value() << std::endl;
}
}
-
+
client.reset();
return 0;
@@ -578,7 +578,7 @@ fetch('https://platform.canary.enjin.io/graphql', {
start
end
isClaimable
- claimsRemaining
+ claimsRemaining
qr {
url
payload
@@ -590,7 +590,7 @@ fetch('https://platform.canary.enjin.io/graphql', {
forceSingleMint
frozen
network
- }
+ }
}
}
`,
@@ -622,7 +622,7 @@ axios.post('https://platform.canary.enjin.io/graphql', {
start
end
isClaimable
- claimsRemaining
+ claimsRemaining
qr {
url
payload
@@ -634,7 +634,7 @@ axios.post('https://platform.canary.enjin.io/graphql', {
forceSingleMint
frozen
network
- }
+ }
}
}
`,
@@ -666,7 +666,7 @@ query GetBeam
start
end
isClaimable
- claimsRemaining
+ claimsRemaining
qr {
url
payload
@@ -678,7 +678,7 @@ query GetBeam
forceSingleMint
frozen
network
- }
+ }
}
}
'''
diff --git a/docs/02-guides/01-platform/01-managing-tokens/07-freezing-thawing.md b/docs/02-guides/01-platform/01-managing-tokens/07-freezing-thawing.md
index 3de7469..677b54e 100644
--- a/docs/02-guides/01-platform/01-managing-tokens/07-freezing-thawing.md
+++ b/docs/02-guides/01-platform/01-managing-tokens/07-freezing-thawing.md
@@ -13,7 +13,7 @@ import TabItem from '@theme/TabItem';
One such use-case is the implementation of "Soulbound" tokens. A Soulbound token is bound to a specific address and cannot be transferred out of the wallet it's minted on. This feature can be used to create unique gameplay mechanics, loyalty rewards, and more.
:::note
-Freezing only applies to ing and transfers, which also results in marketplace listings being unpurchasable.
+Freezing only applies to ing and transfers, which also results in marketplace listings being unpurchasable.
Freezing does not suspend token minting.
:::
@@ -23,17 +23,17 @@ A **freeze state** determines whether a token can be transferred and the conditi
#### Explanation of Freeze States
-- **Permanent:**
- The token is permanently frozen and cannot be transferred to another account under any circumstances. Use this state for tokens that are intended to stay bound to their original holder, such as "Soulbound" tokens for identity or loyalty purposes.
+- **Permanent:**
+ The token is permanently frozen and cannot be transferred to another account under any circumstances. Use this state for tokens that are intended to stay bound to their original holder, such as "Soulbound" tokens for identity or loyalty purposes.
-- **Temporary:**
+- **Temporary:**
The token is temporarily frozen, restricting transfers until it is explicitly thawed by the collection owner. This state is ideal for implementing time-limited restrictions or conditional asset movement.
-- **Never:**
- The token is always transferrable and cannot be frozen. Choose this state if you want the token to remain unrestricted in its movement across wallets and platforms.
+- **Never:**
+ The token is always transferrable and cannot be frozen. Choose this state if you want the token to remain unrestricted in its movement across wallets and platforms.
:::info What you'll need:
-- Some [ Enjin Coin](/06-enjin-products/02-enjin-coin.md) on Enjin Matrixchain to pay for .
+- Some [ Enjin Coin](/06-enjin-products/02-enjin-coin.md) on Enjin Matrixchain to pay for .
You can obtain cENJ (Canary ENJ) for testing from the [Canary faucet](https://faucet.canary.enjin.io/).
- An [Enjin Platform Account](/01-getting-started/04-using-the-enjin-platform.md).
- A [Collection](/02-guides/01-platform/01-managing-tokens/01-creating-collections.md) and a [Token](/02-guides/01-platform/01-managing-tokens/02-creating-tokens/02-creating-tokens.md) to freeze.
@@ -46,15 +46,15 @@ You can obtain cENJ (Canary ENJ) for testing from the [Canary faucet](https://fa
## Option A. Using the Enjin Dashboard
-:::tip Applying Freeze/Thaw Actions to Collections and Tokens
-This tutorial illustrates the process of freezing a collection.
-However, the same steps can be applied to freeze or thaw tokens.
+:::tip Applying Freeze/Thaw Actions to Collections and Tokens
+This tutorial illustrates the process of freezing a collection.
+However, the same steps can be applied to freeze or thaw tokens.
Simply navigate to the corresponding menu for tokens instead of collections, or for thawing instead of freezing.
:::
### Freezing an entire collection
-In the Platform menu, navigate to "**[Collections](https://platform.canary.enjin.io/collections)**".
+In the Platform menu, navigate to "**[Collections](https://platform.canary.enjin.io/collections)**".
**Locate the collection** you wish to freeze, click the **3 vertical dots** (**⋮**) to it's right, then click the "**Freeze**" button.

@@ -219,7 +219,7 @@ fetch('https://platform.canary.enjin.io/graphql', {
$freeze_type: FreezeType!
) {
Freeze(
- collectionId: $collection_id
+ collectionId: $collection_id
freezeType: $freeze_type
){
id
@@ -250,7 +250,7 @@ axios.post('https://platform.canary.enjin.io/graphql', {
$freeze_type: FreezeType!
) {
Freeze(
- collectionId: $collection_id
+ collectionId: $collection_id
freezeType: $freeze_type
){
id
@@ -281,7 +281,7 @@ mutation FreezeCollection
$freeze_type: FreezeType!
) {
Freeze(
- collectionId: $collection_id
+ collectionId: $collection_id
freezeType: $freeze_type
){
id
@@ -528,7 +528,7 @@ mutation FreezeToken
$token_id: BigInt!
$freeze_type: FreezeType!
$freeze_state: FreezeStateType
-
+
) {
Freeze(
collectionId: $collection_id
@@ -702,7 +702,7 @@ fetch('https://platform.canary.enjin.io/graphql', {
$freeze_type: FreezeType!
) {
Thaw(
- collectionId: $collection_id
+ collectionId: $collection_id
freezeType: $freeze_type
){
id
@@ -733,7 +733,7 @@ axios.post('https://platform.canary.enjin.io/graphql', {
$freeze_type: FreezeType!
) {
Thaw(
- collectionId: $collection_id
+ collectionId: $collection_id
freezeType: $freeze_type
){
id
@@ -764,7 +764,7 @@ mutation ThawCollection
$freeze_type: FreezeType!
) {
Thaw(
- collectionId: $collection_id
+ collectionId: $collection_id
freezeType: $freeze_type
){
id
@@ -1037,6 +1037,6 @@ For instance, you'll find settings such as `continueOnFailure` to skip data that
:::
:::tip Need to send a transaction request to user's wallet?
-This can be done using Enjin Platform API & WalletConnect!
+This can be done using Enjin Platform API & WalletConnect!
To learn more, check out the [Using WalletConnect page](/02-guides/01-platform/02-managing-users/01-connecting-user-wallets/01-using-wallet-connect.md).
:::
diff --git a/docs/02-guides/01-platform/01-managing-tokens/08-burning-destroying-tokens.md b/docs/02-guides/01-platform/01-managing-tokens/08-burning-destroying-tokens.md
index 56bf50b..55cea11 100644
--- a/docs/02-guides/01-platform/01-managing-tokens/08-burning-destroying-tokens.md
+++ b/docs/02-guides/01-platform/01-managing-tokens/08-burning-destroying-tokens.md
@@ -8,11 +8,11 @@ import GlossaryTerm from '@site/src/components/GlossaryTerm';
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
-"Melting" (often called "Burning") refers to the process of decreasing a token's supply and removing it from circulation, or in some cases, even removing the token from the blockchain entirely.
+"Melting" (often called "Burning") refers to the process of decreasing a token's supply and removing it from circulation, or in some cases, even removing the token from the blockchain entirely.
Melting a token with releases the Infused ENJ to the holder.
:::info What you'll need:
-- Some [Enjin Coin](/06-enjin-products/02-enjin-coin.md) on Enjin Matrixchain to pay for .
+- Some [Enjin Coin](/06-enjin-products/02-enjin-coin.md) on Enjin Matrixchain to pay for .
You can obtain cENJ (Canary ENJ) for testing from the [Canary faucet](https://faucet.canary.enjin.io/).
- An [Enjin Platform Account](/01-getting-started/04-using-the-enjin-platform.md).
- A [Collection](/02-guides/01-platform/01-managing-tokens/01-creating-collections.md) or a [Token](/02-guides/01-platform/01-managing-tokens/02-creating-tokens/02-creating-tokens.md) to melt/destroy.
@@ -27,7 +27,7 @@ You can obtain cENJ (Canary ENJ) for testing from the [Canary faucet](https://fa
### Melting token's supply
-In the Platform menu, navigate to "**[Tokens](https://platform.canary.enjin.io/tokens)**".
+In the Platform menu, navigate to "**[Tokens](https://platform.canary.enjin.io/tokens)**".
**Locate the token** you wish to melt, click the **3 vertical dots** (**⋮**) to it's right, then click the "**Burn**" button.

@@ -56,14 +56,14 @@ Since this request requires a , it'll need to b
:::info To destroy a token, these requirements must be met:
- The caller is the collection owner
- The token has no attributes
- - If the token has attributes, you can remove the attributes by clicking the **3 vertical dots** (**⋮**) next to the token, followed by "**Attributes**" and selecting "**Remove All"**.
+ - If the token has attributes, you can remove the attributes by clicking the **3 vertical dots** (**⋮**) next to the token, followed by "**Attributes**" and selecting "**Remove All"**.
- The token has 0 supply
- - If the token has supply, you can follow the above guide [Burning token's supply](#melting-tokens-supply) to remove all token supply (as long as you own all of the token's supply)
+ - If the token has supply, you can follow the above guide [Burning token's supply](#melting-tokens-supply) to remove all token supply (as long as you own all of the token's supply)
Note - you can remove the supply and destroy the token in the same melt transaction.
:::
-Melting a token and destroying it are two different actions.
-The action demonstrated above is the action of melting a token, which decreases it's circulating supply.
+Melting a token and destroying it are two different actions.
+The action demonstrated above is the action of melting a token, which decreases it's circulating supply.
While destroying a token removes the token from the blockchain, and retrieves the to the collection owner.
To destroy a token, follow the above instructions for Melting a token, but make sure to tick the `Remove Token Storage` box.
@@ -82,7 +82,7 @@ To destroy a token, follow the above instructions for Melting a token, but make
- If the collection has some tokens, you can follow the above guide [Destroying a token and removing it from the Blockchain](#destroying-a-token-and-removing-it-from-the-blockchain) for each of the tokens in the collection, to destroy them all.
:::
-In the Platform menu, navigate to "**[Collections](https://platform.canary.enjin.io/collections)**".
+In the Platform menu, navigate to "**[Collections](https://platform.canary.enjin.io/collections)**".
**Locate the collection** you wish to destroy, click the **3 vertical dots** (**⋮**) to it's right, then click the "**Destroy**" button.

diff --git a/docs/02-guides/01-platform/01-managing-tokens/09-fetching-token-holders.md b/docs/02-guides/01-platform/01-managing-tokens/09-fetching-token-holders.md
index 012f88c..13a5607 100644
--- a/docs/02-guides/01-platform/01-managing-tokens/09-fetching-token-holders.md
+++ b/docs/02-guides/01-platform/01-managing-tokens/09-fetching-token-holders.md
@@ -21,8 +21,8 @@ Accessing this data is valuable for several purposes:
## Fetching Token Holders with the [Enjin API](/02-guides/01-platform/01-managing-tokens/02-creating-tokens/02-creating-tokens.md)
:::warning Fetching Tokens Limitations
-Please note that the `GetToken` query is limited to tokens from collections that were created via the auth-ed Enjin Platform account.
-To get a token that was created elsewhere (via a different Enjin Platform account / [NFT.io](https://nft.io) / [Enjin Console](https://console.enjin.io) / etc.) the collection must be "Tracked" first, or the query response will return an error.
+Please note that the `GetToken` query is limited to tokens from collections that were created via the auth-ed Enjin Platform account.
+To get a token that was created elsewhere (via a different Enjin Platform account / [NFT.io](https://nft.io) / [Enjin Console](https://console.enjin.io) / etc.) the collection must be "Tracked" first, or the query response will return an error.
Learn more about tracking a collection in the [Tracking Collections section below](#tracking-collections).
:::
@@ -348,8 +348,8 @@ The response may be displayed on several pages. To view all of it, you may need
## Fetching Collection Holders with the [Enjin API](/01-getting-started/05-using-enjin-api/05-using-enjin-api.md)
:::warning Fetching Collections Limitations
-Please note that the `GetCollections` query is limited to collections that were created via the auth-ed Enjin Platform Cloud account.
-To get a collection that was created elsewhere (via a different Enjin Platform Cloud account / [NFT.io](https://nft.io) / [Enjin Console](https://console.enjin.io) / etc.) the collection must be "Tracked" first, or the query response will return an error.
+Please note that the `GetCollections` query is limited to collections that were created via the auth-ed Enjin Platform Cloud account.
+To get a collection that was created elsewhere (via a different Enjin Platform Cloud account / [NFT.io](https://nft.io) / [Enjin Console](https://console.enjin.io) / etc.) the collection must be "Tracked" first, or the query response will return an error.
Learn more about tracking a collection in the [Tracking Collections section below](#tracking-collections).
:::
diff --git a/docs/02-guides/01-platform/02-managing-users/01-connecting-user-wallets/01-using-wallet-connect.md b/docs/02-guides/01-platform/02-managing-users/01-connecting-user-wallets/01-using-wallet-connect.md
index 8f44036..9dd47b8 100644
--- a/docs/02-guides/01-platform/02-managing-users/01-connecting-user-wallets/01-using-wallet-connect.md
+++ b/docs/02-guides/01-platform/02-managing-users/01-connecting-user-wallets/01-using-wallet-connect.md
@@ -8,13 +8,13 @@ import GlossaryTerm from '@site/src/components/GlossaryTerm';
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
-[WalletConnect](https://docs.walletconnect.com/) is an open-source protocol that connects your mobile wallet to decentralized applications.
+[WalletConnect](https://docs.walletconnect.com/) is an open-source protocol that connects your mobile wallet to decentralized applications.
Using the Platform API and WalletConnect you can send any transaction request directly to your user's wallet app.
:::info What you'll need:
- Node.js 18+ and yarn installed
- A mobile device with [Enjin Wallet app](https://enjin.io/wallet) installed
-- A Canary wallet with at least 6.5 ENJ in it to cover for and .
+- A Canary wallet with at least 6.5 ENJ in it to cover for and .
You can obtain cENJ for testing from the [Canary faucet](https://faucet.canary.enjin.io/).
- An [Enjin Platform Account](/01-getting-started/04-using-the-enjin-platform.md) (Canary).
:::
@@ -25,12 +25,12 @@ On production apps, you will need [WalletConnect's SDK](https://docs.walletconne
Start by cloning the polkadot-onboard repository: https://github.com/enjin-forks/polkadot-onboard.git
-Once cloned, install the packages, install the workspace, build the workspace, and start the example project.
+Once cloned, install the packages, install the workspace, build the workspace, and start the example project.
To do that, navigate to the cloned repository folder and run the following commands:
:::info **Note:**
-The commands below are Bash commands, which are commonly run in a Unix-like environment (such as macOS, or Linux).
-Windows users may encounter errors if they try running these commands directly in Command Prompt or PowerShell.
+The commands below are Bash commands, which are commonly run in a Unix-like environment (such as macOS, or Linux).
+Windows users may encounter errors if they try running these commands directly in Command Prompt or PowerShell.
To run them successfully on Windows, use a Bash-compatible terminal, like [Git Bash](https://gitforwindows.org/).
:::
@@ -49,7 +49,7 @@ yarn start:react-next
Navigate to http://localhost:3000 using your browser. If everything went well, a sample page should load up.
:::info Configured Chain
-The sample project is set to broadcast transaction on the Canary Matrixchain Testnet.
+The sample project is set to broadcast transaction on the Canary Matrixchain Testnet.
To configure a different blockchain, you can adjust the `chainIds` in the `examples/react-next/components/ConnectContainer.tsx` file.
Chain IDs on Enjin Chains:
@@ -61,7 +61,7 @@ Chain IDs on Enjin Chains:
## Connect user's wallet
-To send transactions to your user, he must be connected to your dapp.
+To send transactions to your user, he must be connected to your dapp.
Clicking `Get Wallets`, followed by `Polkadot Demo 2.0`, initiates a connection between your user and your dapp.
@@ -74,8 +74,8 @@ Once the user scans the QR code with his Enjin wallet app (or any other wallet w
-Once a connection was made, you'll receive a list of all addresses connected from your user's wallet.
-Now you are able to send any transaction request to your user's wallet.
+Once a connection was made, you'll receive a list of all addresses connected from your user's wallet.
+Now you are able to send any transaction request to your user's wallet.
To demonstrate a sample transaction request, click the "**Submit Transaction with Polkadot.JS**" button on one of the displayed addresses.
@@ -94,7 +94,7 @@ In the next section, you'll learn how to construct your own transaction requests
## How to construct a custom transaction?
-In the example above, we have sent a request to broadcast a transaction that was already constructed for us.
+In the example above, we have sent a request to broadcast a transaction that was already constructed for us.
But how was that transaction constructed and how can we send any transaction we want? Let's find out!
At `examples/react-next/pages/api`, there's two endpoints we'll be using:
@@ -102,7 +102,7 @@ At `examples/react-next/pages/api`, there's two endpoints we'll be using:
- `transaction.tsx` endpoint which constructs the transaction
- `send.tsx` which broadcasts the transaction request to the blockchain using Enjin Platform API.
-First, we need to insert our Enjin platform API key to be able to interact with it.
+First, we need to insert our Enjin platform API key to be able to interact with it.
If you haven't created an api key yet, you can do so in https://platform.canary.enjin.io/settings.
In both `examples/react-next/pages/api/transaction.tsx` and `examples/react-next/pages/api/send.tsx` files, replace `your-api-key` with your api key (note, there's three different api key fields that needs to be updated).
@@ -110,8 +110,8 @@ In both `examples/react-next/pages/api/transaction.tsx` and `examples/react-next
Once we've configured the Enjin Platform API key, rebuild and restart the project:
:::info **Note:**
-The commands below are Bash commands, which are commonly run in a Unix-like environment (such as macOS, or Linux).
-Windows users may encounter errors if they try running these commands directly in Command Prompt or PowerShell.
+The commands below are Bash commands, which are commonly run in a Unix-like environment (such as macOS, or Linux).
+Windows users may encounter errors if they try running these commands directly in Command Prompt or PowerShell.
To run them successfully on Windows, use a Bash-compatible terminal, like [Git Bash](https://gitforwindows.org/).
:::
@@ -120,13 +120,13 @@ yarn build:workspace
yarn start:react-next
```
-Now that the project is authenticated with the Enjin Platform, we can go ahead and press the "**Submit Transaction with Platform**" button.
-A `CreateCollection` request will be sent to your wallet, and once confirmed, the transaction will be signed and broadcasted to the blockchain.
+Now that the project is authenticated with the Enjin Platform, we can go ahead and press the "**Submit Transaction with Platform**" button.
+A `CreateCollection` request will be sent to your wallet, and once confirmed, the transaction will be signed and broadcasted to the blockchain.
Now it's time to break it down and understand how it works:
### Step #1: Constructing the transaction call
-We are constructing the transaction using the `transaction.tsx` endpoint.
+We are constructing the transaction using the `transaction.tsx` endpoint.
First, we make a query to the user's address to get its nonce:
```javascript
@@ -150,7 +150,7 @@ First, we make a query to the user's address to get its nonce:
});
```
-Once we get the nonce, we prepare the `CreateCollection` transaction call using Enjin Platform API.
+Once we get the nonce, we prepare the `CreateCollection` transaction call using Enjin Platform API.
You can use any other mutation Enjin Platform API offers, but for this example we're using CreateCollection.
```javascript
@@ -179,12 +179,12 @@ You can use any other mutation Enjin Platform API offers, but for this example w
});
```
-We are also passing the `signingAccount`. This is necessary so your daemon doesn't sign the transaction.
+We are also passing the `signingAccount`. This is necessary so your daemon doesn't sign the transaction.
In the mutation response, we're asking for the `id` and `signingPayloadJson`, which we will use in the next step.
### Step #2: Sending the Transaction Request to user's wallet
-With the payload in hand we pass that to our WalletConnect signer and ask it to sign. In the example project, this is done at: `examples/react-next/components/AccountBox.tsx`
+With the payload in hand we pass that to our WalletConnect signer and ask it to sign. In the example project, this is done at: `examples/react-next/components/AccountBox.tsx`
```javascript
const txId = data?.data?.CreateCollection?.id;
@@ -196,8 +196,8 @@ The above will trigger the Transaction Request dialog you saw previously, asking
### Step #3: Broadcasting the signed transaction
-Finally, we received the `txId`, `signature`, and `payload` from the user's wallet.
-We can now broadcast the signed transaction to the blockchain using the Enjin Platform API `SendTransaction` mutation.
+Finally, we received the `txId`, `signature`, and `payload` from the user's wallet.
+We can now broadcast the signed transaction to the blockchain using the Enjin Platform API `SendTransaction` mutation.
This is done at: `examples/react-next/pages/api/send.tsx`
```javascript
@@ -221,7 +221,7 @@ This is done at: `examples/react-next/pages/api/send.tsx`
});
```
-The Enjin Platform will broadcast the transaction to the blockchain and keep track of it.
+The Enjin Platform will broadcast the transaction to the blockchain and keep track of it.
You can see the transaction status in Enjin Platform: https://platform.canary.enjin.io/transactions
***
diff --git a/docs/02-guides/01-platform/02-managing-users/01-connecting-user-wallets/02-verifying-wallets.md b/docs/02-guides/01-platform/02-managing-users/01-connecting-user-wallets/02-verifying-wallets.md
index a6db0f2..78515b0 100644
--- a/docs/02-guides/01-platform/02-managing-users/01-connecting-user-wallets/02-verifying-wallets.md
+++ b/docs/02-guides/01-platform/02-managing-users/01-connecting-user-wallets/02-verifying-wallets.md
@@ -459,7 +459,7 @@ print(response.json())
```
:::info Balances Format
-API balances fields are formatted as u128 number type.
+API balances fields are formatted as u128 number type.
to get decimal value, divide the value by 10^18.
:::
diff --git a/docs/02-guides/01-platform/02-managing-users/02-reading-user-wallets.md b/docs/02-guides/01-platform/02-managing-users/02-reading-user-wallets.md
index 11baf2b..b475f41 100644
--- a/docs/02-guides/01-platform/02-managing-users/02-reading-user-wallets.md
+++ b/docs/02-guides/01-platform/02-managing-users/02-reading-user-wallets.md
@@ -7,9 +7,9 @@ description: "Explore how to read user wallet data, providing insights into user
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
-Fetching wallets is crucial because it allows you to see the contents of a wallet, including all tokens held within.
+Fetching wallets is crucial because it allows you to see the contents of a wallet, including all tokens held within.
-This is especially important in gaming and app development as it enables you to assign specific utilities or benefits to certain tokens.
+This is especially important in gaming and app development as it enables you to assign specific utilities or benefits to certain tokens.
For example, if a user has a particular token in their wallet, they might gain access to exclusive in-game items or features within an app, enhancing the user experience and adding value to the tokens.
@@ -244,7 +244,7 @@ print(response.json())
```
:::info Balances Format
-API balances fields are formatted as u128 number type.
+API balances fields are formatted as u128 number type.
to get decimal value, divide the value by 10^18.
:::
diff --git a/docs/02-guides/01-platform/02-managing-users/03-using-managed-wallets.md b/docs/02-guides/01-platform/02-managing-users/03-using-managed-wallets.md
index 931b6b3..f6314e5 100644
--- a/docs/02-guides/01-platform/02-managing-users/03-using-managed-wallets.md
+++ b/docs/02-guides/01-platform/02-managing-users/03-using-managed-wallets.md
@@ -22,7 +22,7 @@ Here's how the typical flow works:
This process ensures that users can interact with blockchain assets seamlessly within your application without needing to understand the underlying complexities of blockchain technology or operating his own crypto wallet.
:::info What you'll need:
-- Some [Enjin Coin](/06-enjin-products/02-enjin-coin.md) on Enjin Matrixchain to pay for .
+- Some [Enjin Coin](/06-enjin-products/02-enjin-coin.md) on Enjin Matrixchain to pay for .
You can obtain cENJ (Canary ENJ) for testing from the [Canary faucet](https://faucet.canary.enjin.io/).
- An [Enjin Platform Account](/01-getting-started/04-using-the-enjin-platform.md).
- A [Collection](/02-guides/01-platform/01-managing-tokens/01-creating-collections.md) and a [Token](/02-guides/01-platform/01-managing-tokens/02-creating-tokens/02-creating-tokens.md) to add to the wallet.
@@ -34,7 +34,7 @@ You can obtain cENJ (Canary ENJ) for testing from the [Canary faucet](https://fa
To create a Managed wallet, run the `CreateWallet` mutation, with a unique ID as a parameter.
-Choose a unique `externalId` for each player/user that can be cross-referenced later. This unique identifier should be something already associated with the player in your database, such as a player ID or username.
+Choose a unique `externalId` for each player/user that can be cross-referenced later. This unique identifier should be something already associated with the player in your database, such as a player ID or username.
By doing so, you will be able to consistently link the Managed Wallet to the respective player.
@@ -195,7 +195,7 @@ print(response.json())