<p>It's likely because your token name doesnt match between the CLI and the metadata.json file. Hard to say since you've hidden them...</p>

CC BY-SA 4.0
2021-12-29T01:03:33.740Z
2021-12-29T01:03:33.740Z
Tygar Pool
<p>It looks like more of a data issue within the metadata json, rather then a problem in the transaction format.</p>
<p>It looks like you're following the <a href="https://developers.cardano.org/docs/native-tokens/minting-nfts/" rel="nofollow noreferrer">https://developers.cardano.org/docs/native-tokens/minting-nfts/</a></p>
<p>Please note that the <code>--mint=&quot;$tokenamount $policyid.$tokenname&quot; \</code> <code>$policyid</code> and <code>$tokenname</code>, have to match the two <code>HIDDEN</code> fields in the metadata.json</p>
<p>Furthermore, the digital asset (eg. the image/audio/video/whatever) needs to be in a IPFS server. Sometimes some IPFS services are slow at serving/propagating the asset, so a workaround, is to create an account on pinata.cloud and load your asset there. Then you're sure everything is fine.</p>
<p>For further help, can you share a minting transaction hash? This way we can inspect the tx and tell you exactly whats wrong.</p>
<p>If you want to do a test, you can use new policy/image whatever, so you won't share private stuff.</p>
<p>Thanks and good luck</p>

CC BY-SA 4.0
2021-12-29T09:51:21.370Z
2021-12-29T09:51:21.370Z
Giovanni G
<p>Your metadata file is not structured correctly. Please check <a href="https://cips.cardano.org/cips/cip25/" rel="nofollow noreferrer">CIP 25 - NFT Metadata Standard</a>.</p>
<pre><code>{
  &quot;721&quot;: {
    &quot;&lt;policy_id&gt;&quot; {
       ...
</code></pre>

CC BY-SA 4.0
2022-01-09T18:29:13.610Z
2022-01-11T05:53:44.903Z
2022-01-11T05:53:44.903Z
Joseph Ku
<p>I hope all is well and everyone had a great holiday season. I am having an issue minting NFT's from the CLI they appear to be minting without metadata, even though I am referring to the fully populated metadata.json file used. All variables are correct ($variables are correct) Can anyone toss me a bone at what I'm doing wrong? The NFT does actually mint, just minus all metadata and thus no picture or details about the NFT.</p>
<p>My Minting Command =</p>
<pre><code>cardano-cli transaction build \
--mainnet \
--alonzo-era \
--tx-in $txhash#$txix \
--tx-out $nftwallet+$output+&quot;$tokenamount $policyid.$tokenname&quot; \
--change-address $address \
--mint=&quot;$tokenamount $policyid.$tokenname&quot; \
--minting-script-file $script \
--metadata-json-file metadata.json \
--invalid-hereafter $slotnumber \
--witness-override 2 \
--out-file matx.raw
</code></pre>
<p>Metadata file -</p>
<pre><code>{
&quot;721&quot;: {
&quot;HIDDEN&quot;: {
&quot;HIDDEN&quot;: {
&quot;name&quot;: &quot;NFT NAME HERE&quot;,
&quot;image&quot;: &quot;ipfs://IPFSLINKHERE&quot;,
&quot;mediaType&quot;: &quot;image/png&quot;,
&quot;description&quot;: &quot;DESCRIPTION HERE&quot;,
&quot;files&quot;: [
{
&quot;name&quot;: &quot;PIC NAME HERE&quot;,
&quot;mediaType&quot;: &quot;image/png&quot;,
&quot;src&quot;: &quot;ipfs://IPFS LINK HERE&quot;
}
]
}
},
&quot;version&quot;: &quot;1.0&quot;
}
}
</code></pre>

CC BY-SA 4.0
2021-12-29T15:12:46.100Z
Please, take a look on this answer: https://cardano.stackexchange.com/a/4882/1231
georgeos
CC BY-SA 4.0
2021-12-30T08:14:03.963Z
Could you please include the error that you are getting?
pyropy
<nft><minting>
NFT Minting without Metadata
# NFT Minting without Metadata

(Asked by: username_0 on 2021-12-28)

I hope all is well and everyone had a great holiday season. I am having an issue minting NFT's from the CLI they appear to be minting without metadata, even though I am referring to the fully populated metadata.json file used. All variables are correct ($variables are correct) Can anyone toss me a bone at what I'm doing wrong? The NFT does actually mint, just minus all metadata and thus no picture or details about the NFT.
My Minting Command =
cardano-cli transaction build \
--mainnet \
--alonzo-era \
--tx-in $txhash#$txix \
--tx-out $nftwallet+$output+"$tokenamount $policyid.$tokenname" \
--change-address $address \
--mint="$tokenamount $policyid.$tokenname" \
--minting-script-file $script \
--metadata-json-file metadata.json \
--invalid-hereafter $slotnumber \
--witness-override 2 \
--out-file matx.raw

Metadata file -
{
"721": {
"HIDDEN": {
"HIDDEN": {
"name": "NFT NAME HERE",
"image": "ipfs://IPFSLINKHERE",
"mediaType": "image/png",
"description": "DESCRIPTION HERE",
"files": [
{
"name": "PIC NAME HERE",
"mediaType": "image/png",
"src": "ipfs://IPFS LINK HERE"
}
]
}
},
"version": "1.0"
}
}

**Tags:** nft, minting
> **Comments:**
> **username_1**: Please, take a look on this answer: https://cardano.stackexchange.com/a/4882/1231  
> **username_2**: Could you please include the error that you are getting?  

---

## 3 answers

### Answer by username_3 on 2021-12-29. Score: 1

It's likely because your token name doesnt match between the CLI and the metadata.json file. Hard to say since you've hidden them...


---

### Answer by username_4 on 2021-12-29. Score: 0

It looks like more of a data issue within the metadata json, rather then a problem in the transaction format.

It looks like you're following the <https://developers.cardano.org/docs/native-tokens/minting-nfts/>

Please note that the `--mint="$tokenamount $policyid.$tokenname" \` `$policyid` and `$tokenname`, have to match the two `HIDDEN` fields in the metadata.json

Furthermore, the digital asset (eg. the image/audio/video/whatever) needs to be in a IPFS server. Sometimes some IPFS services are slow at serving/propagating the asset, so a workaround, is to create an account on pinata.cloud and load your asset there. Then you're sure everything is fine.

For further help, can you share a minting transaction hash? This way we can inspect the tx and tell you exactly whats wrong.

If you want to do a test, you can use new policy/image whatever, so you won't share private stuff.

Thanks and good luck


---

### Answer by username_5 on 2022-01-09. Score: 0

Your metadata file is not structured correctly. Please check CIP 25 - NFT Metadata Standard.
{
  "721": {
    "" {
       ...


---

