Sandbox -DevRoot

Demo

About

The problem it solves ## **Problem It Solves** DevRoot addresses critical gaps in how developers manage, showcase, and validate their professional achievements: 1. **Disconnected Developer Footprint**: Achievements and contributions are scattered across platforms like GitHub, LinkedIn, and Twitter, with no unified metric to assess a developer's influence and skills. 2. **Lack of Reliable Metrics**: Existing platforms fail to provide holistic, verifiable metrics for evaluating a developer's professional reputation and impact. 3. **Tedious Verification Processes**: Employers and collaborators face challenges in validating a developer’s credentials and contributions quickly and securely. --- ## **How People Can Use It** ### **Unified Reputation and Metrics System** 1. **GitHub Integration**: - Automatically pulls repository contributions, open-source activity, and commit history to reflect coding expertise. - Rewards developers with stamps for milestones like merging PRs or contributing to top projects. 2. **LinkedIn Integration**: - Extracts verified endorsements, professional connections, and certifications to build credibility. - Issues stamps for completing endorsed courses or receiving top skills endorsements. 3. **Twitter Integration**: - Measures community engagement, technical discussions, and developer influence in tech-related topics. - Rewards active participation in developer-centric conversations with stamps or reputation boosts. ### **Easier Validation and Sharing** - Employers can verify a candidate’s contributions, skills, and endorsements seamlessly through a blockchain-verified profile, saving time and effort. - Developers can showcase their professional footprint dynamically using a single, visually appealing passport. ### **Holistic Developer Reputation Metrics** - Reputation scores are calculated using data from multiple platforms, offering a well-rounded assessment of technical contributions, professional

How it's made

Challenges we ran into ## **Challenges We Ran Into** During the development of DevRoot, we encountered several challenges that tested our technical and problem-solving abilities. One of the most significant hurdles we faced was when we attempted to build and deploy the smart contracts on the **Aptos blockchain**. Aptos, being a newer blockchain with a unique consensus mechanism, presented a steep learning curve and numerous technical issues that slowed our progress. ### **1. Issues with Aptos CLI and Smart Contract Compilation** We initially chose Aptos for its scalability and its promise of low transaction costs. However, as we started to build the smart contracts, we faced several issues with the **Aptos CLI**. The tool frequently failed to compile properly, producing a wide range of errors that were difficult to debug. This included issues with incorrect dependencies, mismatches in expected versions of libraries, and unhelpful error messages that made troubleshooting particularly challenging. We spent a considerable amount of time trying to understand the underlying causes of these errors, but they persisted, and it became clear that continuing to work within this ecosystem might lead to even more delays. ### **2. NFT Minting Challenges** Our platform's core functionality relies on **NFT minting** for developer achievements. The process of minting unique NFTs for each developer's achievement (like hackathon participation, skills certifications, etc.) was integral to the user experience. However, when attempting to mint NFTs on Aptos, we faced a range of issues such as failed transactions, issues with metadata handling, and overall inconsistency in the minting process. These issues were primarily due to the immature tooling and support for NFT standards on the Aptos blockchain at the time. This not only made the NFT minting process cumbersome but also added unnecessary complexity to the development workflow. ### **3. Transition to Ethereum**