<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pinata on Coderrob</title><link>https://coderrob.com/tags/pinata/</link><description>Recent content in Pinata on Coderrob</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 03 Nov 2021 16:46:16 -0500</lastBuildDate><atom:link href="https://coderrob.com/tags/pinata/index.xml" rel="self" type="application/rss+xml"/><item><title>Pinning NFT Images and Metadata to IPFS with Pinata</title><link>https://coderrob.com/posts/storing-nft-metadata-in-ipfs-with-pinata/</link><pubDate>Wed, 03 Nov 2021 16:46:16 -0500</pubDate><guid>https://coderrob.com/posts/storing-nft-metadata-in-ipfs-with-pinata/</guid><description>&lt;p&gt;An NFT is not the image.&lt;/p&gt;
&lt;p&gt;For a typical ERC-721 token, the smart contract returns a metadata URI. The metadata document at that URI describes the token and points to its image. If either pointer can be changed without limits, the thing a collector sees can change even though the token itself never moved.&lt;/p&gt;
&lt;p&gt;That is a trust problem.&lt;/p&gt;
&lt;p&gt;In this post, I will use &lt;a href="https://ipfs.tech/"&gt;IPFS&lt;/a&gt; and &lt;a href="https://www.pinata.cloud/"&gt;Pinata&lt;/a&gt; to give the image and metadata layers content-addressed identities. I will also use my &lt;a href="https://github.com/Coderrob/pinata-ipfs-scripts-for-nft-projects"&gt;Pinata IPFS scripts for NFT projects&lt;/a&gt; to pin images independently and pin the finished metadata as a directory.&lt;/p&gt;</description></item></channel></rss>