<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[DiscoveringStacks]]></title><description><![CDATA[DiscoveringStacks]]></description><link>https://discoveringstacks.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 15:07:17 GMT</lastBuildDate><atom:link href="https://discoveringstacks.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Building Carbon Credits Marketplace on Stacks Part I]]></title><description><![CDATA[The main aim of the project is to establish a marketplace that can help individuals to buy the credits and tokenize them as NFTs. In order to begin this…]]></description><link>https://discoveringstacks.hashnode.dev/building-carbon-credits-marketplace-on-stacks-part-i</link><guid isPermaLink="true">https://discoveringstacks.hashnode.dev/building-carbon-credits-marketplace-on-stacks-part-i</guid><category><![CDATA[Stacks]]></category><dc:creator><![CDATA[Syed Ghufran Hassan]]></dc:creator><pubDate>Sat, 30 Aug 2025 15:17:57 GMT</pubDate><content:encoded><![CDATA[<p>The main aim of the project is to establish a marketplace that can help individuals to buy the credits and tokenize them as NFTs.  </p>
<p>In order to begin this project I am referencing SIP 009 which is actually the Standard Trait Definition for Non-Fungible Tokens  </p>
<p><a target="_blank" href="https://github.com/stacksgov/sips/blob/main/sips/sip-009/sip-009-nft-standard.md">https://github.com/stacksgov/sips/blob/main/sips/sip-009/sip-009-nft-standard.md</a>  </p>
<p>The main aspect is to gain understanding about setting up carbon credits, how the credits and events will be listed and how they will be available for buy and sell in the marketplace.  </p>
<p>Although we do have similarity with the ERC 721 which is actually ethereum protocol for NFTs so here the only distinction is the placement of token-id in terms of ordering in arguements. This SIP only defines a function for getting the URI pointing to the metadata of an NFT.  </p>
<p>From this document, I have taken reference for native functions and took consideration about last token ID, Token - URI, owner and transfer. They will all be made inclusive in the trait.  </p>
<p>My next approach is to build contracts regarding carbon credits, carbon events, carbon listing, carbon marketplace and retiring carbon credits once they are purchased which I will cover in my next blog.</p>
]]></content:encoded></item></channel></rss>