A Web3-Based NFT Trading Platform.

dangee is a Web3-based NFT trading platform built on the Polygon blockchain. The Polygon blockchain, in particular, is used due to its compatability with Ethereum while featuring much lower gas fees.

Users are able to register onto the platform using Web3 Authentication (i.e., their wallets). Outside of authentication, the user is able to:

1. interact with the smart contract, and
2. mint and sell NFTs privately with other users/wallets.

Please make a MetaMask wallet, and add/keep the MetaMask wallet to your account:

There are two, technically three, roles on the smart contracts.

1. DEFAULT_ADMIN - the original creator of the contract (me)
2. MINT_ROLE - any users granted the ability to mint NFTs
3. users who are neither minters nor admins.

As the role names imply, an admin work with any method on the smart contract. Users with the MINT_ROLE role are able to mint NFTs. Note, these users cannot revoke nor grant MINT_ROLE access to other users.

The MINT_ROLE helps to gate access to minting only to those with permission. The goal is to protect dangee against spam minting. As of right now, the MINT_ROLE is granted to those who connect their wallet to the platform.

Future plans are to deploy dangee onto Microsoft Azure; however, as of yet, dangee remains on the localhost.

Please note that dangee is currently working on the Polygon PoS network, so all transactions and NFT minting occurring use real money.

For more information, refer to the website directory.

Please note that I used two now-deprecated technologies:
(1) Mumbai testnet - support ended as of April 8, 2024.
(2) hardhat-deploy - as of the latest hardhat version, hardhat-deploy has been phased out with Ignition

Solutions:
(1) To combat the Mumbai support ending, I deployed my smart contract to Polygon's PoS network.

(2) Unfortunately, while Ignition is much simpler than the historic hardhat-deploy, it does has been shown to have issues with Polygon's PoS network... which I'm using. Therefore, I ultimately resulted to testing in hardhat and deploying in RemixIDE.

For more information, refer to the smart-contract directory.