Resume Validator
Web3 Resume Validation: Secure, Verified, and Blockchain-Powered!
Created on 23rd March 2025
•
Resume Validator
Web3 Resume Validation: Secure, Verified, and Blockchain-Powered!
The problem Resume Validator solves
Problem Statement
In the current job market, employers face challenges with:
-Verifying the authenticity of resumes and credentials.
-Time-consuming and costly background checks.
-Identifying falsified or exaggerated information.
Solution: Resume Validator DApp
The Resume Validator DApp addresses these issues by:
1.Blockchain-Based Resume Verification:
-It stores the resume hash on the blockchain, making it tamper-proof and immutable.
2.Instant Verification:
-Employers can quickly verify the authenticity of resumes by matching the hash with the stored record.
3.Privacy and Security:
-Only the resume hash is stored, ensuring data privacy while confirming authenticity.
4.Decentralized Validation:
-Eliminates the need for third-party verification services, making the process more transparent and efficient.
Use Cases
-Job Applications: Candidates can validate their resumes, and employers can instantly verify their authenticity.
-Educational Institutions: Universities can store credential hashes, simplifying future verification.
-Freelance Platforms: Freelancers can validate their portfolios, enhancing trust with clients.
Benefits
-Faster Verification: Reduces the time and cost of background checks.
-Tamper-Proof Records: Ensures resume data cannot be altered.
-Decentralized Trust: Removes the need for third-party validators.
-Efficient Hiring: Streamlines the verification process, making hiring faster and more reliable.
Challenges we ran into
One of the major hurdles was dependency conflicts when installing packages. The project initially faced multiple peer dependency issues due to version mismatches between react, react-day-picker, and date-fns. This caused installation errors and prevented the DApp from running smoothly. To resolve this, we used the pnpm package manager, which handled the dependencies more efficiently. However, even with pnpm, we faced ignored build scripts and unmet peer dependencies. We tackled this by manually approving the build scripts and forcing the installation with the --force flag to bypass conflicts.
Another significant challenge was connecting the blockchain backend with the frontend. Integrating ethers.js and ensuring the smart contract deployed on Hardhat interacted correctly with the React-based UI required debugging and configuring the ABI and contract address properly. We resolved this by thoroughly verifying the smart contract deployment, matching the contract address, and refining the connection logic in the frontend.
Lastly, we faced minor issues with Tailwind CSS configuration, where some custom styling was not applied due to incorrect import order. We resolved it by rechecking the Tailwind config file and ensuring proper class usage.
Overall, overcoming these challenges improved our understanding of managing blockchain-based applications, handling dependency conflicts, and ensuring smooth frontend-backend integration.
Tracks Applied (1)
Edu Chain Semester 3 Hackathon
EDU Chain