<?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" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by DuckDuckDev on Medium]]></title>
        <description><![CDATA[Stories by DuckDuckDev on Medium]]></description>
        <link>https://medium.com/@duckddev?source=rss-c5181e480791------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZOYuJSJvKywcA8c1sIKz-w.jpeg</url>
            <title>Stories by DuckDuckDev on Medium</title>
            <link>https://medium.com/@duckddev?source=rss-c5181e480791------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 15:24:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@duckddev/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Sort & Narrow Upcoming NFT Drops with Data: How I Developed NFT Sorter]]></title>
            <link>https://coinsbench.com/sort-narrow-upcoming-nft-drops-with-data-how-i-developed-nft-sorter-59e1b7160fa7?source=rss-c5181e480791------2</link>
            <guid isPermaLink="false">https://medium.com/p/59e1b7160fa7</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[DuckDuckDev]]></dc:creator>
            <pubDate>Wed, 13 Jul 2022 00:54:27 GMT</pubDate>
            <atom:updated>2022-07-13T12:03:07.190Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Orr5LJc6oqOyi_DpSqm1Q.png" /><figcaption><a href="https://nftsorter.com/">https://nftsorter.com/</a></figcaption></figure><p>Art seems interesting enough; let me check out their Twitter. Click. New tab. Hmm, this NFT project has 10,000 followers. Worth looking into. Odd, their posts rarely garner more than three likes. Seems like there’s very little comment engagement. I’ll table this project for now, back to the drop calendar. Click. New tab. Interesting art, but it seems like there’s no community. Click. New tab.</p><p>My process repeats for hours as I try and vet upcoming NFT drops for community engagement. Will investing in this project pay off? I believe that only data can answer that question. Unfortunately, that data was cumbersome to find.</p><p>This is a story of how I became so fed up with how inefficient existing NFT drop calendars were that I programmed my own.</p><h3><strong>My Motivation</strong></h3><p>Time and energy.</p><p>Utilizing existing tools, determining whether an upcoming NFT mint was promising felt inefficient. For traditional investments, like stocks, there were concrete metrics about a company to assess its potential, like revenue and cash flow. There were numerical measurements all aggregated in one place (stock screeners).</p><p>For NFTs, I felt like I was throwing darts in the dark. I learned to utilize metrics like community engagement on the NFT project’s Discord and Twitter. Still, I’d have to click through multiple links on existing drop calendars to do so. Why couldn’t that data be shown in a table format on one page to avoid scrolling, eyeballing, and clicking?</p><h3><strong>The Development</strong></h3><p>At first, it started with a personal Python project utilizing the Twitter API to create a program that would output the average likes, retweets, and comments an account has per tweet. I realized over time that community engagement on an NFT Twitter account is far more revealing than raw followers. Previously, I’d have to guesstimate engagement, but now I had a tool to objectively measure it. Slowly, the metrics I measured increased and as my access to data grew, so did my ability to make good judgments about upcoming projects.</p><p>The thought had been in my mind for a while — if this tool helped me, couldn’t it help others? That’s when I began developing a database of upcoming NFT projects. I created a front-end utilizing Node.js, used the Twitter API to collect engagement data, utilized MongoDB queries to create sorting functionality, and jQuery to create a search bar.</p><p>Thus, NFT Sorter, the drop calendar most comprehensive in features, was born.</p><h3><strong>The End Result</strong></h3><ul><li>At any given time, NFT Sorter lists over 150+ projects sorted by engagement.</li><li>The database is updated daily, adding the newest announced drops and archiving projects after their drop date.</li><li>Clicking project titles link to the collection’s Discord, Twitter, and website.</li><li>Sort by Twitter followers, number of tweets, average likes, replies, retweets, and drop date.</li><li>Search by specific terms.</li><li>Narrow results according to your requirements.</li></ul><blockquote>If you’re interested in seeing the end result, NFT Sorter can be found <a href="https://nftsorter.com/">here</a>. Any feedback in the comments is much appreciated!</blockquote><p>The greatest lesson I learned in creating NFT Sorter was how interdisciplinary tech ideas can be. My project was inspired by stock screeners in the financial industry, something I wouldn’t expect would be the basis of my next project.</p><p>If you’re a developer looking for their next big project, I’d recommend looking toward other fields around you for inspiration.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59e1b7160fa7" width="1" height="1" alt=""><hr><p><a href="https://coinsbench.com/sort-narrow-upcoming-nft-drops-with-data-how-i-developed-nft-sorter-59e1b7160fa7">Sort &amp; Narrow Upcoming NFT Drops with Data: How I Developed NFT Sorter</a> was originally published in <a href="https://coinsbench.com/">CoinsBench</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Call Functions on Previously Deployed Remix Contracts in Three Steps]]></title>
            <link>https://medium.com/@duckddev/call-functions-on-previously-deployed-remix-contracts-in-three-steps-9c5a7810b75f?source=rss-c5181e480791------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c5a7810b75f</guid>
            <category><![CDATA[remix-ide]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[remix]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[DuckDuckDev]]></dc:creator>
            <pubDate>Fri, 01 Jul 2022 20:09:46 GMT</pubDate>
            <atom:updated>2022-07-01T20:09:46.871Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8wiTtzj4oQbq7n8FnjUeng.jpeg" /></figure><p>Have you ever wanted a simple way to interact with your deployed smart contracts? If you’ve ever used <a href="https://remix.ethereum.org/">Remix IDE</a> to deploy a smart contract, you may notice that the ability to interact with your contract seems to disappear once you reload the webpage.</p><p>This may seem problematic for any functions you’d need access to down the road, such as a withdraw function in an NFT collection.</p><p>Luckily, every Remix-deployed contract’s functions can reaccessed again online in a matter of minutes. Here’s how.</p><p><strong>Step 1) Load, Navigate, Recompile</strong></p><p>First, load the <a href="https://remix.ethereum.org/">Remix IDE webpage</a>. Navigate to your smart contract file in the Remix file explorer, then click the Solidity Compiler icon (circled in screenshot below) in the left-hand menu bar. Finally, click the compile button.</p><p><em>Note: To access a previously deployed contract, the compiled smart contract in this step must be the exact same as the previously deployed contract.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/372/1*13IthZy-ybQcn4CyBQpQBw.png" /></figure><p><strong>Step 2) Copy Case Sensitive Contract Address</strong></p><p>Find the account you originally deployed your smart contract from. For example, if you’re using Metamask, find the transaction log for your contract deployment, and click “View on block explorer” next to “Status”.</p><p><strong>Import note:</strong> The Remix IDE will not load your contract’s functions for interaction unless you have the “checksumed address”.</p><p>To find the checksumed address, navigate to the scan page for the contract. The checksumed address should be listed at the top of the page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/1*9Xs61rqmn7LIdJlLs5NnPQ.png" /></figure><p>Copy the case-sensitive address to your clipboard.</p><p><strong>Step 3) Load Contract</strong></p><p>Navigate back to Remix IDE and the “Deploy &amp; Run Transactions” page. Make sure you’re connected to the environment you deployed your contract to originally and connected with the same account you deployed with. Paste the checksumed address into the “At Address” field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/363/1*Jp-yLYYbkp4mcv0dPZQXyg.png" /></figure><p>Congratulations! Beneath “Deployed Contracts,” your previously deployed contract’s functions are once again accessible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c5a7810b75f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Find Quality NFT Projects 10x Faster — New Tool in Beta]]></title>
            <link>https://medium.com/@duckddev/find-quality-nft-projects-10x-faster-new-tool-in-beta-34acd8c2c168?source=rss-c5181e480791------2</link>
            <guid isPermaLink="false">https://medium.com/p/34acd8c2c168</guid>
            <category><![CDATA[nftcommunity]]></category>
            <category><![CDATA[investment]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[DuckDuckDev]]></dc:creator>
            <pubDate>Tue, 07 Jun 2022 21:52:25 GMT</pubDate>
            <atom:updated>2022-06-07T21:52:25.828Z</atom:updated>
            <content:encoded><![CDATA[<h3>Find Quality NFT Projects 10x Faster — New Tool in Beta</h3><p>I’m an NFT enthusiast who’s been frustrated by how time-consuming it is to screen upcoming NFT drops. In the past, I’d use upcoming drop lists, click-through Twitter accounts, and eyeball engagement. But, wow, did that process make me tired. So much so that I decided to develop my own NFT screening tool. Introducing…</p><h3><a href="https://nftsorter.com/">https://nftsorter.com/</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l3PZVRSI-FNtF7xqd9r1jA.png" /></figure><p><strong>Doing the grunt work for you.</strong></p><p>Rather than you having to guesstimate engagement and lose time paging between a drop list tab and each collection’s Twitter, NFT Sorter automatically indexes NFT projects by Twitter followers, number of tweets, average likes, replies, retweets, and drop date all in one page.</p><p>Clicking on a project title links to the collection’s Discord, Twitter, and website.</p><p>At any given time, NFT Sorter has 150+ upcoming projects indexed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i6VtXtfYZDTG39_VsTcMDA.png" /></figure><p><strong>Advanced sorting functionality.</strong></p><p>Is there a specific metric you look for in new NFT projects? Automatically order results using NFT Sorter. Find the highest quality projects with result filter functionality. Looking for data on a specific project? Use our search bar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dGaLyPl1wWGRD6WnwCoSwA.png" /></figure><p><strong>Completely free.</strong></p><p>I made NFT Sorter because I was fed up with how time-consuming it was to find quality drops. It’s saved me time and energy finding new projects; I hope it can help you too!</p><p>NFT Sorter is in a free open beta. I’d love to hear your feedback in the comments or on our discord. <a href="https://discord.gg/yhb4A5vz9v">https://discord.gg/yhb4A5vz9v</a></p><p>Thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34acd8c2c168" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Limit NFT or Token Supply With Four Lines of Code]]></title>
            <link>https://medium.com/@duckddev/limit-nft-or-token-supply-with-four-lines-of-code-2fd2f94a4002?source=rss-c5181e480791------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fd2f94a4002</guid>
            <category><![CDATA[solidity]]></category>
            <category><![CDATA[nft-minting]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <dc:creator><![CDATA[DuckDuckDev]]></dc:creator>
            <pubDate>Fri, 29 Apr 2022 00:44:01 GMT</pubDate>
            <atom:updated>2022-04-29T00:44:01.932Z</atom:updated>
            <content:encoded><![CDATA[<p>Ever seen an NFT collection with a max supply of NFTs that could be minted? As a developer, I wanted to program my own NFT minting contract and sought to programmatically cap the number of NFTs that could be minted from my collection.</p><p>Here’s the simplest implementation I could find. The following assumes you are using a ERC721 token and only covers the supply limitation implementation, not the entire mint function.</p><p><strong>Setup. </strong><a href="https://www.npmjs.com/package/@openzeppelin/contracts/v/4.4.1"><strong>Install</strong></a><strong> OpenZeppelin Library</strong></p><blockquote>npm i @openzeppelin/contracts</blockquote><p>Run the above command in console in your project’s directory. OpenZeppelin is a library of Ethereum smart contracts. You’ll be utilizing OpenZeppelin’s ERC721Enumerable contract, which will allow your contract to keep track of how many NFTs are minted.</p><p><strong>Line 1. Import OpenZeppelin </strong><a href="https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC721/extensions/ERC721Enumerable.sol"><strong>ERC721Enumerable</strong></a></p><blockquote>import “@openzeppelin/contracts/token/ERC721/extensions/ERC721Enumerable.sol”;</blockquote><p><strong>Line 2. Include ERC721Enumerable in Contract Declaration</strong></p><blockquote>contract NFTContract <strong>is ERC721Enumerable </strong>{</blockquote><blockquote>}</blockquote><p><strong>Line 3. Set Max Supply in Contract</strong></p><blockquote>contract NFTContract is ERC721Enumerable {</blockquote><blockquote><strong>uint256 public constant maxSupply = x;</strong></blockquote><blockquote>}</blockquote><p>maxSupply will be referenced later and serves as the limit you want to set for how many NFTs can be minted from your contract. Adjust x to be the number of your choosing.</p><p><strong>Line 4. Function Requirement Statement</strong></p><blockquote><em>require</em>(totalSupply() &lt; maxSupply);</blockquote><p>The line above should be inserted into your minting function. totalSupply() is a helper function from ERC721Enumerable, which returns the value of how many tokens have been created from the contract over its lifetime. The require statement compares the total amount of tokens created to the limit and stops the function from being run if the total amount of tokens currently created is not below the max supply limit.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fd2f94a4002" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Save Solidity Contract Creator As Variable]]></title>
            <link>https://medium.com/@duckddev/how-to-save-solidity-contract-creator-as-variable-c1f2e5716788?source=rss-c5181e480791------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1f2e5716788</guid>
            <category><![CDATA[solidity]]></category>
            <category><![CDATA[solidity-tutorial]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[DuckDuckDev]]></dc:creator>
            <pubDate>Fri, 29 Apr 2022 00:25:21 GMT</pubDate>
            <atom:updated>2022-04-29T00:25:21.519Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Step 1. Setup Contract</strong></p><blockquote>pragma solidity &gt;=0.7.0 &lt;0.9.0;</blockquote><blockquote>contract Owner {</blockquote><blockquote>}</blockquote><p><strong>Step 2. Initialize Owner Variable</strong></p><blockquote>pragma solidity &gt;=0.7.0 &lt;0.9.0;</blockquote><blockquote>contract Owner {</blockquote><blockquote><em>address private owner;</em></blockquote><blockquote>}</blockquote><p><strong>Step 3. Set Owner in Constructor</strong></p><blockquote>pragma solidity &gt;=0.7.0 &lt;0.9.0;</blockquote><blockquote>contract Owner {</blockquote><blockquote>address private owner;</blockquote><blockquote><em>constructor() {<br>owner = msg.sender;<br>}</em></blockquote><blockquote>}</blockquote><p>Whether you’re trying to make it so that only the person who can deploy a smart contract’s funds can access certain functions or you want to have the wallet address of the contract creator to reference in the future, the above implementation will save the creator of a contract’s address as a Solidity contract variable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1f2e5716788" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OpenZeppelin Override TypeError Fixes]]></title>
            <link>https://medium.com/@duckddev/openzeppelin-override-typeerror-fixes-db7e571c39d9?source=rss-c5181e480791------2</link>
            <guid isPermaLink="false">https://medium.com/p/db7e571c39d9</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[openzeppelin]]></category>
            <category><![CDATA[bug-fixes]]></category>
            <category><![CDATA[solidity]]></category>
            <dc:creator><![CDATA[DuckDuckDev]]></dc:creator>
            <pubDate>Fri, 29 Apr 2022 00:15:33 GMT</pubDate>
            <atom:updated>2022-04-29T02:15:02.259Z</atom:updated>
            <content:encoded><![CDATA[<p>A few weeks ago, I was developing an NFT minting contract in Solidity utilizing the OpenZeppelin library. After attempting to compile a program with the following setup (irrelevant sections omitted), I received a series of type errors due to a conflict in functions when applying multiple OpenZeppelin extensions to the Solidity contract.</p><blockquote><em>pragma</em> solidity 0.8.1;</blockquote><blockquote><em>import </em>“@openzeppelin/contracts/token/ERC721/extensions/ERC721URIStorage.sol”;<br><em>import</em> “@openzeppelin/contracts/token/ERC721/extensions/ERC721Enumerable.sol”;</blockquote><blockquote>contract CompanionsNFT is ERC721URIStorage, ERC721Enumerable {</blockquote><blockquote>}</blockquote><p>Here’s how I solved each error.</p><p><strong>Error 1:</strong> “TypeError: Derived contract must override function “_burn”. Two or more base classes define function with same name and parameter types.”</p><p><strong>Solution:</strong></p><blockquote>function _burn(uint256 tokenId)<br>internal<br>override(ERC721, ERC721URIStorage)<br>{<br>super._burn(tokenId);<br>}</blockquote><p><strong>Error 2: “</strong>TypeError: Derived contract must override function “_beforeTokenTransfer”. Two or more base classes define function with same name and parameter types.”</p><p><strong>Solution:</strong></p><blockquote>function _beforeTokenTransfer(address from, address to,<br>uint256 amount) internal virtual override(ERC721, ERC721Enumerable) <br>{<br>super._beforeTokenTransfer(from, to, amount);<br>}</blockquote><p><strong>Error 3:</strong> “TypeError: Derived contract must override function “supportsInterface”. Two or more base classes define function with same name and parameter types.”</p><p><strong>Solution:</strong></p><blockquote>function supportsInterface(bytes4 interfaceId)<br>public<br>view<br>virtual<br>override(ERC721, ERC721Enumerable) <em>returns</em> (bool)<br>{<br><em>return</em> super.supportsInterface(interfaceId);<br>}</blockquote><p><strong>Error 4: </strong>“TypeError: Derived contract must override function “tokenURI”. Two or more base classes define function with same name and parameter types.”</p><p><strong>Solution:</strong></p><blockquote>function tokenURI(uint256 tokenId)<br>public<br>view<br>override(ERC721, ERC721URIStorage)<br><em>returns</em> (string memory)<br>{<br><em>return</em> super.tokenURI(tokenId);<br>}</blockquote><p><strong>Important Notes:</strong></p><ul><li>Each function‘s override parameters would likely need to be adjusted to the OpenZeppelin library that’s giving you a conflict. For example, ERC721Royalty instead of ERC721URIStorage. From my experience, console error logs return which parameters need changing in this case.</li><li>Each function manually overrides the conflicting function to solve the TypeError.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db7e571c39d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>