HashCred

Demo

About

The problem it solves ## Problem Statement In today’s digital landscape, **certificate forgery** has become a widespread and damaging issue. Educational qualifications, training credentials, and professional certifications are frequently falsified, eroding trust between applicants, institutions, and employers. Verification of legitimate certificates is **painfully slow and fragmented**: * **Closed, proprietary systems** limit access to verification tools. * **Inconsistent data formats** make interoperability nearly impossible. * **Manual verification processes** introduce delays that hinder hiring and admissions workflows. * **Privacy concerns** arise when verification systems expose personal data such as email addresses or ID numbers. Employers, recruiters, and institutions are left without a **unified, transparent, and tamper-proof framework** for verifying credentials. As a result, genuine candidates face longer processing times, while bad actors exploit the gaps to present fraudulent documents. This problem is not confined to academia — it spans **corporate hiring, online learning platforms, professional licensing, and skill-based training programs**. Without a modern, privacy-focused verification system, trust in digital credentials will continue to decline. > **HashCred** addresses this gap by delivering a blockchain-based, privacy-preserving platform that empowers institutions to issue verifiable credentials and enables employers to authenticate them instantly and securely.

How it's made

Challenges we ran into ## Challenges Faced During development, the team encountered several technical challenges, particularly around integrating advanced **SUI blockchain** features: 1. **Sponsored Transaction Integration** * Implementing sponsored transactions for zkLogin proved to be a significant hurdle. * The team initially struggled with understanding the transaction flow, byte serialization, and signature handling. * This was resolved by exploring an open-source GitHub repository provided by **Mysten Labs** and actively seeking guidance from the SUI community on Discord. 2. **Smart Contract Development** * While SUI Move provides robust tooling, designing and deploying contracts for certificate issuance required navigating a new programming model. * The team relied heavily on the **official documentation** and various **tutorials** to correctly implement the required smart contract logic and ensure interoperability with the front-end application. 3. **zkLogin Workflow Complexity** * Managing the interplay between ephemeral key pairs, epoch-based address rotation, and JWT-based zero-knowledge proof generation required deep understanding of the zkLogin protocol. * Iterative testing and debugging were essential to ensure that authentication remained both secure and user-friendly. Through these challenges, the team gained a deeper understanding of the SUI ecosystem, zkLogin’s authentication model, and the nuances of building a fully integrated Web3 application from the ground up.