How sachincoder1/ecommerce-dapp works
Project Type and Purpose
• This is a full-stack decentralized e-commerce DApp.
• Frontend: Next.js + Tailwind CSS + Material-Tailwind, Web3 integration via ethers.js.
• Blockchain “backend”: Solidity smart contract, Hardhat for development/deployment, testing with Chai, deployed to Polygon (Alchemy RPC), IPFS for image/metadata storage.
Main Components
a. Frontend Application
• Next.js pages and React components under frontend/pages, frontend/components, frontend/subcomponents.
• State/context in frontend/context/MainContext.js.
• Web3 interface via ethers.js in wallet connector (WalletConnect.jsx).
• Calls out to blockchain through an RPC provider (Alchemy) and interacts with IPFS for metadata.
b. Smart Contract Layer
• Solidity contract(s) in blockchain/contracts.
• Deployment scripts in blockchain/scripts/deploy.js using Hardhat.
• Hardhat config (hardhat.config.js) defines networks (local, polygon).
• Unit tests (blockchain/test/Ecommerce.test.js) validate contract behavior.
c. Storage & External Services
• IPFS for decentralized image/metadata storage (upload in admin flow).
• Alchemy (Polygon Mumbai) as JSON-RPC provider.
• Hardhat local network for development/testing.
Relationships & Data Flow
• User/Admin in browser → Next.js UI → ethers.js calls → Polygon RPC (Alchemy) → Smart Contract → on-chain state.
• Admin UI also uploads to IPFS → returns CID → stored in smart contract via a transaction.
• Frontend queries smart contract for product list, order history; fetches metadata from IPFS using CID.
• Hardhat scripts deploy contracts to target network; tests run against local Hardhat network.
Architectural Patterns & Design Principles
• Separation of concerns: UI vs. blockchain logic vs. storage layer.
• DApp pattern: “UI → Web3 Provider → Smart Contract.”
• Context-driven state management in React.
• Config-driven deployment (Hardhat + Next.js configs).