Validating Resume using Ethereum and Polygon

Imagine a world where resumes are not just documents but verifiable proof of professional achievements. Enter our solution, utilizing Soul-Bound-Tokens (SBTs), a digital token system. Organizations issue SBTs representing specific experiences. Applicants securely store these in blockchain wallets, crafting resumes dynamically from chosen SBTs. Employers gain trust in the hiring process by reviewing resumes backed by tamper-proof SBTs. Join us in shaping the future of transparent and trustworthy professional credential verification.

• Polygon
• Solidity
• ZKP
• Hardhat
• Infura

• If you want to claim any issue (task), just reply with any message on that issue thread which justifies that you want to work on this issue. Ex :- Claim, I want to work on this issue, etc.
  
• Issues will be given out on first come first serve basis.
  
• In case of no activity on an issue even after 2 days, the issue will be reassigned. If you have difficulty approaching an issue, feel free to ask on our Discord channel.
  

• Fork the repository to your github account.
• Clone it to your local setup by using git clone <repo link>
• Navigate to the respective folder in which the code need to be updated or added.
• Do the necessary changes according to the issue assigned.
• All set! Once you are confident in your work, push your code and create a pull request (PR) to the main branch of the upstream repository with proper descriptions/comments in the code explaining what you did and wait until we review it.
• Single commit per pull request and name the commit as something meaningful.
• Reference the issue numbers in the commit message if it resolves an open issue.
• Strictly follow the template provided inside .github directory to make a PR.
• Make changes to the pull request if the reviewing maintainer recommends them.
• Do not use unnecessary variables or functions and follow a easy and understandable code structure with proper comments.
• Pull Requests older than 2 days with no response from the contributor shall be marked closed.
• Do not make PR which is not related to any issues.
• Avoid duplicate PRs, if need be comment on the older PR with the PR number of the follow-up (new PR) and close the obsolete PR yourself.
• Be polite and gentle to other community members.

If you have any doubt or suggestions regarding the project or it's any issue, feel free to ping us anytime in the Deresume channel of our Discord server.