How itsaaryan/skillset-verified works
Main Components
• Frontend (React Application):
• User interface built using React (the “src/” folder contains pages, components, and asset files).
• The components include specialized views for Admin, Employee, and Organization Endorser roles; chat features; QR scanning; and analytics (charts and graphs).
• Integration with MetaMask for login/authentication.
• Blockchain Layer (Smart Contracts and Migrations):
• Smart contracts deployed on the Ethereum network (files in “src/abis” such as Admin.json, Employee.json, OrganizationEndorser.json, and others).
• Migration scripts (in the “migrations” folder) and the Truffle configuration (truffle-config.js) that manage contract deployment.
• Firebase & External API Services:
• Firebase as a backend service (see “src/firebase/firebase.js” and “src/firebase/api.js”) likely used for the chat system and real-time notifications.
• Mention external API calls (such as retrieving Codeforces, HackerEarth, or other coding platform ratings) for displaying platform ratings.
• CI/CD and Deployment:
• Integration with GitHub workflows (under “.github/workflows”) and deployment onto Azure Static Web Apps.
• Mention configuration files that support the build and deployment process (like package.json, web.config, etc.).
Relationships and Interactions
• The Blockchain Layer for executing smart contract functions via MetaMask.
• Firebase/external APIs for chat messages, notifications, and rating integrations.
• That the Blockchain layer (smart contracts) controls the core business logic for skill endorsements, certifications, and role management.
• That user interactions (e.g., sending a chat, requesting endorsements, generating/reading QR codes) involve communication flows between the UI, blockchain operations, and Firebase.
Architectural Patterns and Design Principles
• Separation of concerns: Clearly distinguish the presentation layer (React components/pages) from the decentralized business logic (smart contracts) and the backend services (Firebase & external API integrations).
• DApp Integration: Show the MetaMask and blockchain connection as a dedicated interface, ensuring that the end-user’s interactions are secure and verified.
• Use of CI/CD: Emphasize automation in deployments to Azure using GitHub workflows, which streamlines development and ensures consistency.
Relevant Technologies, Frameworks, and Libraries
• React.js for the UI.
• MetaMask for decentralized authentication.
• Ethereum smart contracts (with Truffle for deployment and migration).
• Firebase for real-time functionality like chat and notifications.
• External API integrations for verifying platform-based ratings.
• Azure Static Web Apps for hosting.
• Additionally, mention utility libraries (e.g., for QR scanning or charting) where relevant.
• It should illustrate the secure login via MetaMask that then routes transactions to smart contracts on the blockchain.
• Additionally, show the support for notifications and chat being powered by Firebase along with external API integrations for rating validations.