Case Study: The Crop Collective Blockchain Development
THE CROP COLLECTIVE
BLOCKCHAIN DEVELOPMENT CASE STUDY
Web Design & Development
- Simple, catchy and easy to navigate
- Adaptation of look & feel for easy navigation on small mobile screen
- Loading speed as fast as 6.02 secondS
Smart Contract Development
Automatic execution as end users purchase NFTs directly from the Client
Metamask Contract Interaction
Accurate submission of transactions together with the related gas fees.
Integration to the Chainlink Ecosystem
Smoothly connecting the smart contract with off-chain ecosystem
Final Test Audit
- Final check by developers to remove bugs (if any)
- As a final check before launch, clients will also conduct a test to confirm if everything works well
Technology Stack
- SOLIDITY PROGRAMMING: For any EVM chain
- REACT JS: For front end web development
- PINATA CLOUD: For the IPFS storage
- AWS EC2: For cloud server
- AWS S3: For image and file server
- ETHEREUM (or any EVM chain): For the blockchain
- MORALIS DATABASE: For off-chain and on-chain data management
Proposed Architecture
ERC 721 Token Contract
- Beyond the responsibilities of a standard ERC721 token, it is used to lock and replace periphery contracts and control minting/burning
- Contains two main roles: Minter and owner
Seeder
- Determines traits during minting, and can be replaced to allow for future trait generation algorithm upgrades
- Currently, traits are determined using pseudo-random number generation
Descriptor
- Used to store/render artwork and build token URIs
- When token URI is called, NFT parts are read and converted into a series of SVG reacts, building a SVG image on-chain
- Once the entire SVG has been 4 generated, the token URI then consists of base64 encoded data URI with the JSON contents directly inlined, including the SVG image

