opencodeiiita / deresume Goto Github PK

View Code? Open in Web Editor NEW

9.0 2.0 20.0 221 KB

Validating Resume using Ethereum

License: MIT License

JavaScript 68.98% HTML 22.34% CSS 0.32% Solidity 8.37%

hardhat infura polygon reactjs solidity opencode23

deresume's Introduction

DEresume

Validating Resume using Ethereum and Polygon

Description

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.

Tech Stacks

Polygon
Solidity
ZKP
Hardhat
Infura

Claiming an issue

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.

Guidelines

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.

Communication

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.

deresume's People

Contributors

Stargazers

Watchers

deresume's Issues

Task-4

Develop logic to make SBTs non-transferrable. Also, the mint function can only be called by institutes that were registered in the institute.sol.
NOTE:- 1. Here you will use the institute.sol that is given in the smart-contracts folder not the ones you have created individually.
2. Use the ERC721 to make SBTs.

task-7

What should be the commands for the compilation and deployment of contracts in the Hardhat environment? We have deploy.js as our deployment script for the contract.
Note:- make your txt files with your names on it in task-7 folder

Task-5

Enhance the sbt contract for Soul-Bound Tokens (SBT) with improved metadata, refined transfer logic, event logging, token expiry, potential external data integration, and gas efficiency.

Details:

Improved Metadata:

-Expand metadata details for a richer representation of professional experiences.
-Include additional fields such as location, skills acquired, or any pertinent information.
2. Refined Transfer Logic:

-Revise the transfer logic to accommodate specific conditions.
-Allow transfers only when certain criteria are met, enhancing control over token ownership.
3. Event Logging:

-Implement Solidity events for crucial actions like minting a new SBT or transferring ownership.
-Ensure comprehensive event logging for transparency and traceability.
4. Token Expiry:

-Introduce an expiration date for SBTs to manage the token lifecycle.
-Implement logic to prevent actions, like transfers, after the specified expiration date.
5. Potential External Data Integration:

-Explore the possibility of integrating an oracle or an external data source.
-Dynamically fetch and display real-time information related to professional experiences in the token metadata.
Gas Efficiency and Optimization:

Optimize the contract for gas efficiency, considering gas costs for common operations.
Explore potential optimizations to reduce transaction costs and enhance overall efficiency.

Design task

Create a React.js webpage to explore and display existing Soul-Bound Tokens (SBTs) associated with the user's Metamask wallet. Additionally, link preexisting webpages in the frontend folder.

Tech Stack:
Frontend: React.js, Redux (optional), React Router
UI: Material-UI or Ant Design
Styling: CSS
Details:

-Link Preexisting Pages:

Connect and link preexisting webpages in the frontend folder.
-SBT Explorer Webpage:

Develop a React.js webpage for exploring and displaying SBTs.
Implement Metamask connectivity for user authentication.
-Display User's SBTs:

Create a section displaying user-specific SBTs with relevant details.
-Responsive Design:

Ensure a responsive design for a seamless user experience.
Also make contributions in contributors folder.
You must also make a deploy.js file after hardhat compilation and select network as polygontestnet

Task-2

Make a meta mask wallet id connect to web3 and develop an authentication system using metamask and fetching the users wallet address

Task-1

Make a smart contract in solidity for institute registration with their wallet addresses, descriptions, and name of the institute with a function that tells that this particular address belongs to a institute

Task-3

ERC-721 Implementation

Implement the ERC-721 standard for the Soul-Bound Token (SBT) contract using OpenZeppelin's ERC721URIStorage.sol.
Make the solidity file in your names folder inside the contributors folder. You can add the skill parameters by observing the frontend page for sbtissue in the frontend folder.
NOTE:-you only have to make an ERC-721 token which can be used as a professional skill credential not a SBT .You will only name the file as sbt.sol.