<p>For display purpose, people generally use the &quot;name&quot; attribute from the CIP-25 metadata, not the &lt;asset_name&gt;.</p>
<p><a href="https://cips.cardano.org/cips/cip25/" rel="nofollow noreferrer">https://cips.cardano.org/cips/cip25/</a>:</p>
<pre><code>{
  &quot;721&quot;: {
    &quot;&lt;policy_id&gt;&quot;: {
      &quot;&lt;asset_name&gt;&quot;: {
        &quot;name&quot;: &lt;string&gt;,
        &quot;image&quot;: &lt;uri | array&gt;
      }
    }
  }
}
</code></pre>

CC BY-SA 4.0
2022-06-05T01:23:31.673Z
Is the asset name attached to the TokenName variable used in smart contracts
Floof99
CC BY-SA 4.0
2022-06-03T21:53:21.603Z
2022-06-03T21:53:21.603Z
DaveStrider
<p>So I am working on a NFT minting and I checked the CIP-25 for metadata descriptions and I am confused regarding the naming of the NFT.</p>
<p>What is really the name of the NFT? (as in recognized by JPG.store) Is it the TokenName that is recognized by smart contracts or is it the name specified in the metadata?</p>

<plutus><nft><metadata><metadata.json>
CNFT metadata structure
# CNFT metadata structure

(Asked by: username_0 on 2022-06-03)

So I am working on a NFT minting and I checked the CIP-25 for metadata descriptions and I am confused regarding the naming of the NFT.

What is really the name of the NFT? (as in recognized by JPG.store) Is it the TokenName that is recognized by smart contracts or is it the name specified in the metadata?

**Tags:** plutus, nft, metadata, metadata.json

---

## 1 answers

### Answer by username_1 on 2022-06-03. Score: 2 | Accepted answer

For display purpose, people generally use the "name" attribute from the CIP-25 metadata, not the .
https://cips.cardano.org/cips/cip25/:
{
  "721": {
    "": {
      "": {
        "name": ,
        "image": 
      }
    }
  }
}

> **Comments:**
> **username_0**: Is the asset name attached to the TokenName variable used in smart contracts  

---

