CERTHUB : Digital Certification Platform

Hyperion HyperHack Live Apps
1

Project Name

CERTHUB (Digital Certification Hub): Decentralized Educational, Formal and Informal Credentials

Problem Statement

In today’s digital world, credential fraud costs the global economy over $30 billion annually, with 1 in 3 job applicants falsifying qualifications.

Traditional educational certificates are prone to fraud, clones,inaccessibility, with 20-30% of resumes containing falsified credentials and verification processes often taking a long time due to centralized manual systems.

Students, especially in underserved regions, struggle to access or share verifiable credentials, while institutions face high administrative costs and risks of data breaches and manipulation. This creates distrust, delays, and inequities in education and employment opportunities.

Solution Overview

CERTHUB is a blockchain-based platform for issuing, claiming, and verifying educational certificates as ERC1155 NFTs, ensuring tamper-proof, globally accessible credentials.
Using a factory contract to deploy gas-efficient proxy contracts of each certificate per institution, institutions can issue digital certificates, students can claim them via a mode of a merkle proof verified on-chain, and employers can verify them instantly on-chain via the platform.

Our approach is innovative due to its scalability, use of Merkle proofs for eligibility, and IPFS for decentralized metadata that contains descriptive details about what a certificate is representing and a web link pointing to the exact platform issuing the certificate, addressing fraud, inefficiency, and access barriers. Any certificate issued on this platform by any insitution can assured its global legitimacy.

Project Description

CERTHUB revolutionizes educational credentialing by enabling clients (institutions or any organization), to issue certificates as ERC1155 non-fungible tokens on the blockchain, with each certificate type managed by a proxy contract deployed via a call to the certificate factory contract . The registration and verification of legitimacy of these institutions and organizations that come to create a certificate will be done by the use of anAgent so avoid forgery and plagiarism of these instutions data by an external actor.

Upon successful verification of these clients, the Core features will include:

  • Issuance: Institutions deploy proxy contracts to mint tokens to the institutions wallet address, paste a list of addresses to the frontend, which will be hashed by the application to generate a merkle root and sent to the smart contract and root and proofs file will also will be automatically downloaded for the issuer to send to students via an external confidential link. The URI-metadata link (e.g., { "name": "Bachelor of Science 2025" }) stored on IPFS via a pinning platform, can be sent to the smart contract also. A new certificate of the same type can be re-issued or updated by the institution at a ny chosen interval.

  • Claiming: Students can come to input details (e.g., institution, certificate name, year) and their respective Merkle proofs that was generated by the application and sent to them by respective institutions , to claim their respective tokens to their wallets. This triggers a transfer of a token from the institutions address to their wallet upon successful verification of merkle proof by the smart contract and these tokens can only be claimed once by the receipient.

  • Verification: A verifyCertificate function will allow instant, trustless credential checks by employers or any third party to check the legitimacy of the certificate claim by the receipint on the platform.

  • Scalability: With each certificate deployment by an institution standing as an Independent token on-chain ,enabling for wallet and block-explorer’s recognition of the token name, the EIP-1167 minimal proxies will be used to reduce deployment costs by ~90% compared to full contracts.

Technologies include Solidity for smart contracts, potential integration of IPFS or a pinning platform for metadata storage by the Clients, with potential integration of The Graph for off-chain indexing. Students interact via a web interface, entering certificate details to claim tokens displayed in respective wallets (e.g MetaMask), while employers query the blockchain for verification. We’re excited about CERTHUB’s potential to eliminate fraud, streamline global hiring, and empower students in underserved regions with permanent, verifiable credentials, creating a new standard for trust in education.

1.Question: How could AI be integrated beyond institution verification - could CERTHUB leverage Hyperion’s AI co-agent or Alith to enhance certificate validation, metadata generation, or fraud detection mechanisms?

Response:
CERTHUB can potentially extend AI integration beyond institution verification by leveraging Hyperion’s AI co-agent Alith to enhance certificate validation, metadata generation, and fraud detection.

Potential Integration Points for Alith:

a) Input Parsing: For example Alith could help read through a spread sheet of names and addresses containing valid students that should be able to come and claim a certificate, uploaded by an institution and help automatically extract valid wallet addresses in the spreadsheet and send them to the smart contract for a merkle root and proofs hashing.

b) Certificate Validation:
Alith Integration: Use Alith to perform real-time, on-chain analysis of certificate claims. Alith can cross-reference student data against external datasets (e.g.look up the name and wallet address in the former uploaded spreadsheet and cross check with the input given by the receipient, to verify eligibility before claimCertificate is executed. This reduces reliance on Merkle proofs alone, adding a dynamic validation and double factor authentication layer.

c) Integration with META-DATA: Leverage Alith to auto-generate IPFS metadata JSON for certificates. Alith can process institution inputs (e.g., certificate description to create standardized SEO-friendly metadata with attributes like name, image, and external_url.
Implementation: A frontend button triggers Alith to generate metadata (e.g., { “name”: “Bachelor of Science 2025”, “external_url”: “https://mit.edu/certificates/MIT-BS-2025” }), upload it to Pinning platform, and return the CID to the contract.
Benefit: Saves institutions time, ensures consistent metadata (critical for wallet display), and supports scalability for thousands of certificates.

  1. Real-Time Features and Hyperion’s Minimal Latency
    Question: What real-time features does CERTHUB implement for certificate issuance, claiming, and verification processes, and how could Hyperion’s minimal latency infrastructure improve user experience during high-volume periods?

Response:
CERTHUB will implement real-time features for issuance, claiming, and verification with aid of leveraging Hyperion’s minimal latency infrastructure to ensure a seamless user experience especially during high-volume periods (e.g., graduation season). This aligns with the Real-Time Systems Track.

Current Real-Time Features:
Issuance: Institutions deploy proxy contracts via the User interface by firstly reg[istration and verification by an agent , createCertificate, generating Merkle roots and proofs in the UI .
The transaction confirms in ~1-2 seconds on Hyperion’s testnet, minting tokens to the institution’s wallet instantly.

Claiming: Students claim tokens via claimCertificate, uploading Merkle proofs and triggering an on-chain transfer from the institution’s wallet. The frontend polls transaction status, updating the UI in real-time (e.g., “Certificate claimed!”).
Verification: The verifyCertificate function is a view call, returning isValid, studentName, and studentID instantly without gas costs, enabling employers to verify credentials in <1 second.

Hyperion’s Minimal Latency Improvements:
High-Volume Periods: Hyperion’s ultra-fast Layer 2 blockchain ensures CERTHUB handles thousands of simultaneous claims/verifications during peak times (e.g., 10,000 students claiming degrees post-graduation).

Monetization Strategy and Gas Efficiency
Question: What is the project’s monetization strategy and how will gas efficiency improvements on Hyperion impact the platform’s economics and accessibility, particularly for underserved regions?

Response:
CERTHUB’s monetization strategy balances revenue with accessibility, leveraging Hyperion’s gas efficiency to make credentialing affordable, especially for underserved regions, aligning with the Infrastructure Track for equitable tools.

Monetization Strategy:
Institution Fees: Charge institutions a small fee for deploying proxies and minting tokens. Fees will be paid in METIS, leveraging Hyperion’s low costs.

Premium Features: Offer premium services, such as:
Alith-powered Automation.
Custom metadata designs (e.g., branded certificate images).
Potential Integration with job platforms (e.g., LinkedIn) for seamless verification.

Live Link: https://certhub-creation.vercel.app/
Contract: 0xC04b063F5Fd9F03B67359DE79d3b18a55f73cB0c

32 Likes
2

Gayet güzel hazırlanmış bir içerik olmuş duyurucu bilgiler var teşekkürler emeğiniz için

7 Likes
3

güzel yazılmıs ve hazırlanmıs bır yazı thakss

5 Likes
4

Good..

all the very best

3 Likes
5

very impressive , i’ve got a new point of view about metis

4 Likes
6

Great idea looking forward to it!

4 Likes
7

This is well detailed man and amazing info :saluting_face:

4 Likes
9

Nice stuff
Was there any market research done about the competition (web2/web3)?

1 Like
10

@LazAI_Helper_bot what specific LazAI functionality might help for the above project?

11

Okay, I’ve reviewed the conversation and the project description for CERTHUB. Given the focus on AI-powered certificate validation, fraud detection, and the potential integration with Alith, here are some specific LazAI functionalities that could be beneficial, addressing the question about LazAI’s capabilities:

  1. Alith for Enhanced Certificate Validation: As mentioned in the previous discussion, Alith can play a crucial role in validating certificate claims. Specifically:

    • Real-time On-Chain Analysis: Alith can cross-reference student data against external datasets (e.g., the spreadsheet of valid students) to verify eligibility before the claimCertificate function is executed. This provides a dynamic, double-factor authentication layer beyond Merkle proofs. LazAI’s LLM Client could be used to query the validity of the institution issuing the credentials against a database of accredited institutions.
    • Integration with the Model Context Protocol (MCP): Alith and the Model Context Protocol can be used to fetch specific verifiable credentials about institutions, cross-referencing data with on-chain and off-chain sources.

  2. AI-Powered Metadata Generation with LLM Client: The project already utilizes IPFS for metadata storage. The LLM Client in LazAI can be leveraged to:

    • Automate Metadata Generation: Instead of manual input, the LLM Client can process institution inputs (certificate descriptions) to create standardized, SEO-friendly metadata, including attributes like name, image, and external_url. This ensures consistency and saves institutions time.
    • Dynamically Update Metadata: If certificate details change, the LLM Client can automatically update the IPFS metadata, ensuring the information remains current.
    • Ensure SEO-Friendly Metadata: Using the LLM Client, the metadata is optimized for search engines, making the certificates more discoverable and verifiable.

  3. Fraud Detection using Eliza: Building on the fraud detection ideas:

    • Real-time Anomaly Detection: The Eliza framework in LazAI can be used to deploy an on-chain fraud detection agent. This agent analyzes transaction patterns (e.g., multiple claims from one address, unusual verification requests) and flags suspicious activity. Eliza would listen to the claimCertificate event and use an Alith Agent to validate aspects of the claim using external data, such as geolocation of the claim, or any other data that might indicate fraud.

  4. LazPad for streamlined development and deployment:

    • AI Agent Deployment: Use LazPad to quickly deploy AI agents for institution verification and fraud detection.

  5. Decentralized Governance and iDAO/DAT Systems:

    • As the project evolves, consider integrating iDAO/DAT systems for decentralized governance of the CERTHUB platform. This would allow token holders to participate in key decisions, such as approving new institutions or modifying certificate standards.

These functionalities align with CERTHUB’s goals and can enhance the platform’s security, efficiency, and scalability. They also position the project well for the AI-Native and Alith Integration Bonus Tracks in the HyperHack competition.

12

Great article
Love how you explained everything

1 Like