How nikhildsahu/e-certify works
Project type and purpose
• From the README and file tree, E-Certify is a blockchain-based DApp for online certificate issuance, storage, sharing and validation.
• It uses React.js for the front end, Ethereum smart contracts (via Truffle) for on-chain logic, IPFS for document storage, and Firebase for OTP-based authentication.
File structure
• Top-level directories:
• contracts/ (solidity source & Truffle migrations)
• e-certify/ (Truffle React “client” with compiled contract JSON artifacts)
• src/ (React application: App.js, Auth/, Institute/, Student/, CommonComponents/, Routes/, utils/)
• public/ (static HTML, manifest)
• img/ (screenshots)
• Solidity/ (version notes)
• Key patterns:
• No traditional server—front end talks directly to the blockchain and IPFS.
• Separation of UI modules by user role (Student vs. Institute).
• Utilities for Web3, IPFS, and Firebase live under src/utils, Fire.js, ipfs.js, getWeb3.js, web3.js.
README for additional insights
• Confirms DApp on Ethereum using MetaMask.
• Documents multi-sig wallet creation for each student/institute pair.
• Specifies Truffle for contract management and local development console.
• Emphasizes local encryption then upload to IPFS, followed by on-chain hash storage.
a. Main components
• React Single-Page App (src/)
• MetaMask / Web3 Provider
• Ethereum Network (local Ganache/Truffle or testnet via Infura)
• Smart Contracts (Migrations.sol, SimpleStorage.sol, MultiSig.sol)
• IPFS Network (document storage)
• Firebase Auth (OTP service)
b. Relationships and interactions
• User ↔ React SPA
• React SPA → MetaMask → Ethereum smart contracts (RPC calls)
• React SPA → ipfs.js → IPFS API (upload/download encrypted certs)
• React SPA ↔ Fire.js → Firebase OTP service for signup/login
• Smart contracts emit events → React SPA listens for on-chain updates
c. Architectural patterns
• MVC-like separation in the front-end (components, routes, state management via Web3 hooks)
• “Smart contract as backend” – no centralized server; on-chain logic
• Asynchronous promise-based flows for blockchain and IPFS calls
• Multi-signature wallet pattern for joint student/institute approvals
d. Relevant technologies/frameworks
• React.js, JSX, CSS (UI)
• Truffle (contract testing, migrations)
• Web3.js, getWeb3.js (Ethereum integration)
• IPFS API (via ipfs.js)
• Firebase Auth (via Fire.js)
• MetaMask extension (provider)
Details
• Truffle migration process as part of the development pipeline.
• Multi-sig approval flow between student/institute wallets.
• Do not omit the Firebase OTP handshake step in the authentication flow.