<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Jagger Bellagarda</title>
    <description>The latest articles on DEV Community by Jagger Bellagarda (@jagger_sa).</description>
    <link>https://dev.to/jagger_sa</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F828744%2Fb5eeecdc-6a41-450d-b1be-cc4785db637b.jpg</url>
      <title>DEV Community: Jagger Bellagarda</title>
      <link>https://dev.to/jagger_sa</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jagger_sa"/>
    <language>en</language>
    <item>
      <title>DID linked NFTs</title>
      <dc:creator>Jagger Bellagarda</dc:creator>
      <pubDate>Thu, 10 Mar 2022 20:37:22 +0000</pubDate>
      <link>https://dev.to/jagger_sa/did-linked-nfts-85n</link>
      <guid>https://dev.to/jagger_sa/did-linked-nfts-85n</guid>
      <description>&lt;p&gt;Hi there,&lt;/p&gt;

&lt;p&gt;I have a bit of an odd request.&lt;/p&gt;

&lt;p&gt;I am looking at coding an NFT smart contract created that has the mint functionality link to a verifiable credential issued to a decentralized identifier (outside of the smart contract I am assuming) instead of just an IPFS link. &lt;/p&gt;

&lt;p&gt;Therefore, there needs to be a new functionality coded that will be executed when a transfer of an NFT occurs, the verifiable credential is revoked and reissued to the new holder.&lt;/p&gt;

&lt;p&gt;Is this possible at all?&lt;/p&gt;

</description>
      <category>nft</category>
    </item>
  </channel>
</rss>
