From 585226c3c7978304cabe62dea0895958f4a18817 Mon Sep 17 00:00:00 2001 From: BiancaIalangi Date: Mon, 20 Oct 2025 21:52:28 +0300 Subject: [PATCH 1/7] update info - Smart contract interactions --- .../mxpy/smart-contract-interactions.md | 194 +++++++++--------- sidebars.js | 1 + 2 files changed, 102 insertions(+), 93 deletions(-) diff --git a/docs/sdk-and-tools/mxpy/smart-contract-interactions.md b/docs/sdk-and-tools/mxpy/smart-contract-interactions.md index 72caa058..f1687577 100644 --- a/docs/sdk-and-tools/mxpy/smart-contract-interactions.md +++ b/docs/sdk-and-tools/mxpy/smart-contract-interactions.md @@ -5,48 +5,50 @@ title: Smart contract interactions [comment]: # (mx-abstract) -Let's dive deeper into the Smart Contract interactions and what do you need to know when you need to interact with a SC. If you followed the previous mxpy related documentation, you should be able to set up your prerequisites like proxy URL, the chain ID and the PEM file. -For this, we need an interactions file. Usually, we find this file inside the contract's folder, in an **interaction** folder. The interactions file usually has a suggestive name, related to which chain the setup has been done. For example: **devnet.snippets.sh**. +Let's dive deeper into the Smart Contract interactions and what do you need to know when you need to interact with a SC. If you followed the [previous `mxpy`](/docs/sdk-and-tools/mxpy/mxpy-cli.md) related documentation, you should be able to set up your prerequisites like proxy URL, the chain ID and the PEM file. + +For this, we need a file inside the contract's folder, with a suggestive name. For example: **devnet.snippets.sh**. :::important -In order to be able to call methods from the interactions file, we need to assign the shell file as a source file in the terminal. We can do this by running the `source devnet.snippets.sh` command. Also, after each change to the interactions file structure, we need to repeat the source command. +In order to be able to call methods from the file, we need to assign the shell file as a source file in the terminal. We can do this by running the `source devnet.snippets.sh` command. Also, after each change to the interactions file, we need to repeat the source command. ::: Let's take the following example: -- We want to deploy a new SC on the Devnet -- We then need to upgrade the contract, to make it payable -- We call an endpoint without transferring any assets -- We make an ESDTTransfer, in order to call a payable endpoint -- We call a view function +1. We want to deploy a new SC on the Devnet. +2. We then need to upgrade the contract, to make it payable. +3. We call an endpoint without transferring any assets. +4. We make an `ESDTTransfer`, in order to call a payable endpoint. +5. We call a view function. [comment]: # (mx-context-auto) ## Prerequisites -[comment]: # (mx-context-auto) - -### mxpy - -We're going to use [**mxpy**](/sdk-and-tools/mxpy/mxpy-cli) to deploy the contract. Follow the installation guide [here](/sdk-and-tools/mxpy/installing-mxpy) - make sure to use the latest version available. - -[comment]: # (mx-context-auto) +:::important +Before starting this tutorial, make sure you have the following: -### Rust +- [`mxpy`](/sdk-and-tools/mxpy/mxpy-cli). Follow the [installation guide](/sdk-and-tools/mxpy/installing-mxpy) - make sure to use the latest version available. +- `stable` **Rust** version `≥ 1.85.0`. Follow the [installation guide](/docs/developers/toolchain-setup.md#installing-rust-and-sc-meta). +- `sc-meta` (install [multiversx-sc-meta](/docs/developers/meta/sc-meta-cli.md)) -Install **Rust** and [**sc-meta**](/developers/meta/sc-meta) as depicted [here](/docs/developers/toolchain-setup.md#installing-rust-and-sc-meta). They are required to build smart contracts. +::: -## Deploy & Upgrade +## Deploy -First things first. In order to deploy a new contract, we need to use **sc-meta** to build it, by invoking `sc-meta all build`. This will output the WASM bytecode, to be used within the interactions file: +First things first. In order to deploy a new contract, we need to use **sc-meta** to build it, in the contract root, by invoking `sc-meta all build`. This will output the WASM bytecode, to be used within the interactions file: -``` +```shell WASM_PATH="~/my-contract/output/my-contract.wasm" ``` -Now, in order to deploy the contract, we use the special **deploy** function of mxpy, that deploys the contract on the appointed chain, and runs the **init** function of the contract. +Now, in order to deploy the contract, we use the special **deploy** function of `mxpy`, that deploys the contract on the appointed chain, and runs the **init** function of the contract. + +```shell +WALLET_PEM="~/my-wallet/my-wallet.pem" +PROXY="https://devnet-gateway.multiversx.com" +CHAIN_ID="D" -``` deploySC() { mxpy --verbose contract deploy \ --bytecode=${WASM_PATH} \ @@ -56,17 +58,23 @@ deploySC() { --arguments $1 $2 \ --send || return } + +deploySC $1 $2 ``` -Now let's look at the structure of the interaction. It receives the path of the wasm file, where we previously built the contract. It also receives the path of the PEM file, the proxy url and the chain id, where the contract will be deployed. Another important parameter is the gas limit, where we state the maximum amount of gas we are willing to spend with this transaction. Each transaction cost depends on its complexity and the amount of data storage it handles. +Run in terminal the following command to deploy the smart contract on Devnet: + +```shell +source devnet.snippets.sh +``` -Another argument we must take a closer look at is **recall-nonce**. As we know, each account has its own nonce, that increases with each sent transaction. That being said, when calling an endpoint or a deploy function and so on, we must pass the next-in-line nonce, for the transaction to be correctly processed. And **recall-nonce** does just that. It gives us the correct nonce by querying the blockchain for the last one. +Now let's look at the structure of the interaction. It receives the path of the **wasm** file, where we previously built the contract. It also receives the path of the **wallet** (the PEM file), the **proxy URL** and the **chain ID**, where the contract will be deployed. Another important parameter is the **gas limit**, where we state the maximum amount of gas we are willing to spend with this transaction. Each transaction cost depends on its complexity and the amount of data storage it handles. Other than this, we also have the **arguments** keyword, that allows us to pass in the required parameters. As we previously said, deploying a smart contract means that we run the **init** function, which may or may not request some parameters. In our case, the **init** function has two different arguments, and we pass them when calling the **deploy** function. We'll come back later in this section at how we can pass parameters in function calls. -After the transaction is sent, mxpy will output information like the transaction hash, data and any other important information, based on the type of transaction. In case of a contract deployment, it will also output the newly deployed contract address. +After the transaction is sent, `mxpy` will output information like the transaction hash, data and any other important information, based on the type of transaction. In case of a contract deployment, it will also output the newly deployed contract address. -Let's now suppose we need to make the contract payable, in case it needs to receive funds. We could redeploy the contract but that will mean two different contracts, and not to mention that we will lose any existing storage. For that, we can use the **upgrade** command, that replaces the existing SC bytecode with the newly built contract version. +Let's now suppose we need to make the contract **payable**, in case it needs to receive funds. We could redeploy the contract but that will mean two different contracts, and not to mention that we will lose any existing storage. For that, we can use the **upgrade** command, that replaces the existing SC bytecode with the newly built contract version. :::caution It is import to handle data storage with caution when upgrading a smart contract. Data structure, especially for complex data types, must be preserved, otherwise the data may become corrupt. @@ -74,9 +82,11 @@ It is import to handle data storage with caution when upgrading a smart contract The upgrade function would look like this: -``` +```shell +CONTRACT_ADDRESS="erd1qqqqqqqqqqqqqpgqspymnxmfjve0vxhmep5vr3tf6sj8e80dd8ss2eyn3p" + upgradeSC() { - mxpy --verbose contract upgrade ${CONTRACT_ADDRESS} --payable \ + mxpy --verbose contract upgrade ${CONTRACT_ADDRESS} --metadata-payable \ --bytecode=${WASM_PATH} \ --pem=${WALLET_PEM} \ --gas-limit=60000000 \ @@ -84,32 +94,25 @@ upgradeSC() { --arguments $1 $2 \ --send || return } -``` -:::important -When we run the **upgrade** function, we once again call the **init** function of the SC. What this mean is that we must pass the function's parameters again, no matter if they changed or if they remained the same. -::: +upgradeSC $1 $2 +``` -Here we have 2 new different elements that we need to observe. First, we changed the **deploy** function with the **upgrade** function, which in turn requires the address of the previously deployed SC address, in order to be able to identify what SC to upgrade. Is important to note that this function can only be called by the SC's owner. The second element we need to observe is the **payable** keyword, which represents a code metadata flag that allows the SC to receive payments. - -:::tip -More information about Code Metadata can be found [here](/developers/data/code-metadata). -::: +Here we have 2 new different elements that we need to observe. First, we changed the **deploy** function with the **upgrade** function, which in turn requires the address of the previously deployed SC address, in order to be able to identify what SC to upgrade. Is important to note that this function can only be called by the SC's owner. The second element we need to observe is the **metadata-payable** keyword, which represents a [code metadata](/docs/developers/data/code-metadata.md) flag that allows the SC to receive payments. [comment]: # (mx-context-auto) ## Non payable endpoint interaction -Let's suppose we want to call the following endpoint, that receives an address and three different BigUint arguments, in this specific order. - -``` +Let's suppose we want to call the following endpoint, that receives an address and three different `BigUint` arguments, in this specific order. +```shell ###PARAMS #1 - FirstBigUintArgument #2 - SecondBigUintArgument - -ADDRESS_ARGUMENT="erd14nw9pukqyqu75gj0shm8upsegjft8l0awjefp877phfx74775dsq49swp3" THIRD_BIGUINT_ARGUMENT=0x0f4240 +ADDRESS_ARGUMENT=addr:erd14nw9pukqyqu75gj0shm8upsegjft8l0awjefp877phfx74775dsq49swp3 + myNonPayableEndpoint() { address_argument="0x$(mxpy wallet bech32 --decode ${ADDRESS_ARGUMENT})" mxpy --verbose contract call ${CONTRACT_ADDRESS} \ @@ -120,57 +123,59 @@ myNonPayableEndpoint() { --arguments $address_argument $1 $2 ${THIRD_BIGUINT_ARGUMENT}\ --send || return } + +myNonPayableEndpoint $1 $2 ``` -So, what happens in this interaction and how do we call it? Besides the function and arguments parts, the snippet is more or less the same as when deploying or upgrading a contract. When calling a non payable function, we need to provide the endpoint's name as the function argument. As for the arguments, they have to be in the same order as in the SC, including when calling an endpoint that has a variable number of arguments. Now, for the sake of example, we provided the arguments in multiple ways. It is up to each developer to choose the layout he prefers, but a few points need to be underlined: +So, what happens in this interaction and how do we call it? Besides the function and arguments parts, the snippet is more or less the same as when deploying or upgrading a contract. When calling a non payable function, we need to provide the endpoint's name as the function argument. As for the arguments, they have to be in the **same order** as in the SC, including when calling an endpoint that has a variable number of arguments. Now, for the sake of example, we provided the arguments in multiple ways. It is up to each developer to choose the layout he prefers, but a few points need to be underlined: -- Most of the supplied arguments need to be in the hex format (0x...). -- When converting a value to a hex format, we need to make sure it has an even number of characters. If not, we need to provide an extra 0 in order to make it even. (e.g. The number 911 -> In hex encoding, it is equal to: 38f -> So we need to provide the argument 0x038f). +- Most of the supplied **arguments** need to be in the **hex format**: `0x...`. +- When converting a value to a hex format, we need to make sure it has an **even number** of characters. If not, we need to provide an extra 0 in order to make it even. (e.g. The number 911 -> In hex encoding, it is equal to: 38f -> So we need to provide the argument 0x038f). - Arguments can be provided both as a fixed arguments (usually for unchangeable arguments like the contract's address or a fixed number) or can be provided as an input in the terminal, when interacting with the snippet (mostly used for arguments that change often like numbers). -In our example we provide the address argument as a fixed argument. We then convert it to hex format (as it is in the bech32 format by default) and only after that we pass it as a parameter. As for the BigUint parameters, we provide the first two parameters directly in the terminal and the last one as a fixed argument, hex encoded. +In our example we provide the address argument as a fixed argument. We then convert it to hex format (as it is in the bech32 format by default) and only after that we pass it as a parameter. As for the `BigUint` parameters, we provide the first two parameters directly in the terminal and the last one as a fixed argument, hex encoded. :::tip -mxpy facilitates us with some encoding conventions, including: +`mxpy` facilitates us with some encoding conventions, including: -- We can use **str:** for encoding strings. For example: str:MYTOKEN-123456 -- Blockchain addresses that start with **erd1** are automatically encoded, so there is no need to further hex encode them -- The values **true** or **false** are automatically converted to **boolean** values -- Values that are identified as **numbers** are hex encoded by default -- Arguments like **0x...** are left unchanged, as they are interpreted as already encoded hex values +- We can use **str:** for encoding strings. For example: `str:MYTOKEN-123456`. +- Blockchain addresses that start with **erd1** are automatically encoded, so there is no need to further hex encode them. +- The values **true** or **false** are automatically converted to **boolean** values. +- Values that are identified as **numbers** are hex encoded by default. +- Arguments like `0x...` are left unchanged, as they are interpreted as already encoded hex values. - ::: +::: So, in case of our **myNonPayableEndpoint** interaction, we can write it like so: -``` +```shell ###PARAMS #1 - FirstBigUintArgument #2 - SecondBigUintArgument - -ADDRESS_ARGUMENT="erd14nw9pukqyqu75gj0shm8upsegjft8l0awjefp877phfx74775dsq49swp3" THIRD_BIGUINT_ARGUMENT=1000000 +ADDRESS_ARGUMENT=addr:erd14nw9pukqyqu75gj0shm8upsegjft8l0awjefp877phfx74775dsq49swp3 + myNonPayableEndpoint() { mxpy --verbose contract call ${CONTRACT_ADDRESS} \ --pem=${WALLET_PEM} \ --gas-limit=6000000 \ --proxy=${PROXY} --chain=${CHAIN_ID} \ --function="myNonPayableEndpoint" \ - --arguments $address_argument $1 $2 ${THIRD_BIGUINT_ARGUMENT}\ + --arguments ${ADDRESS_ARGUMENT} $1 $2 ${THIRD_BIGUINT_ARGUMENT}\ --send || return } ``` A call example for this endpoint would look like: -``` +```shell myNonPayableEndpoint 10000 100000 ``` -This would translate in (using unencoded values for easier reading): +Using unencoded values (for easier reading) would translate into: -``` +```shell myNonPayableEndpoint erd14nw9pukqyqu75gj0shm8upsegjft8l0awjefp877phfx74775dsq49swp3 10000 100000 1000000 ``` @@ -188,7 +193,7 @@ It is import to make sure all arguments have the correct encoding. Otherwise, th Now let's take a look at the following example, where we want to call a payable endpoint. -``` +```shell myPayableEndpoint() { method_name=str:myPayableEndpoint my_token=str:$1 @@ -203,7 +208,7 @@ myPayableEndpoint() { } ``` -As we can see, the way we call a payable endpoint is by calling an ESDTTransfer function (or any other function that transfer assets and supports contract calls) and providing the name of the method as an argument. The order of the arguments differs for each transfer function. In our case, we specify in the terminal the token type and the amount of tokens we want to transfer and then we provide as a fixed input what SC function we want to call. +As we can see, the way we call a **payable endpoint** is by calling an `ESDTTransfer` function (or any other function that transfer assets and supports contract calls) and providing the name of the method as an argument. The order of the arguments differs for each transfer function. In our case, we specify in the terminal the **token type** and **the amount of tokens** we want to transfer and then we provide as a **fixed input** what SC function we want to call. [comment]: # (mx-context-auto) @@ -211,7 +216,8 @@ As we can see, the way we call a payable endpoint is by calling an ESDTTransfer Now let's suppose we want to call an endpoint that accepts an NFT or an SFT as payment. -``` +```shell +###PARAMS # $1 = NFT/SFT Token Identifier, # $2 = NFT/SFT Token Nonce, # $3 = NFT/SFT Token Amount, @@ -219,30 +225,31 @@ Now let's suppose we want to call an endpoint that accepts an NFT or an SFT as p FIRST_BIGUINT_ARGUMENT=1000 SECOND_BIGUINT_ARGUMENT=10000 +MY_WALLET_ADDRESS=erd1... + myESDTNFTPayableEndpoint() { - user_address="$(mxpy wallet pem-address $WALLET_PEM)" method_name=str:myESDTNFTPayableEndpoint sft_token=str:$1 sft_token_nonce=$2 sft_token_amount=$3 - destination_address=$4 - mxpy --verbose contract call $user_address \ + destination_address=addr:$4 + mxpy --verbose contract call ${MY_WALLET_ADDRESS} \ --pem=${WALLET_PEM} \ --gas-limit=100000000 \ --proxy=${PROXY} --chain=${CHAIN_ID} \ --function="ESDTNFTTransfer" \ - --arguments $sft_token - $sft_token_nonce - $sft_token_amount - $destination_address - $method_name - ${FIRST_BIGUINT_ARGUMENT} + --arguments $sft_token \ + $sft_token_nonce \ + $sft_token_amount \ + $destination_address \ + $method_name \ + ${FIRST_BIGUINT_ARGUMENT} \ ${SECOND_BIGUINT_ARGUMENT} \ --send || return } ``` -First of all, to call this type of transfer function we need to pass the receiver address the same as the sender address. So in this example we convert the caller's address based on the indicated PEM file. Now, like in the case of `ESDTTransfer`, the name of the called function is `ESDTNFTTransfer`. All the other required data is passed as arguments (including the destination contract's address and the endpoint). In case of this single NFT/SFT transfer, we first pass the token (identifier, nonce and amount) and then we pass the destination address and the name of the endpoint. In the end we pass whatever parameters the indicated method needs. +First of all, to call this type of transfer function we need to pass the receiver address the same as the sender address. So in this example, `MY_WALLET_ADDRESS` is the caller's address of the PEM wallet used. Now, like in the case of `ESDTTransfer`, the name of the called function is `ESDTNFTTransfer`. All the other required data is passed as arguments (including the destination contract's address and the endpoint). In case of this single NFT/SFT transfer, we first pass the **token** (identifier, nonce and amount) and then we pass the **destination address** and the **name of the endpoint**. In the end we pass whatever parameters the indicated method needs. [comment]: # (mx-context-auto) @@ -250,7 +257,7 @@ First of all, to call this type of transfer function we need to pass the receive In case we need to call an endpoint that accepts multiple tokens (let's say for example 2 fungible tokens and an NFT). Let's take a look at the following example: -``` +```shell ###PARAMS # $1 = Destination Address, @@ -265,9 +272,8 @@ In case we need to call an endpoint that accepts multiple tokens (let's say for FIRST_BIGUINT_ARGUMENT=1000 SECOND_BIGUINT_ARGUMENT=10000 myMultiESDTNFTPayableEndpoint() { - user_address="$(mxpy wallet pem-address $WALLET_PEM)" method_name=str:myMultiESDTPayableEndpoint - destination_address=$1 + destination_address=addr:$1 number_of_tokens=3 first_token=str:$2 first_token_nonce=0 @@ -284,25 +290,27 @@ myMultiESDTNFTPayableEndpoint() { --gas-limit=100000000 \ --proxy=${PROXY} --chain=${CHAIN_ID} \ --function="MultiESDTNFTTransfer" \ - --arguments $destination_address - $number_of_tokens - $first_token - $first_token_nonce - $first_token_amount - $second_token - $second_token_nonce - $second_token_amount - $third_token - $third_token_nonce - $third_token_amount - $method_name - ${FIRST_BIGUINT_ARGUMENT} + --arguments $destination_address \ + $number_of_tokens \ + $first_token \ + $first_token_nonce \ + $first_token_amount \ + $second_token \ + $second_token_nonce \ + $second_token_amount \ + $third_token \ + $third_token_nonce \ + $third_token_amount \ + $method_name \ + ${FIRST_BIGUINT_ARGUMENT} \ ${SECOND_BIGUINT_ARGUMENT} \ --send || return } ``` -In this example, we call `myMultiESDTPayableEndpoint` endpoint, by transferring 3 different tokens (the first two are fungible tokens and the last one is an NFT). The endpoint takes 2 BigUInt arguments. The layout of the snippet is almost the same as with **ESDTNFTTransfer** (including the fact that the sender is the same as the receiver) but has different arguments. We now pass the destination address first and the number of ESDT/NFT tokens that we want to sent. Then, for each sent token, we specify the identifier, the nonce (in our example 0 for the fungible tokens and a specific value for the NFT) and the amount. In the end, like with the **ESDTTransfer**, we pass the name of the method we want to call and the rest of the parameters of that specific method. +In this example, we call `myMultiESDTPayableEndpoint` endpoint, by transferring **3 different tokens**: the first two are fungible tokens and the last one is an NFT. + +The endpoint takes 2 BigUInt arguments. The layout of the snippet is almost the same as with **ESDTNFTTransfer** (including the fact that the sender is the same as the receiver) but has different arguments. We now pass the destination address first and the number of ESDT/NFT tokens that we want to sent. Then, for each sent token, we specify the identifier, the nonce (in our example 0 for the fungible tokens and a specific value for the NFT) and the amount. In the end, like with the **ESDTTransfer**, we pass the name of the method we want to call and the rest of the parameters of that specific method. :::tip More information about ESDT Transfers [here](/tokens/fungible-tokens/#transfers). @@ -314,7 +322,7 @@ More information about ESDT Transfers [here](/tokens/fungible-tokens/#transfers) In case we want to call a view function, we can use the **query** keyword. -``` +```shell ###PARAMS #1 - First argument @@ -322,9 +330,9 @@ In case we want to call a view function, we can use the **query** keyword. myView() { mxpy --verbose contract query ${CONTRACT_ADDRESS} \ --proxy=${PROXY} \ - --function="myView" + --function="myView" \ --arguments $1 $2 } ``` -When calling a view function, mxpy will output the standard information in the terminal, along with the results, formatted based on the requested data type. The arguments are specified in the same way as with endpoints. +When calling a **view** function, `mxpy` will output the standard information in the terminal, along with the results, formatted based on the requested data type. The arguments are specified in the same way as with endpoints. diff --git a/sidebars.js b/sidebars.js index 7fb5b32c..8d343db0 100644 --- a/sidebars.js +++ b/sidebars.js @@ -202,6 +202,7 @@ const sidebars = { items: [ "sdk-and-tools/mxpy/installing-mxpy", "sdk-and-tools/mxpy/mxpy-cli", + "sdk-and-tools/mxpy/smart-contract-interactions", ], }, { From c27745766d342bd340a42a903c7667744cb7bd0c Mon Sep 17 00:00:00 2001 From: BiancaIalangi Date: Wed, 22 Oct 2025 12:40:12 +0300 Subject: [PATCH 2/7] final touch - Smart contract interactions --- .../mxpy/smart-contract-interactions.md | 95 +++++++++++-------- 1 file changed, 58 insertions(+), 37 deletions(-) diff --git a/docs/sdk-and-tools/mxpy/smart-contract-interactions.md b/docs/sdk-and-tools/mxpy/smart-contract-interactions.md index f1687577..da7e364f 100644 --- a/docs/sdk-and-tools/mxpy/smart-contract-interactions.md +++ b/docs/sdk-and-tools/mxpy/smart-contract-interactions.md @@ -5,12 +5,18 @@ title: Smart contract interactions [comment]: # (mx-abstract) -Let's dive deeper into the Smart Contract interactions and what do you need to know when you need to interact with a SC. If you followed the [previous `mxpy`](/docs/sdk-and-tools/mxpy/mxpy-cli.md) related documentation, you should be able to set up your prerequisites like proxy URL, the chain ID and the PEM file. +Let's dive deeper into smart contract interactions and what you need to know to interact with a contract. If you followed the [previous `mxpy`](/docs/sdk-and-tools/mxpy/mxpy-cli.md) related documentation, you should be able to set up your prerequisites like proxy URL, the chain ID and the PEM file. -For this, we need a file inside the contract's folder, with a suggestive name. For example: **devnet.snippets.sh**. +For this, we need a file inside the contract's folder, with a suggestive name. For example: `devnet.snippets.sh`. :::important -In order to be able to call methods from the file, we need to assign the shell file as a source file in the terminal. We can do this by running the `source devnet.snippets.sh` command. Also, after each change to the interactions file, we need to repeat the source command. +In order to be able to call methods from the file, we need to assign the shell file as a source file in the terminal. We can do this by running the next command: + +```shell +source devnet.snippets.sh +``` + +After each change to the interactions file, we need to repeat the source command. ::: Let's take the following example: @@ -25,18 +31,23 @@ Let's take the following example: ## Prerequisites -:::important Before starting this tutorial, make sure you have the following: - [`mxpy`](/sdk-and-tools/mxpy/mxpy-cli). Follow the [installation guide](/sdk-and-tools/mxpy/installing-mxpy) - make sure to use the latest version available. -- `stable` **Rust** version `≥ 1.85.0`. Follow the [installation guide](/docs/developers/toolchain-setup.md#installing-rust-and-sc-meta). -- `sc-meta` (install [multiversx-sc-meta](/docs/developers/meta/sc-meta-cli.md)) +- `stable` **Rust** version `≥ 1.83.0`. Follow the [installation guide](/docs/developers/toolchain-setup.md#installing-rust-and-sc-meta). +- `sc-meta` (install [multiversx-sc-meta](/docs/developers/meta/sc-meta-cli.md)). -::: +[comment]: # (mx-context-auto) ## Deploy -First things first. In order to deploy a new contract, we need to use **sc-meta** to build it, in the contract root, by invoking `sc-meta all build`. This will output the WASM bytecode, to be used within the interactions file: +First things first. In order to deploy a new contract, we need to use `sc-meta` to build it, in the contract root, by invoking the next command: + +```shell +sc-meta all build +``` + +This will output the WASM bytecode, to be used within the interactions file: ```shell WASM_PATH="~/my-contract/output/my-contract.wasm" @@ -58,21 +69,24 @@ deploySC() { --arguments $1 $2 \ --send || return } - -deploySC $1 $2 ``` -Run in terminal the following command to deploy the smart contract on Devnet: +Run in terminal the following command to deploy the smart contract on Devnet. Replace `arg1` and `arg2` with your desired deployment values. ```shell source devnet.snippets.sh +deploySC arg1 arg2 ``` -Now let's look at the structure of the interaction. It receives the path of the **wasm** file, where we previously built the contract. It also receives the path of the **wallet** (the PEM file), the **proxy URL** and the **chain ID**, where the contract will be deployed. Another important parameter is the **gas limit**, where we state the maximum amount of gas we are willing to spend with this transaction. Each transaction cost depends on its complexity and the amount of data storage it handles. +Now let's look at the structure of the interaction. It receives the path of the **wasm file**, where we previously built the contract. It also receives the path of the **wallet** (the PEM file), the **proxy URL** and the **chain ID**, where the contract will be deployed. Another important parameter is the **gas limit**, where we state the maximum amount of gas we are willing to spend with this transaction. Each transaction cost depends on its complexity and the amount of data storage it handles. Other than this, we also have the **arguments** keyword, that allows us to pass in the required parameters. As we previously said, deploying a smart contract means that we run the **init** function, which may or may not request some parameters. In our case, the **init** function has two different arguments, and we pass them when calling the **deploy** function. We'll come back later in this section at how we can pass parameters in function calls. -After the transaction is sent, `mxpy` will output information like the transaction hash, data and any other important information, based on the type of transaction. In case of a contract deployment, it will also output the newly deployed contract address. +After the transaction is sent, `mxpy` will output information like the **transaction hash**, **data** and any other important information, based on the type of transaction. In case of a contract deployment, it will also output the newly deployed contract address. + +[comment]: # (mx-context-auto) + +## Upgrade Let's now suppose we need to make the contract **payable**, in case it needs to receive funds. We could redeploy the contract but that will mean two different contracts, and not to mention that we will lose any existing storage. For that, we can use the **upgrade** command, that replaces the existing SC bytecode with the newly built contract version. @@ -94,11 +108,12 @@ upgradeSC() { --arguments $1 $2 \ --send || return } - -upgradeSC $1 $2 ``` -Here we have 2 new different elements that we need to observe. First, we changed the **deploy** function with the **upgrade** function, which in turn requires the address of the previously deployed SC address, in order to be able to identify what SC to upgrade. Is important to note that this function can only be called by the SC's owner. The second element we need to observe is the **metadata-payable** keyword, which represents a [code metadata](/docs/developers/data/code-metadata.md) flag that allows the SC to receive payments. +Here we have 2 new different elements that we need to observe: + +1. We changed the **deploy** function with the **upgrade** function. This new function requires the address of the previously deployed smart contract so the system can identify which contract to update. It is important to note that this function can only be called by the smart contract's owner. +2. The **metadata-payable** keyword, which represents a [code metadata](/docs/developers/data/code-metadata.md) flag that allows the smart contract to receive payments. [comment]: # (mx-context-auto) @@ -108,8 +123,8 @@ Let's suppose we want to call the following endpoint, that receives an address a ```shell ###PARAMS -#1 - FirstBigUintArgument -#2 - SecondBigUintArgument +# $1 = FirstBigUintArgument +# $2 = SecondBigUintArgument THIRD_BIGUINT_ARGUMENT=0x0f4240 ADDRESS_ARGUMENT=addr:erd14nw9pukqyqu75gj0shm8upsegjft8l0awjefp877phfx74775dsq49swp3 @@ -123,23 +138,26 @@ myNonPayableEndpoint() { --arguments $address_argument $1 $2 ${THIRD_BIGUINT_ARGUMENT}\ --send || return } - -myNonPayableEndpoint $1 $2 ``` -So, what happens in this interaction and how do we call it? Besides the function and arguments parts, the snippet is more or less the same as when deploying or upgrading a contract. When calling a non payable function, we need to provide the endpoint's name as the function argument. As for the arguments, they have to be in the **same order** as in the SC, including when calling an endpoint that has a variable number of arguments. Now, for the sake of example, we provided the arguments in multiple ways. It is up to each developer to choose the layout he prefers, but a few points need to be underlined: +So, what happens in this interaction and how do we call it? -- Most of the supplied **arguments** need to be in the **hex format**: `0x...`. -- When converting a value to a hex format, we need to make sure it has an **even number** of characters. If not, we need to provide an extra 0 in order to make it even. (e.g. The number 911 -> In hex encoding, it is equal to: 38f -> So we need to provide the argument 0x038f). +Besides the function and arguments parts, the snippet is more or less the same as when deploying or upgrading a contract. When calling a non payable function, we need to provide the endpoint's name as the function argument. As for the arguments, they have to be in the **same order** as in the smart contract, including when calling an endpoint that has a variable number of arguments. Now, for the sake of example, we provided the arguments in multiple ways. + +It is up to each developer to choose the layout he prefers, but a few points need to be underlined: + +- Most of the supplied **arguments** need to be in the **hexadecimal format**: `0x...`. +- When converting a value to a hexadecimal format, we need to make sure it has an **even number** of characters. If not, we need to provide an extra `0` in order to make it even: + - Example: the number `911` -> in hexadecimal encoding, it is equal to: `38f` -> so we need to provide the argument `0x038f`. - Arguments can be provided both as a fixed arguments (usually for unchangeable arguments like the contract's address or a fixed number) or can be provided as an input in the terminal, when interacting with the snippet (mostly used for arguments that change often like numbers). -In our example we provide the address argument as a fixed argument. We then convert it to hex format (as it is in the bech32 format by default) and only after that we pass it as a parameter. As for the `BigUint` parameters, we provide the first two parameters directly in the terminal and the last one as a fixed argument, hex encoded. +In our example we provide the address argument as a fixed argument. We then convert it to hexadecimal format (as it is in the bech32 format by default) and only after that we pass it as a parameter. As for the `BigUint` parameters, we provide the first two parameters directly in the terminal and the last one as a fixed argument, hexadecimal encoded. :::tip `mxpy` facilitates us with some encoding conventions, including: -- We can use **str:** for encoding strings. For example: `str:MYTOKEN-123456`. -- Blockchain addresses that start with **erd1** are automatically encoded, so there is no need to further hex encode them. +- We can use `str:` for encoding strings. For example: `str:MYTOKEN-123456`. +- Blockchain addresses that start with `erd1` are automatically encoded, so there is no need to further hex encode them. - The values **true** or **false** are automatically converted to **boolean** values. - Values that are identified as **numbers** are hex encoded by default. - Arguments like `0x...` are left unchanged, as they are interpreted as already encoded hex values. @@ -149,10 +167,9 @@ In our example we provide the address argument as a fixed argument. We then conv So, in case of our **myNonPayableEndpoint** interaction, we can write it like so: ```shell - ###PARAMS -#1 - FirstBigUintArgument -#2 - SecondBigUintArgument +# $1 = FirstBigUintArgument +# $2 = SecondBigUintArgument THIRD_BIGUINT_ARGUMENT=1000000 ADDRESS_ARGUMENT=addr:erd14nw9pukqyqu75gj0shm8upsegjft8l0awjefp877phfx74775dsq49swp3 @@ -170,6 +187,7 @@ myNonPayableEndpoint() { A call example for this endpoint would look like: ```shell +source devnet.snippets.sh myNonPayableEndpoint 10000 100000 ``` @@ -208,7 +226,7 @@ myPayableEndpoint() { } ``` -As we can see, the way we call a **payable endpoint** is by calling an `ESDTTransfer` function (or any other function that transfer assets and supports contract calls) and providing the name of the method as an argument. The order of the arguments differs for each transfer function. In our case, we specify in the terminal the **token type** and **the amount of tokens** we want to transfer and then we provide as a **fixed input** what SC function we want to call. +As we can see, the way we call a **payable endpoint** is by calling an `ESDTTransfer` function (or any other function that transfer assets and supports contract calls) and providing the name of the method as an argument. The order of the arguments differs for each transfer function. In our case, we specify in the terminal the **token type** and **the amount of tokens** we want to transfer and then we provide as a **fixed input** what smart contract endpoint we want to call. [comment]: # (mx-context-auto) @@ -222,7 +240,6 @@ Now let's suppose we want to call an endpoint that accepts an NFT or an SFT as p # $2 = NFT/SFT Token Nonce, # $3 = NFT/SFT Token Amount, # $4 = Destination Address, - FIRST_BIGUINT_ARGUMENT=1000 SECOND_BIGUINT_ARGUMENT=10000 MY_WALLET_ADDRESS=erd1... @@ -249,7 +266,11 @@ myESDTNFTPayableEndpoint() { } ``` -First of all, to call this type of transfer function we need to pass the receiver address the same as the sender address. So in this example, `MY_WALLET_ADDRESS` is the caller's address of the PEM wallet used. Now, like in the case of `ESDTTransfer`, the name of the called function is `ESDTNFTTransfer`. All the other required data is passed as arguments (including the destination contract's address and the endpoint). In case of this single NFT/SFT transfer, we first pass the **token** (identifier, nonce and amount) and then we pass the **destination address** and the **name of the endpoint**. In the end we pass whatever parameters the indicated method needs. +First of all, to call this type of transfer function we need to pass the receiver address the same as the sender address. So in this example, `MY_WALLET_ADDRESS` is the caller's address of the PEM wallet used. + +Now, like in the case of `ESDTTransfer`, the name of the called function is `ESDTNFTTransfer`. All the other required data is passed as arguments (including the destination contract's address and the endpoint). + +In case of this single NFT/SFT transfer, we first pass the **token** (identifier, nonce and amount) and then we pass the **destination address** and the **name of the endpoint**. In the end we pass whatever parameters the indicated method needs. [comment]: # (mx-context-auto) @@ -268,9 +289,9 @@ In case we need to call an endpoint that accepts multiple tokens (let's say for # $6 = Third Token Identifier, # $7 = Third Token Nonce, # $8 = Third Token Identifier, - FIRST_BIGUINT_ARGUMENT=1000 SECOND_BIGUINT_ARGUMENT=10000 + myMultiESDTNFTPayableEndpoint() { method_name=str:myMultiESDTPayableEndpoint destination_address=addr:$1 @@ -310,7 +331,7 @@ myMultiESDTNFTPayableEndpoint() { In this example, we call `myMultiESDTPayableEndpoint` endpoint, by transferring **3 different tokens**: the first two are fungible tokens and the last one is an NFT. -The endpoint takes 2 BigUInt arguments. The layout of the snippet is almost the same as with **ESDTNFTTransfer** (including the fact that the sender is the same as the receiver) but has different arguments. We now pass the destination address first and the number of ESDT/NFT tokens that we want to sent. Then, for each sent token, we specify the identifier, the nonce (in our example 0 for the fungible tokens and a specific value for the NFT) and the amount. In the end, like with the **ESDTTransfer**, we pass the name of the method we want to call and the rest of the parameters of that specific method. +The endpoint takes 2 BigUInt arguments. The layout of the snippet is almost the same as with `ESDTNFTTransfer` (including the fact that the sender is the same as the receiver) but has different arguments. We now pass the destination address first and the number of ESDT/NFT tokens that we want to sent. Then, for each sent token, we specify the identifier, the nonce (in our example 0 for the fungible tokens and a specific value for the NFT) and the amount. In the end, like with the `ESDTTransfer`, we pass the name of the method we want to call and the rest of the parameters of that specific method. :::tip More information about ESDT Transfers [here](/tokens/fungible-tokens/#transfers). @@ -323,10 +344,10 @@ More information about ESDT Transfers [here](/tokens/fungible-tokens/#transfers) In case we want to call a view function, we can use the **query** keyword. ```shell - ###PARAMS -#1 - First argument -#2 - Second argument +# $1 = First argument +# $2 = Second argument + myView() { mxpy --verbose contract query ${CONTRACT_ADDRESS} \ --proxy=${PROXY} \ From b3a82cb1685610875ece95dd5ec2993941732bd0 Mon Sep 17 00:00:00 2001 From: BiancaIalangi Date: Wed, 22 Oct 2025 12:41:39 +0300 Subject: [PATCH 3/7] remove abreviation --- docs/sdk-and-tools/mxpy/smart-contract-interactions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/sdk-and-tools/mxpy/smart-contract-interactions.md b/docs/sdk-and-tools/mxpy/smart-contract-interactions.md index da7e364f..70611f78 100644 --- a/docs/sdk-and-tools/mxpy/smart-contract-interactions.md +++ b/docs/sdk-and-tools/mxpy/smart-contract-interactions.md @@ -21,7 +21,7 @@ After each change to the interactions file, we need to repeat the source command Let's take the following example: -1. We want to deploy a new SC on the Devnet. +1. We want to deploy a new smart contract on the Devnet. 2. We then need to upgrade the contract, to make it payable. 3. We call an endpoint without transferring any assets. 4. We make an `ESDTTransfer`, in order to call a payable endpoint. @@ -88,7 +88,7 @@ After the transaction is sent, `mxpy` will output information like the **transac ## Upgrade -Let's now suppose we need to make the contract **payable**, in case it needs to receive funds. We could redeploy the contract but that will mean two different contracts, and not to mention that we will lose any existing storage. For that, we can use the **upgrade** command, that replaces the existing SC bytecode with the newly built contract version. +Let's now suppose we need to make the contract **payable**, in case it needs to receive funds. We could redeploy the contract but that will mean two different contracts, and not to mention that we will lose any existing storage. For that, we can use the **upgrade** command, that replaces the existing smart contract bytecode with the newly built contract version. :::caution It is import to handle data storage with caution when upgrading a smart contract. Data structure, especially for complex data types, must be preserved, otherwise the data may become corrupt. From cd20fc60f73aefd0ce2cf507de74284bee105541 Mon Sep 17 00:00:00 2001 From: BiancaIalangi Date: Tue, 28 Oct 2025 13:02:03 +0200 Subject: [PATCH 4/7] apply reviews --- .../mxpy/smart-contract-interactions.md | 157 +++++++----------- 1 file changed, 61 insertions(+), 96 deletions(-) diff --git a/docs/sdk-and-tools/mxpy/smart-contract-interactions.md b/docs/sdk-and-tools/mxpy/smart-contract-interactions.md index 70611f78..8670b6c5 100644 --- a/docs/sdk-and-tools/mxpy/smart-contract-interactions.md +++ b/docs/sdk-and-tools/mxpy/smart-contract-interactions.md @@ -21,11 +21,11 @@ After each change to the interactions file, we need to repeat the source command Let's take the following example: -1. We want to deploy a new smart contract on the Devnet. -2. We then need to upgrade the contract, to make it payable. -3. We call an endpoint without transferring any assets. -4. We make an `ESDTTransfer`, in order to call a payable endpoint. -5. We call a view function. +1. We want to **deploy** a new smart contract on the Devnet. +2. We then need to **upgrade** the contract, to make it payable. +3. We **call** an endpoint without transferring any assets. +4. We **transfer** ESDT, in order to call a payable endpoint. +5. We call a **view** function. [comment]: # (mx-context-auto) @@ -35,7 +35,7 @@ Before starting this tutorial, make sure you have the following: - [`mxpy`](/sdk-and-tools/mxpy/mxpy-cli). Follow the [installation guide](/sdk-and-tools/mxpy/installing-mxpy) - make sure to use the latest version available. - `stable` **Rust** version `≥ 1.83.0`. Follow the [installation guide](/docs/developers/toolchain-setup.md#installing-rust-and-sc-meta). -- `sc-meta` (install [multiversx-sc-meta](/docs/developers/meta/sc-meta-cli.md)). +- `sc-meta`. Follow the [installation guide](/docs/developers/toolchain-setup.md#installing-rust-and-sc-meta). [comment]: # (mx-context-auto) @@ -58,14 +58,12 @@ Now, in order to deploy the contract, we use the special **deploy** function of ```shell WALLET_PEM="~/my-wallet/my-wallet.pem" PROXY="https://devnet-gateway.multiversx.com" -CHAIN_ID="D" deploySC() { mxpy --verbose contract deploy \ --bytecode=${WASM_PATH} \ --pem=${WALLET_PEM} \ - --gas-limit=60000000 \ - --proxy=${PROXY} --chain=${CHAIN_ID} \ + --proxy=${PROXY} \ --arguments $1 $2 \ --send || return } @@ -78,11 +76,11 @@ source devnet.snippets.sh deploySC arg1 arg2 ``` -Now let's look at the structure of the interaction. It receives the path of the **wasm file**, where we previously built the contract. It also receives the path of the **wallet** (the PEM file), the **proxy URL** and the **chain ID**, where the contract will be deployed. Another important parameter is the **gas limit**, where we state the maximum amount of gas we are willing to spend with this transaction. Each transaction cost depends on its complexity and the amount of data storage it handles. +Now let's look at the structure of the interaction. It receives the path of the **wasm file**, where we previously built the contract. It also receives the path of the **wallet** (the PEM file) and the **proxy URL** where the contract will be deployed. Other than this, we also have the **arguments** keyword, that allows us to pass in the required parameters. As we previously said, deploying a smart contract means that we run the **init** function, which may or may not request some parameters. In our case, the **init** function has two different arguments, and we pass them when calling the **deploy** function. We'll come back later in this section at how we can pass parameters in function calls. -After the transaction is sent, `mxpy` will output information like the **transaction hash**, **data** and any other important information, based on the type of transaction. In case of a contract deployment, it will also output the newly deployed contract address. +After the transaction is sent, `mxpy` will output information like the **transaction hash**, **data** and any other important information, based on the type of transaction. In case of a contract deployment, it will also output the **newly deployed contract address**. [comment]: # (mx-context-auto) @@ -103,13 +101,14 @@ upgradeSC() { mxpy --verbose contract upgrade ${CONTRACT_ADDRESS} --metadata-payable \ --bytecode=${WASM_PATH} \ --pem=${WALLET_PEM} \ - --gas-limit=60000000 \ - --proxy=${PROXY} --chain=${CHAIN_ID} \ + --proxy=${PROXY} \ --arguments $1 $2 \ --send || return } ``` +`CONTRACT_ADDRESS` is a placeholder value which value needs to be replaced with the address previously generated in the deploy action. + Here we have 2 new different elements that we need to observe: 1. We changed the **deploy** function with the **upgrade** function. This new function requires the address of the previously deployed smart contract so the system can identify which contract to update. It is important to note that this function can only be called by the smart contract's owner. @@ -126,14 +125,13 @@ Let's suppose we want to call the following endpoint, that receives an address a # $1 = FirstBigUintArgument # $2 = SecondBigUintArgument THIRD_BIGUINT_ARGUMENT=0x0f4240 -ADDRESS_ARGUMENT=addr:erd14nw9pukqyqu75gj0shm8upsegjft8l0awjefp877phfx74775dsq49swp3 +ADDRESS_ARGUMENT=erd14nw9pukqyqu75gj0shm8upsegjft8l0awjefp877phfx74775dsq49swp3 myNonPayableEndpoint() { address_argument="0x$(mxpy wallet bech32 --decode ${ADDRESS_ARGUMENT})" mxpy --verbose contract call ${CONTRACT_ADDRESS} \ --pem=${WALLET_PEM} \ - --gas-limit=6000000 \ - --proxy=${PROXY} --chain=${CHAIN_ID} \ + --proxy=${PROXY} \ --function="myNonPayableEndpoint" \ --arguments $address_argument $1 $2 ${THIRD_BIGUINT_ARGUMENT}\ --send || return @@ -142,7 +140,7 @@ myNonPayableEndpoint() { So, what happens in this interaction and how do we call it? -Besides the function and arguments parts, the snippet is more or less the same as when deploying or upgrading a contract. When calling a non payable function, we need to provide the endpoint's name as the function argument. As for the arguments, they have to be in the **same order** as in the smart contract, including when calling an endpoint that has a variable number of arguments. Now, for the sake of example, we provided the arguments in multiple ways. +Besides the function and arguments parts, the snippet is more or less the same as when deploying or upgrading a contract. When calling a **non payable** function, we need to provide the **endpoint's name** as the function argument. As for the arguments, they have to be in the **same order** as in the smart contract, including when calling an endpoint that has a variable number of arguments. Now, for the sake of example, we provided the arguments in multiple ways. It is up to each developer to choose the layout he prefers, but a few points need to be underlined: @@ -159,7 +157,7 @@ In our example we provide the address argument as a fixed argument. We then conv - We can use `str:` for encoding strings. For example: `str:MYTOKEN-123456`. - Blockchain addresses that start with `erd1` are automatically encoded, so there is no need to further hex encode them. - The values **true** or **false** are automatically converted to **boolean** values. -- Values that are identified as **numbers** are hex encoded by default. +- Values that are identified as **numbers** are hex encoded as `BigUint` values. - Arguments like `0x...` are left unchanged, as they are interpreted as already encoded hex values. ::: @@ -176,8 +174,7 @@ ADDRESS_ARGUMENT=addr:erd14nw9pukqyqu75gj0shm8upsegjft8l0awjefp877phfx74775dsq49 myNonPayableEndpoint() { mxpy --verbose contract call ${CONTRACT_ADDRESS} \ --pem=${WALLET_PEM} \ - --gas-limit=6000000 \ - --proxy=${PROXY} --chain=${CHAIN_ID} \ + --proxy=${PROXY} \ --function="myNonPayableEndpoint" \ --arguments ${ADDRESS_ARGUMENT} $1 $2 ${THIRD_BIGUINT_ARGUMENT}\ --send || return @@ -194,7 +191,7 @@ myNonPayableEndpoint 10000 100000 Using unencoded values (for easier reading) would translate into: ```shell -myNonPayableEndpoint erd14nw9pukqyqu75gj0shm8upsegjft8l0awjefp877phfx74775dsq49swp3 10000 100000 1000000 +myNonPayableEndpoint addr:erd14nw9pukqyqu75gj0shm8upsegjft8l0awjefp877phfx74775dsq49swp3 10000 100000 1000000 ``` :::caution @@ -213,20 +210,29 @@ Now let's take a look at the following example, where we want to call a payable ```shell myPayableEndpoint() { - method_name=str:myPayableEndpoint - my_token=str:$1 + token_identifier=$1 token_amount=$2 mxpy --verbose contract call ${CONTRACT_ADDRESS} \ --pem=${WALLET_PEM} \ - --gas-limit=6000000 \ - --proxy=${PROXY} --chain=${CHAIN_ID} \ - --function="ESDTTransfer" \ - --arguments $my_token $token_amount $method_name\ + --proxy=${PROXY} \ + --token-transfers $token_identifier $token_amount \ + --function="myPayableEndpoint" \ --send || return } ``` -As we can see, the way we call a **payable endpoint** is by calling an `ESDTTransfer` function (or any other function that transfer assets and supports contract calls) and providing the name of the method as an argument. The order of the arguments differs for each transfer function. In our case, we specify in the terminal the **token type** and **the amount of tokens** we want to transfer and then we provide as a **fixed input** what smart contract endpoint we want to call. +To call a **payable endpoint**, we use the `--token-transfer` flag, which requires two values: + +1. The token identifier. +2. The amount. + +In our case, we specify in the terminal the **token identifier** and **the amount of tokens** we want to transfer. + +:::info +When specifying the amount of tokens to transfer, the value must include the token's decimal precision. + +For example EGLD use 18 decimals. This means that if you want to transfer 1.5 EGLD, the amount value will be $1.5 \times 10^{18}$. +::: [comment]: # (mx-context-auto) @@ -237,41 +243,23 @@ Now let's suppose we want to call an endpoint that accepts an NFT or an SFT as p ```shell ###PARAMS # $1 = NFT/SFT Token Identifier, -# $2 = NFT/SFT Token Nonce, -# $3 = NFT/SFT Token Amount, -# $4 = Destination Address, +# $2 = NFT/SFT Token Amount, FIRST_BIGUINT_ARGUMENT=1000 SECOND_BIGUINT_ARGUMENT=10000 -MY_WALLET_ADDRESS=erd1... myESDTNFTPayableEndpoint() { - method_name=str:myESDTNFTPayableEndpoint - sft_token=str:$1 - sft_token_nonce=$2 - sft_token_amount=$3 - destination_address=addr:$4 - mxpy --verbose contract call ${MY_WALLET_ADDRESS} \ + sft_token_identifier=$1 + sft_token_amount=$2 + mxpy --verbose contract call ${CONTRACT_ADDRESS} \ --pem=${WALLET_PEM} \ - --gas-limit=100000000 \ - --proxy=${PROXY} --chain=${CHAIN_ID} \ - --function="ESDTNFTTransfer" \ - --arguments $sft_token \ - $sft_token_nonce \ - $sft_token_amount \ - $destination_address \ - $method_name \ - ${FIRST_BIGUINT_ARGUMENT} \ - ${SECOND_BIGUINT_ARGUMENT} \ + --proxy=${PROXY} \ + --token-transfers $sft_token_identifier $sft_token_amount \ + --function="myESDTNFTPayableEndpoint" \ + --arguments ${FIRST_BIGUINT_ARGUMENT} ${SECOND_BIGUINT_ARGUMENT} \ --send || return } ``` -First of all, to call this type of transfer function we need to pass the receiver address the same as the sender address. So in this example, `MY_WALLET_ADDRESS` is the caller's address of the PEM wallet used. - -Now, like in the case of `ESDTTransfer`, the name of the called function is `ESDTNFTTransfer`. All the other required data is passed as arguments (including the destination contract's address and the endpoint). - -In case of this single NFT/SFT transfer, we first pass the **token** (identifier, nonce and amount) and then we pass the **destination address** and the **name of the endpoint**. In the end we pass whatever parameters the indicated method needs. - [comment]: # (mx-context-auto) ### Multi-ESDT transfer @@ -279,60 +267,37 @@ In case of this single NFT/SFT transfer, we first pass the **token** (identifier In case we need to call an endpoint that accepts multiple tokens (let's say for example 2 fungible tokens and an NFT). Let's take a look at the following example: ```shell - ###PARAMS -# $1 = Destination Address, -# $2 = First Token Identifier, -# $3 = First Token Amount, -# $4 = Second Token Identifier, -# $5 = Second Token Amount, +# $1 = First Token Identifier, +# $2 = First Token Amount, +# $3 = Second Token Identifier, +# $4 = Second Token Amount, +# $5 = Third Token Identifier, # $6 = Third Token Identifier, -# $7 = Third Token Nonce, -# $8 = Third Token Identifier, FIRST_BIGUINT_ARGUMENT=1000 SECOND_BIGUINT_ARGUMENT=10000 myMultiESDTNFTPayableEndpoint() { - method_name=str:myMultiESDTPayableEndpoint - destination_address=addr:$1 - number_of_tokens=3 - first_token=str:$2 - first_token_nonce=0 - first_token_amount=$3 - second_token=str:$4 - second_token_nonce=0 - second_token_amount=$5 - third_token=str:$6 - third_token_nonce=$7 - third_token_amount=$8 - - mxpy --verbose contract call $user_address \ + first_token_identifier=$1 + first_token_amount=$2 + second_token_identifier=$3 + second_token_amount=$4 + third_token_identifier=$5 + third_token_amount=$6 + + mxpy --verbose contract call ${CONTRACT_ADDRESS} \ --pem=${WALLET_PEM} \ - --gas-limit=100000000 \ - --proxy=${PROXY} --chain=${CHAIN_ID} \ - --function="MultiESDTNFTTransfer" \ - --arguments $destination_address \ - $number_of_tokens \ - $first_token \ - $first_token_nonce \ - $first_token_amount \ - $second_token \ - $second_token_nonce \ - $second_token_amount \ - $third_token \ - $third_token_nonce \ - $third_token_amount \ - $method_name \ - ${FIRST_BIGUINT_ARGUMENT} \ - ${SECOND_BIGUINT_ARGUMENT} \ + --proxy=${PROXY} \ + --token-transfers $first_token_identifier $first_token_amount \ + $second_token_identifier $second_token_amount \ + $third_token_identifier $third_token_amount \ + --function="payable_nft_with_args" \ + --arguments ${FIRST_BIGUINT_ARGUMENT} ${SECOND_BIGUINT_ARGUMENT} \ --send || return -} ``` In this example, we call `myMultiESDTPayableEndpoint` endpoint, by transferring **3 different tokens**: the first two are fungible tokens and the last one is an NFT. -The endpoint takes 2 BigUInt arguments. The layout of the snippet is almost the same as with `ESDTNFTTransfer` (including the fact that the sender is the same as the receiver) but has different arguments. We now pass the destination address first and the number of ESDT/NFT tokens that we want to sent. Then, for each sent token, we specify the identifier, the nonce (in our example 0 for the fungible tokens and a specific value for the NFT) and the amount. In the end, like with the `ESDTTransfer`, we pass the name of the method we want to call and the rest of the parameters of that specific method. - :::tip More information about ESDT Transfers [here](/tokens/fungible-tokens/#transfers). ::: From 1adb36ecbffc98a67c7800f841d2fb9fded9c254 Mon Sep 17 00:00:00 2001 From: BiancaIalangi Date: Tue, 28 Oct 2025 14:21:16 +0200 Subject: [PATCH 5/7] apply reviews --- docs/sdk-and-tools/mxpy/smart-contract-interactions.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/sdk-and-tools/mxpy/smart-contract-interactions.md b/docs/sdk-and-tools/mxpy/smart-contract-interactions.md index 8670b6c5..b293abdf 100644 --- a/docs/sdk-and-tools/mxpy/smart-contract-interactions.md +++ b/docs/sdk-and-tools/mxpy/smart-contract-interactions.md @@ -140,7 +140,7 @@ myNonPayableEndpoint() { So, what happens in this interaction and how do we call it? -Besides the function and arguments parts, the snippet is more or less the same as when deploying or upgrading a contract. When calling a **non payable** function, we need to provide the **endpoint's name** as the function argument. As for the arguments, they have to be in the **same order** as in the smart contract, including when calling an endpoint that has a variable number of arguments. Now, for the sake of example, we provided the arguments in multiple ways. +Besides the function and arguments parts, the snippet is more or less the same as when deploying or upgrading a contract. When calling a **non payable** function, we need to provide the **endpoint's name** as the function argument. As for the arguments, they have to be in the **same order** as in the endpoint's signature. Now, for the sake of example, we provided the arguments in multiple ways. It is up to each developer to choose the layout he prefers, but a few points need to be underlined: @@ -152,7 +152,7 @@ It is up to each developer to choose the layout he prefers, but a few points nee In our example we provide the address argument as a fixed argument. We then convert it to hexadecimal format (as it is in the bech32 format by default) and only after that we pass it as a parameter. As for the `BigUint` parameters, we provide the first two parameters directly in the terminal and the last one as a fixed argument, hexadecimal encoded. :::tip -`mxpy` facilitates us with some encoding conventions, including: +`mxpy` provides the following encoding conventions: - We can use `str:` for encoding strings. For example: `str:MYTOKEN-123456`. - Blockchain addresses that start with `erd1` are automatically encoded, so there is no need to further hex encode them. @@ -273,7 +273,7 @@ In case we need to call an endpoint that accepts multiple tokens (let's say for # $3 = Second Token Identifier, # $4 = Second Token Amount, # $5 = Third Token Identifier, -# $6 = Third Token Identifier, +# $6 = Third Token Amount, FIRST_BIGUINT_ARGUMENT=1000 SECOND_BIGUINT_ARGUMENT=10000 From eaca40c47722c3c9115f69f641e54938afea3d35 Mon Sep 17 00:00:00 2001 From: BiancaIalangi Date: Tue, 28 Oct 2025 14:25:01 +0200 Subject: [PATCH 6/7] typo --- docs/sdk-and-tools/mxpy/smart-contract-interactions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sdk-and-tools/mxpy/smart-contract-interactions.md b/docs/sdk-and-tools/mxpy/smart-contract-interactions.md index b293abdf..c3a2b137 100644 --- a/docs/sdk-and-tools/mxpy/smart-contract-interactions.md +++ b/docs/sdk-and-tools/mxpy/smart-contract-interactions.md @@ -231,7 +231,7 @@ In our case, we specify in the terminal the **token identifier** and **the amoun :::info When specifying the amount of tokens to transfer, the value must include the token's decimal precision. -For example EGLD use 18 decimals. This means that if you want to transfer 1.5 EGLD, the amount value will be $1.5 \times 10^{18}$. +For example EGLD uses 18 decimals. This means that if you want to transfer 1.5 EGLD, the amount value will be $1.5 \times 10^{18}$. ::: [comment]: # (mx-context-auto) From 91fbb12da9d9af481b4a84669e3c48246a44ed16 Mon Sep 17 00:00:00 2001 From: BiancaIalangi Date: Tue, 28 Oct 2025 17:10:07 +0200 Subject: [PATCH 7/7] add extra info about token identifier for token transfer --- .../sdk-and-tools/mxpy/smart-contract-interactions.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/sdk-and-tools/mxpy/smart-contract-interactions.md b/docs/sdk-and-tools/mxpy/smart-contract-interactions.md index c3a2b137..a1de4e25 100644 --- a/docs/sdk-and-tools/mxpy/smart-contract-interactions.md +++ b/docs/sdk-and-tools/mxpy/smart-contract-interactions.md @@ -221,13 +221,22 @@ myPayableEndpoint() { } ``` -To call a **payable endpoint**, we use the `--token-transfer` flag, which requires two values: +To call a **payable endpoint**, we use the `--token-transfer` argument, which requires two values: 1. The token identifier. 2. The amount. In our case, we specify in the terminal the **token identifier** and **the amount of tokens** we want to transfer. +:::info +The format for the token identifier changes based on the type of asset you are sending: + +- **ESDTs Tokens**: Use the **standard** Token Identifier. +- **NFTs and SFTs**: Use the **extended** Token identifier format, which includes the token's nonce. The nonce must be hex-encoded. + - Example: `NFT-123456-0a` (where `0a` is the hex-encoded nonce). + +::: + :::info When specifying the amount of tokens to transfer, the value must include the token's decimal precision.