How laitazidan/blockchain-certficate-verification works
Project type and purpose
• This is a full-stack blockchain-enabled certificate issuance and verification system.
• The “frontend” is a React/Tailwind/Vite web app for users to generate and validate certificates.
• The “backend” is a Python service (likely using Flask or FastAPI) that exposes REST endpoints, handles certificate cryptography, persists data in MongoDB, and mediates with the blockchain.
• The “blockchain” folder contains a Truffle project defining and deploying a smart contract (CertificateVerification) on an Ethereum-compatible network.
File structure
• Top-level:
• backend/ – Python API, crypto utilities, routes, Mongo driver, static assets.
• blockchain/ – smart contract code, build artifacts, migrations, tests, truffle config.
• frontend/ – React components, pages, styling, build config (Vite, Tailwind, Flowbite).
• test/ – end-to-end tests for the API and smart contract.
• backend/crypto and backend/database signal separation of concerns (cryptography vs. storage).
• backend/routes maps to logical API endpoints: activity, blockchain interactions, certificate issuance, verification, and a route to serve the frontend.
• blockchain/ using Truffle indicates an Ethereum development flow: compile, migrate, test.
(empty) README
• No high-level architecture section provided—so we’ll rely on the structure and file names for guidance.
Detail
• Call out environment config (.env) feeding credentials/keys into the backend.
• Public/private key files under “Crypto module” as assets used for signing.