Understanding the purpose of nonce in Elrond NFT transactions

NFT
1

I’m working with NFT transfers on the Elrond blockchain and came across the nonce parameter. Here’s a sample transaction structure I found:

NFTTransferTx {
    From: <sender wallet address>
    To: <sender wallet address>
    Amount: 0
    GasLimit: 1000000 + data_length * 1500
    Payload: "ESDTNFTTransfer" +
          "@" + <collection_id_hex> +
          "@" + <nft_nonce_hex> + 
          "@" + <transfer_amount_hex> +
          "@" + <recipient_address_hex>
}

Can someone explain what exactly this nonce value represents in the context of Elrond NFTs? Also, what’s the proper way to obtain this nonce value when preparing a transfer transaction? I’m trying to understand how it differs from regular transaction nonces.

2

Hey @Elias87! Yeah, the nonce thing tripped me up when I started with Elrond NFTs too.

That nonce in the payload isn’t a transaction nonce - it’s just a unique ID for each NFT in a collection. Think of it as the NFT’s serial number.

When you mint a collection, each NFT gets a nonce starting from 1, 2, 3, etc. So if “CoolArt” has 100 NFTs, they’re numbered 1-100. Want to transfer #42? Use nonce 42 in your payload.

You get the nonce by querying the blockchain API or using the Elrond SDK to fetch NFT details. Are you building from scratch or using a specific SDK? And are you transferring your own NFTs or building marketplace functionality?

Watch out for hex encoding - convert the nonce number to hex properly before adding it to the payload. What language are you using?

3

the nonce acts like a unique id fw your nft, kinda like a fingerprint for each one in a collection. You can check em on Elrond Explorer for all the nonces. Just make sure u convert to hex right or else the transfer might fail!

4

The Problem:

You’re having trouble understanding and using the nonce parameter when transferring Elrond NFTs. You’ve seen examples in transaction structures, but are unsure how to obtain the correct nonce value and how it differs from regular transaction nonces.

:thinking: Understanding the “Why” (The Root Cause):

The nonce parameter within the Elrond NFT transfer payload is not the same as the transaction nonce used to prevent replay attacks in standard blockchain transactions. Instead, it acts as a unique serial number for each NFT within a specific collection. Each NFT minted into a collection receives a sequential nonce value (typically starting from 1, then 2, 3, and so on). This nonce is integral to identifying the specific NFT you intend to transfer.

:gear: Step-by-Step Guide:

  1. Retrieve the NFT’s Nonce: You cannot generate the nonce yourself; it’s assigned during the minting process. To obtain the correct nonce for a specific NFT, you must query Elrond’s blockchain API. The API endpoint /accounts/{address}/nfts allows you to retrieve all NFTs associated with a given wallet address. The response will include the nonce (along with other NFT metadata such as collection ID) for each NFT.

  2. Use the Elrond SDK (Recommended): Using the official Elrond SDK is highly recommended. The SDK simplifies the process of interacting with the blockchain API and handles details such as data formatting and hex encoding. Consult the Elrond SDK documentation for specific functions to retrieve NFT details and construct transaction payloads. This approach is more robust and less error-prone than manually interacting with the API.

  3. Proper Hex Encoding: Crucially, after retrieving the nonce (which is likely an integer), you must convert it to its hexadecimal representation before including it in the Payload of your NFTTransferTx. Pay close attention to padding the hex representation to ensure it’s the correct length. Failure to do so will result in transaction failures.

  4. Construct the Transaction Payload: Once you have the correct hexadecimal nonce, integrate it into your NFTTransferTx payload as shown in your example:

NFTTransferTx {
    From: <sender wallet address>
    To: <recipient wallet address>
    Amount: 0
    GasLimit: 1000000 + data_length * 1500
    Payload: "ESDTNFTTransfer" +
          "@" + <collection_id_hex> +
          "@" + <nft_nonce_hex> + 
          "@" + <transfer_amount_hex> +
          "@" + <recipient_address_hex>
}

Remember that <nft_nonce_hex> should be the correctly padded hex representation of the nonce obtained from Step 1.

:mag: Common Pitfalls & What to Check Next:

  • Incorrect API Endpoint: Double-check that you’re using the correct Elrond API endpoint /accounts/{address}/nfts to retrieve NFT metadata.
  • Hex Encoding Errors: The most common mistake is improper hex encoding of the nonce. Carefully review your conversion process. Use a reliable hex encoding library if available in your chosen programming language.
  • Data Type Mismatches: Ensure that all data types in your NFTTransferTx structure match the Elrond blockchain’s requirements. Incorrect data types can lead to transaction failures.
  • Transaction Gas Limit: Ensure that your GasLimit is sufficient to cover the transaction costs.

:speech_balloon: Still running into issues? Share your (sanitized) code snippet showing how you’re retrieving the nonce and constructing the transaction payload, along with the exact error message you’re receiving, and any other relevant details. The community is here to help!