Design Schema for Backend

[pratiksardar]

DoD:
Enhance the image schema attached to cover all scenarios.

Personas :

1. Seller [Creates an Impact Product, Backend should save all the impact Products created by seller ] , this should save Date of selling(listing), address or seller etc refer sample initial - Seller will create Project(NFTs) should be albe to track how much is sold and earned,
2. Buyer

• Buys a NFT , Stakes it , Claims Rewards ,locks it , Unstake it.

3. Admin - For supporting analytics and all.

[tusharshah21]

I'd like to work on this issue as I have experience in designing scalable backend schemas. I plan to create a comprehensive data model covering sellers, buyers, and admins tracking NFT listings, sales, staking, rewards, and analytics support. Looking forward to contributing to the backend structure!

[Anuragyadav622003]

I'd love to work on this issue as I have hands-on experience with backend schema design and Prisma/SQL modeling. I plan to enhance the image schema to support NFT metadata, IPFS-based image sources, accessibility fields like alt, and token tracking. This will ensure better support for sellers listing impact NFTs, buyers interacting with purchases, and admins needing analytics. I'm confident in translating real-world personas into a scalable schema and can deliver clean, testable updates with proper documentation.

[gelluisaac]

Hi, I'm a software developer with a strong interest in NFT infrastructure and smart product ecosystems. I'm excited to enhance the image schema to support seller listings, buyer actions, and admin analytics. I’ll ensure schema flexibility for tracking NFT lifecycle—minting, staking, rewards, and more. My focus is on creating a robust, extensible schema that supports all personas seamlessly

Recommended by OnlyDust for high-quality and dependable contributions.

[Superior212]

Hi, I'm Superior!
With strong backend and Web3 experience, I’m ready to enhance the image schema to support all user scenarios.

My Approach:

1. Expand the image schema to cover all use cases for Sellers, Buyers, and Admins, ensuring it supports product creation, sales tracking, NFT actions (buy, stake, claim, lock, unstake), and analytics.
2. Ensure the backend saves all impact products with seller info, listing date, sales, and earnings.
3. Design schema fields for tracking buyer actions and admin analytics.
4. Deliver a robust, extensible schema with clear documentation.
5. Communicate progress and submit a well-structured PR.
   My experience ensures a scalable, future-proof solution. Looking forward to contributing!

[tusharshah21]

@pratiksardar can you please look into the PR and let me know if you need any changes

[tusharshah21]

@pratiksardar are you there mate?

[tusharshah21]

Hello @pratiksardar can you look into it mate!