From 5f3bf0dd36ae6168089519cb97e0e9969b930c68 Mon Sep 17 00:00:00 2001 From: Dragos-Gabriel Danciulescu Date: Thu, 21 Nov 2024 17:55:26 +0200 Subject: [PATCH] Removed unnecessary setup section, duplicate --- source/mainnet/conf.py | 1 - .../sft-minting/build-smart-contract.rst | 4 ++-- .../mainnet/tutorials/sft-minting/index.rst | 1 - .../mainnet/tutorials/sft-minting/setup.rst | 24 ------------------- 4 files changed, 2 insertions(+), 28 deletions(-) delete mode 100644 source/mainnet/tutorials/sft-minting/setup.rst diff --git a/source/mainnet/conf.py b/source/mainnet/conf.py index d2eb91f6a7..c41b9a7d29 100644 --- a/source/mainnet/conf.py +++ b/source/mainnet/conf.py @@ -494,7 +494,6 @@ ".smart-contracts/tutorials/nft-minting/build-smart-contract": "tutorials/nft-minting/build-smart-contract.html", "./smart-contracts/tutorials/nft-minting/mint-xfer": "tutorials/nft-minting/mint-xfer.html", "./smart-contracts/tutorials/sft-minting/index": "tutorials/sft-minting/index.html", - "./smart-contracts/tutorials/sft-minting/setup": "tutorials/sft-minting/setup.html", "./smart-contracts/tutorials/sft-minting/build-smart-contract": "tutorials/sft-minting/build-smart-contract.html", "./smart-contracts/tutorials/sft-minting/mint-xfer": "tutorials/sft-minting/mint-xfer.html", "./smart-contracts/tutorials/fungible-tokens/index": "tutorials/fungible-tokens/index.html", diff --git a/source/mainnet/tutorials/sft-minting/build-smart-contract.rst b/source/mainnet/tutorials/sft-minting/build-smart-contract.rst index fa35152fa6..91899d4796 100644 --- a/source/mainnet/tutorials/sft-minting/build-smart-contract.rst +++ b/source/mainnet/tutorials/sft-minting/build-smart-contract.rst @@ -4,7 +4,7 @@ Smart contract modifications ============================ -In this tutorial, you will use the example ``cis2-nft`` contract template from Concordium, which you can initialize using the cargo-concordium tool via the ``cargo concordium init`` command. In this tutorial you will add a couple of things and update some functions to give more flexibility to the template. +In this tutorial, you will use the example ``cis2-multi`` contract template from Concordium, which can be found `here `_ for further reading. In this tutorial you will add a couple of things and update some functions to give more flexibility to the template. First, you will add a new struct called ``TokenMetadata``. It needs to implement the ``Serialize`` and ``SchemaType`` traits. For those who are familiar with the Ethereum ecosystem, it's similar to the ABI. @@ -57,7 +57,7 @@ When you have the ``TokenMetadata`` add one more line to the minting params stru tokens: collections::BTreeMap, } -Always remember, à blockchain itself is a state-keeping machine. If you send a transaction, you change the state. If you mint an NFT or transfer it, the state is changed again. Basically, if you make any change to the data structure, you change the state. So what is this state? Look at the code snippet below. +Always remember, a blockchain itself is a state-keeping machine. If you send a transaction, you change the state. If you mint an NFT or transfer it, the state is changed again. Basically, if you make any change to the data structure, you change the state. So what is this state? Look at the code snippet below. .. code-block:: rust diff --git a/source/mainnet/tutorials/sft-minting/index.rst b/source/mainnet/tutorials/sft-minting/index.rst index c47b2d2b83..cdf43a9649 100644 --- a/source/mainnet/tutorials/sft-minting/index.rst +++ b/source/mainnet/tutorials/sft-minting/index.rst @@ -25,6 +25,5 @@ One of the best use cases of semi-fungible tokens is in gaming and the metaverse :maxdepth: 1 :caption: Semi-fungible token minting - setup build-smart-contract mint-xfer diff --git a/source/mainnet/tutorials/sft-minting/setup.rst b/source/mainnet/tutorials/sft-minting/setup.rst deleted file mode 100644 index 65807e69e8..0000000000 --- a/source/mainnet/tutorials/sft-minting/setup.rst +++ /dev/null @@ -1,24 +0,0 @@ -.. include:: ../../variables.rst -.. _setup-sft-env: - -================================= -Setup the development environment -================================= - -If you have done the NFT minting tutorial, you will already have most of the necessary setup, including the |bw| and necessary tools for authoring smart contracts. Otherwise, see :ref:`Set up the development environment`. You need the following tools: - -- ``rustup``, including Wasm -- ``cargo concordium`` -- ``concordium client`` -- |bw| -- a Concordium node - -You will use `this smart contract `_ that is provided by Concordium team. - -You need to import the key export from |bw| in ``concordium client``. It will ask you to create a password for the output file. - -.. code-block:: console - - concordium-client config account import --name .json - -Once you have completed setup, :ref:`click here to continue to part 2 of this tutorial`.