GITBOOK-200: No subject

BuildOnViction · Sep 20, 2024 · b972111 · b972111
1 parent f17f772
commit b972111
Show file tree

Hide file tree

Showing 38 changed files with 57 additions and 20 deletions.
diff --git a/.gitbook/assets/Screenshot 2024-09-20 at 13.15.40.png b/.gitbook/assets/Screenshot 2024-09-20 at 13.15.40.png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1).png b/.gitbook/assets/image (1) (1).png
diff --git a/.gitbook/assets/image (1).png b/.gitbook/assets/image (1).png
diff --git a/.gitbook/assets/image (2) (1) (1).png b/.gitbook/assets/image (2) (1) (1).png
diff --git a/.gitbook/assets/image (2) (1).png b/.gitbook/assets/image (2) (1).png
diff --git a/.gitbook/assets/image (2).png b/.gitbook/assets/image (2).png
diff --git a/.gitbook/assets/image (3) (1) (1).png b/.gitbook/assets/image (3) (1) (1).png
diff --git a/.gitbook/assets/image (3) (1).png b/.gitbook/assets/image (3) (1).png
diff --git a/.gitbook/assets/image (3).png b/.gitbook/assets/image (3).png
diff --git a/.gitbook/assets/image (4) (1) (1) (1).png b/.gitbook/assets/image (4) (1) (1) (1).png
diff --git a/.gitbook/assets/image (4) (1) (1).png b/.gitbook/assets/image (4) (1) (1).png
diff --git a/.gitbook/assets/image (4) (1).png b/.gitbook/assets/image (4) (1).png
diff --git a/.gitbook/assets/image (4).png b/.gitbook/assets/image (4).png
diff --git a/.gitbook/assets/image (5) (1) (1).png b/.gitbook/assets/image (5) (1) (1).png
diff --git a/.gitbook/assets/image (5) (1).png b/.gitbook/assets/image (5) (1).png
diff --git a/.gitbook/assets/image (5).png b/.gitbook/assets/image (5).png
diff --git a/.gitbook/assets/image (6) (1) (1).png b/.gitbook/assets/image (6) (1) (1).png
diff --git a/.gitbook/assets/image (6) (1).png b/.gitbook/assets/image (6) (1).png
diff --git a/.gitbook/assets/image (6).png b/.gitbook/assets/image (6).png
diff --git a/.gitbook/assets/image (7) (1) (1) (1).png b/.gitbook/assets/image (7) (1) (1) (1).png
diff --git a/.gitbook/assets/image (7) (1) (1).png b/.gitbook/assets/image (7) (1) (1).png
diff --git a/.gitbook/assets/image (7) (1).png b/.gitbook/assets/image (7) (1).png
diff --git a/.gitbook/assets/image (7).png b/.gitbook/assets/image (7).png
diff --git a/.gitbook/assets/image (8) (1) (1) (1).png b/.gitbook/assets/image (8) (1) (1) (1).png
diff --git a/.gitbook/assets/image (8) (1) (1).png b/.gitbook/assets/image (8) (1) (1).png
diff --git a/.gitbook/assets/image (8) (1).png b/.gitbook/assets/image (8) (1).png
diff --git a/.gitbook/assets/image (8).png b/.gitbook/assets/image (8).png
diff --git a/.gitbook/assets/image.png b/.gitbook/assets/image.png
diff --git a/.gitbook/assets/success.png b/.gitbook/assets/success.png
diff --git a/archive/how-to-deploy-a-nft-token.md b/archive/how-to-deploy-a-nft-token.md
@@ -316,7 +316,7 @@ ganache-cli -p 8545
 
 `Ganache` will start running, listening on port `8545`. Automatically you will have 10 available wallets with their private keys and `100 ETH` each. You can use them to test your smart contracts.
 
-![](<../.gitbook/assets/image (4) (1) (1).png>)
+![](<../.gitbook/assets/image (4) (1) (1) (1).png>)
 
 ## 5. Adding Tests <a href="#id-9c8f" id="id-9c8f"></a>
 
@@ -484,9 +484,9 @@ You can use MEW to _**Write**_ and to _**Read**_ functions, like `getGradient`!
 In `Ethereum (Ropsten)`, the Etherscan page with [our migrated contract](https://ropsten.etherscan.io/address/0x22fb8a49811d33d34be96c82b3937b252e78a8d5) will **change** after the first token is minted. A new link will be displayed now to track the ERC721 token `GRAD`.
 {% endhint %}
 
-![](<../.gitbook/assets/image (8) (1) (1).png>)
+![](<../.gitbook/assets/image (8) (1) (1) (1).png>)
 
-![](<../.gitbook/assets/image (1) (1) (1) (1) (1).png>)
+![](<../.gitbook/assets/image (1) (1) (1) (1) (1) (1).png>)
 
 ## What’s next? <a href="#id-2883" id="id-2883"></a>
 

diff --git a/faq/products/vicissuer/README.md b/faq/products/vicissuer/README.md
@@ -40,9 +40,9 @@ Before issuing your token on Viction, make sure you are aware of the available t
 
 **Step 3:** Fill out the token information including Token Name, Token Symbol, Token Supply, Decimals, Token Type VRC20(deprecated) or VRC25, and whether or not it’s reissuable.
 
-* The symbol of the token contract is the symbol by which the token contract should be known, for example, “MYT”. It is broadly equivalent to a stock ticker and limited to 5 characters in length.
+* The symbol of the token contract is the symbol by which the token contract should be known, for example “VIC”. It is broadly equivalent to a stock ticker and limited to 5 characters in length.
 * Decimals refer to how divisible a token can be, from 0 (not at all divisible) to 18 (pretty much continuous) and even higher if required. Technically speaking, the decimal value is the number of digits that come after the decimal place when displaying token values on-screen.
-* Make sure to check out the differences between reissuable/ non-reissuable tokens, and VRC20(deprecated)/ VRC25 tokens by hovering on the information icon and clicking on the “Differences?” link.
+* Make sure to check out the differences between reissuable/ non-reissuable tokens, and VRC20(deprecated)/ VRC25 tokens by hovering on the information icon and clicking on the **Differences?** hyperlink.
 
 <figure><img src="../../../.gitbook/assets/Screenshot 2023-11-26 at 00.50.40.png" alt=""><figcaption></figcaption></figure>
 
@@ -52,7 +52,7 @@ Before issuing your token on Viction, make sure you are aware of the available t
 **Disclaimer:** The token issuance fee could vary depending on how much it costs to deploy the smart contract.
 {% endhint %}
 
-**Step 4:** VicIssuer will ask for the token’s information to confirm. Please check all the criteria carefully before clicking on the “Issue token” and wait for the contract to be deployed.
+**Step 4:** VicIssuer will ask for the token’s information to confirm. Please check all the criteria carefully before clicking on the **Issue token** and wait for the contract to be deployed.
 
 For VRC25 tokens, if you want to verify and publish the contract source code on VicScan, please copy the source code from the **Code review** section. You can refer to the guidance [here](how-to-verify-and-publish-contract-source-code-on-vicscan.md).
 
@@ -66,22 +66,58 @@ If you do not copy it at this stage, you will not be able to go back and copy it
 **Note:** Any developer with some experience developing and deploying smart contracts can refer to our reference implementation of the [Standards & Specification](https://docs.viction.xyz/developer-guide/standards-and-specification) to make customizations to the deployed token contract.
 {% endhint %}
 
-### **THE STEPS BELOW ARE FOR VRC25 TOKENS ONLY**
+**Step 5:** After successfully issuing the token, you can view the token details on the dashboard of VicIssuer.
 
-**Step 5:** A notification is received when the token is successfully issued. Click “View detail” to check the token’s summary including number of holders, transactions, etc. For VRC25 tokens, choose **Apply to pay fee by token** for VIC ZeroGas integration.
+<figure><img src="../../../.gitbook/assets/Screenshot 2024-09-20 at 13.15.40.png" alt=""><figcaption></figcaption></figure>
 
-**Step 6:** Once deployed, the issuer needs to agree that the fees for all transactions to the newly deployed token contract will be paid in terms of the issued token. Once the conditions are agreed upon, move to the next step by clicking “I understand”.
+## Apply Zero Gas Protocol <a href="#apply-zero-gas-protocol" id="apply-zero-gas-protocol"></a>
 
-**Step 7:** The token issuer needs to deposit a minimum amount of 10 VIC. The deposit can’t be withdrawn. The VIC held in the deposit pool will be deducted to pay the Masternodes for processing transactions.
+Your token is now ready for use, however **without ZeroGas registration**, you **CAN NOT** enable free gas for your transactions. Please note that you can only apply the ZeroGas Protocol for VRC25 tokens
 
-**Step 8:** Now the new VRC25 token can be used. Edit the transaction fee in the token itself. Change this number at any time during the operation period of the token.
+**Step 1:** On the Token Detail screen, click on the **Apply Zero Gas Protocol.**
 
-**Step 9:** In the token management dashboard, there are buttons to interact with the tokens, such as transfer and deposit more VIC to pay for subsequent transaction fees. Don’t forget to regularly check the balance of the VRC25 deposit because transactions will not be processed if the remaining deposit is not enough to pay the transaction fees.
+<figure><img src="../../../.gitbook/assets/image (3).png" alt=""><figcaption></figcaption></figure>
+
+**Step 2:** The Zero Gas introduction and conditions will appear; please read them carefully and click the **I Understand** button to proceed.
+
+<figure><img src="../../../.gitbook/assets/image (1).png" alt=""><figcaption></figcaption></figure>
+
+**Step 3:** The token issuer needs to deposit a minimum amount of 10 VIC. Click the **Submit** button to review.
+
+{% hint style="danger" %}
+The deposit can’t be withdrawn. The VIC held in the deposit pool will be deducted to pay the Masternodes for processing transactions.
+{% endhint %}
+
+<figure><img src="../../../.gitbook/assets/image (4).png" alt=""><figcaption></figcaption></figure>
+
+**Step 4:** On the Zero Gas Protocol Application screen, click on **Apply Zero Gas Protocol** to proceed.
+
+<figure><img src="../../../.gitbook/assets/image (5).png" alt=""><figcaption></figcaption></figure>
+
+**Step 5: Confirm** the transaction to proceed, a success message will be displayed once the token has been applied.
+
+<div>
+
+<figure><img src="../../../.gitbook/assets/image (6).png" alt="" width="563"><figcaption></figcaption></figure>
+
+
+
+<figure><img src="../../../.gitbook/assets/success.png" alt="" width="375"><figcaption></figcaption></figure>
+
+</div>
+
+**Step 6:** Click on Token Detail to be redirected to the list page, where you will see the VRC fee fund displayed along with the deposited amount.
+
+<figure><img src="../../../.gitbook/assets/image (7).png" alt=""><figcaption></figcaption></figure>
+
+{% hint style="warning" %}
+Don’t forget to regularly check the balance of the VRC25 deposit because transactions will not be processed if the remaining deposit is not enough to pay the transaction fees.
+{% endhint %}
 
 ### **DONATE VIC FOR VRC25 TRANSACTION FEES**
 
 If there are not enough VIC funds to pay for subsequent transaction fees, any token holders can deposit more VIC to the VicIssuer contract to continue making transactions.‌
 
-Go to the **“Donate VRC-25 fee”** tab from VicIssuer’s homepage. Enter the name of the token to donate VIC to, then enter the donation amount. Considering that the transaction fee in Viction is near zero, 1 VIC can power thousands of transactions.
+Go to the **Donate VRC-25 fee** tab from VicIssuer’s homepage. Enter the name of the token to donate VIC to, then enter the donation amount. Considering that the transaction fee in Viction is near zero, 1 VIC can power thousands of transactions.
 
-![](https://lh5.googleusercontent.com/PL-tz1-aPJlSOOaNlMBgj3He75quhYhHTv9DXzNAvlwlvfZ8iXD-XmznFiq7K5hFhtzqGP8GMBXcrvobrE8-MfNqtygA48BI7OnjY9DYY5v5Up1V9k0cd3QkkQfxTNG36VYWbdy3)
+<figure><img src="../../../.gitbook/assets/image.png" alt=""><figcaption></figcaption></figure>
diff --git a/...l/how-to-connect-to-viction-network/viction-wallet/user-guide/authentication.md b/...l/how-to-connect-to-viction-network/viction-wallet/user-guide/authentication.md
@@ -38,6 +38,6 @@ To increase security, you can lock the wallet when not in use, or the wallet wil
 
 **Step 2:** Input **Password**
 
-<figure><img src="../../../../.gitbook/assets/image (2) (1).png" alt="" width="375"><figcaption></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/image (2) (1) (1).png" alt="" width="375"><figcaption></figcaption></figure>
 
 **Step 3:** Click **Unlock Wallet** to access Viction
diff --git a/general/how-to-connect-to-viction-network/viction-wallet/user-guide/send-nft.md b/general/how-to-connect-to-viction-network/viction-wallet/user-guide/send-nft.md
@@ -6,11 +6,11 @@ Viction Wallet allows users to store, send, and receive non-fungible tokens (NFT
 
 **Step 1:** On the home screen, click the **NFTs tab**
 
-<figure><img src="../../../../.gitbook/assets/image (4) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/image (4) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 **Step 2:** Click on a NFT to see the NFT detail, then click **Send** to make a transaction
 
-<figure><img src="../../../../.gitbook/assets/image (5) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/image (5) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 **Step 3**: Input the recipient address in these ways:
 
@@ -20,12 +20,12 @@ Viction Wallet allows users to store, send, and receive non-fungible tokens (NFT
 
 → Then click **Review**
 
-<figure><img src="../../../../.gitbook/assets/image (6) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/image (6) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 **Step 4**: Click **Confirm** to confirm transaction
 
-<figure><img src="../../../../.gitbook/assets/image (7) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/image (7) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 After the transaction has been finalized, the sender will be redirected to a transaction details page, and the recipient will get a message that they have received the NFT.
 
-<figure><img src="../../../../.gitbook/assets/image (8) (1).png" alt="" width="360"><figcaption></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/image (8) (1) (1).png" alt="" width="360"><figcaption></figcaption></figure>
diff --git a/how-to/how-to-verify-if-a-contract-has-been-issued-via-vicissuer.md b/how-to/how-to-verify-if-a-contract-has-been-issued-via-vicissuer.md
@@ -2,6 +2,7 @@
 description: >-
   In this article, we will cover for how to verify the token contract had been
   issued by VICIssuer
+hidden: true
 ---
 
 # How to verify if a contract has been issued via VICIssuer