****Art and Development****
The scope of this proposal is for the development of a Gas Efficient Smart Contract capable of minting NFTs into the Opensea marketplace via a direct minting application on the client’s webpage. As well as physical creation of the NFT art assets. This process includes; Image/Metadata pairing and generation, IPFS pinning, ERC721 creation, DAPP Creation, a reveal mechanic, and then post-launch functionality on the website including collections and displaying in an array/grid.
3d Assets*: If 3d assets are decided, assets will be modeled/created in a commercially licensed version of Autodesk Maya (most 3d projects use pirated software, waiting for the crackdown on this). The assets are then loaded into the custom program where they are combined and converted into a Universal 3d file type capable of being displayed and interacted with on mobile devices, pc, mac, as well as the open-sea viewer page.
Images/Metadata pairing:
Regardless of traits decides or rarities tiers decide, all images will need to be organized and randomly paired to the metadata/token IDs. This involves scripting the images into predetermined categories, assigning the metadata to them, and then randomly pairing the metadata/image to a tokenID and then reconstructing the bunch as a whole. The timeline depends on the complexity of images and metadata.
IPFS Pinning:
All metadata and traits need to be pinned on IPFS before mint, as the contract points to specific IPFS addresses to display the NFTs and Opensea reads the metadata for display. If a revealing process is being done, the logic for this is extremely important in order to have a successful reveal and the contract must be written ahead of time.
ERC721 creation: The ERC721 is the smart contract that we are creating to mint our ERC721 NFTs. These contracts are extremely important and must be written ahead of time for any potential future functionality, so the roadmap or lifetime of the NFT is important here. You need to look ahead
and determine what you will need to include for any what if’s. Hundreds of hours of testing need to go into a smart contract before release to make sure it is not exploitable by users or other smart contracts. The same goes for the DAPP integration and testing.
DAPP:
The DAPP for this will be several-fold deep. Aside from a simple minting DAPP, we will need the DAPP functionality for the Array collection, future array collection minting, and any claiming portals for the ERC1155s. The front end of these is highly customizable, and the backend being the Metamask portion of it and the code to operate the DAPP functionality and have it access the proper contracts while ensuring a secure environment for the user.
... Show more