The following are a requirements for all submissions to this hackathon. 

• W3C-compliant verifiable credentials.

• 3-minute video describing what the app does and provide a URL to a public code repository.

• Text description of the project’s features and functionality.

• Explanation of how DIDs, VCs, and other requirements were used.

* Due to the uniqueness of their challenges DIDs and VCs are not required for submissions to Pinata and VCs are not required for NetSys. 

 

What to Build - Zero Knowledge Proofs in Self-Sovereign Identity Track

Sponsored by Privacy & Scaling Explorations

Overview

This track aims to foster innovation and collaboration among developers, researchers, and industry experts to advance the use of programmable cryptography in digital identity solutions.

Objectives

1. Innovate with ZKPs, MPC, FHE: Develop creative applications using programmable cryptography to enhance privacy, security, and interoperability in SSI systems.

2. Collaborate and Learn: Engage with zkp experts to learn about best practices, existing tools, and solutions.

Examples tooling and further track details can be found here.

 

What to Build - Future of Education & Workforce Track

Sponsored by Job for the Future Foundation and Digital Credentials Consortium

This challenge set is part of the Education Track, and invites you to explore a future where access to education is available to any learner and where education opens the door to economic advancement.

 

Challenges

The Future of Education & Workforce Challenge Set, sponsored by Job for the Future Foundation and Digital Credentials Consortium, invites participants to explore innovative solutions in education and workforce development. The challenges include:

1. Verifiable Learner/Worker IDs and Records Challenge: Demonstrate transformative applications when individuals control their own data, including learning and employment experiences.
2. Powerful New VC Tools: a) Multiple language support: Build tools for creating VCs in any language, promoting cross-border mobility. b) Browser Integration: Develop a browser plugin for improved VC display and verification.
3. Feature Enhancement: Improve existing tools (Learner Credential Wallet and VerifierPlus) to support rich credential displays using the renderMethod attribute.

Bonus Design Challenge: Explore ways to establish credibility in digital credentials, focusing on how humans can trust verification processes in a world of diverse VCs.

 

These challenges aim to leverage Verifiable Credentials to create more accessible, mobile, and trustworthy systems for education and workforce advancement.

Submission requirements

• Your submission must be open source, using the MIT license.

• It must use W3C-compliance Verifiable Credentials and meet technical interoperability standards used by JFF Plugfest.

Detailed requirements, examples, and tooling can be found here.

 

What to Build - Reusable Identity Track

 

Trinsic IDV Platform (Optional)

Trinsic is providing a sandbox identity verification product to hackathon participants for free. Through this sandbox, you'll have a global document verification product capable of verifying 16,000+ document types, including driver's licenses, passports, permanent resident cards, etc., along with liveness detection and biometric matching. In other words, a best-in-class identity verification tool to verify a user against their government ID.

Trinsic also allows identity verification through other reusable ID methods as well, such as mobile driver's licenses and verifiable credentials.

Demo

Trinsic recently recorded a webinar which shows the IDV product & how to integrate (includes samples, SDKs in the various languages, etc) The recording can be found here.

In order to be onboarded to Trinsic's IDV platform please send an email to hackathon@trinsic.id

 

Pinata File-Based Identity Solutions

Challenges include:

• Verifiable File Storage. Associate files to users via verifiable credentials. Both files and verifiable credential metadata can be stored publicly or privately using Pinata’s immutable Files API. In this challenge, you will demonstrate your creativity in usingimmutability and verifiable content hashes to solve a real-world problem.
• Proof of Personhood Credentials. In this open-to-interpretation challenge, we want to see creative solutions to personhood credentials that leverage immutable file storage. Participants can use private file storage through Pinata’s Files API or public file storage through Pinata’s IPFS pinning service.
• Identity-Based Access Controls For Private Files. Access controls are one of software’s ongoing challenges. In this challenge, participants should build an identity-based access control system for retrieving files stored privately on Pinata’s Files API. Note, this challenge should not use IPFS as IPFS is a public network. This should make use of private file storage through the Files API.

Submission requirements

• Must use Pinata to store and serve files: Each submission must use Pinata for filestorage and retrieval.
• Depending on the challenge, participants may be able to use IPFS and private files or just private files.
• Must focus on solving real-world problems: Submissions should focus on practical use cases and leverage creative solutions that include Pinata’s file APIs

The full list of tooling and docs can be found here.

 

ArcBlock

Overview

This challenge encourages participants to explore how DID/VC can be applied to real-world scenarios to address practical problems using ArcBlock's technology stack.

Challenge

Dive into the world of decentralized identity (DID) and verifiable credentials (VC) with ArcBlock's technology stack. This track challenges participants to develop innovative applications that solve real-world problems, leveraging the power of DID/VC to enhance privacy, security, and user experience in practical scenarios. The application can be anything; the only requirement is that it must utilize DID/VC and the ArcBlock technology stack

In addition all participants will receive a DID/VC based digital badge of “Proof of Participation” and all winning projects will receive:

• A DID/VC based digital certificate of winning

• Showcase in ArcBlock’s official blog, twitter and other social media accounts.

• Projects that can actually be useful will be accepted into ArcBlock’s official

          Blocklet Store

Submission requirements

• Use ArcBlock’s technology stack to build the application (include: DID:Connect,DID:Spaces, DID:Wallet, Blocklet, AIGNE etc.)

Tooling and support resources can be found here. 

 

Truvity

Overview:

These challenges invite participants to explore how decentralized identity and verifiable credentials can streamline complex eKYC processes and digital identity management using self-sovereign identity solutions. The challenges focus on building innovative applications that simplify the journey of individuals like Miko, an expat moving to Amsterdam, by leveraging digital wallets, to-do lists, and interlinked verifiable credentials.

To build the applications you need to leverage the Truvity SDK (available in TypeScript and Java).

What we are looking for:

• eKYC with Reusable Identity is a complex process involving many actors, processes, and documents. You can model the process from the perspective of an Issuer or a Relying Party (Verifier), but the most interesting part would be building the Expat Wallet that orchestrates the entire flow using a pre-built To-Do List.
• We've created many features to simplify this journey. Review them all and use as many as possible in your solution.
• You don’t need to focus on the real content of the documents; feel free to model them with few fields found online.

Challenge 1: Miko’s Journey to Amsterdam: Reusable Digital Identity for Expats

Challenge 2: eKYC: Compliance Officer Panel

Full challenge details can be found here.

 

TBD (Block)

tbDEX is an open messaging protocol that enables liquidity seekers to connect with liquidity providers. This means that as a liquidity provider, your business can be the backend supplier in several payment applications. 

Performing KYC on repeat customers every time they attempt to transact with you from a different payment app would be a pain. To avoid this, you will use the Web5 SDK to issue a Known Customer Credential (KCC) to a customer, Alice, who you have already completed KYC on. You will store the JWT representing the KCC in Alice’s Decentralized Web Node so that she can present it to your business from any payment app. 

Challenge 

1. Create a Decentralized Identifier (DID) and DWN to use as the Issuer.

2. Issue Alice a KCC that includes evidence. Note that for this challenge, you do not need to implement an actual identity verification flow. 

3. Install the VC Protocol onto your DWN so that you can communicate with Alice’s DWN. 

4. Obtain permission to write to Alice’s DWN by sending a GET request to https://vc-to-dwn.tbddev.org/authorize?issuerDid=${issuerDidUri} ;

5. Store the VC JWT of the KCC as a record in Alice’s DWN. 

Submit 

DWN Record ID of the KCC 

Additional Submission Requirements

Tooling and support resources can be found here. 

 

VIDOS 

Overview

This track invites participants to explore how decentralized identity, specifically leveraging DIDs (Decentralized Identifiers) and VCs (Verifiable Credentials), can be applied to innovative use cases in recruitment and reusable ID. Participants will utilize the Vidos tech stack and other tools from our partner network to build solutions that enhance security, efficiency, and user control in these domains.

Challenge 1: Employer Portal Using DIDs and VCs (Education track)

Develop a proof-of-concept ‘employer portal’ that enables recruiters to identify, verify, and onboard candidates through a seamless, decentralized identity system. The portal should integrate DID-based identity management and support the issuance and verification of VCs to streamline the hiring process. 

Challenge 2: VC Interoperability (Reusable ID track)

Develop a proof-of-concept solution that demonstrates the flexibility and interoperability of Verifiable Credentials (VCs) across multiple scenarios. Your solution should showcase how a single VC can be reused in different contexts, such as using a passport for both travel access and age-gated entry. Additionally, the solution should be capable of verifying similar credentials VCs from different issuers, e.g. passport credentials issued by different national authorities - highlighting the versatility of VCs in various real-world applications.

Submission Requirements

• Integration with the Vidos tech stack.

Key features, example use cases and tooling available here. 

 

Ontology

Overview

ONT Login is a decentralized universal authentication login component that helps developers shield the details of authentication implementation, and can quickly bring a Web 3.0 secure login experience to enterprises and services. It gives a great presentation of how reuseable identity can be applied in any Web2 / Web3 applications with the protection of users data and privacy. Currently, users need to log into the service via ONT ID. It is fully open source and supports multi-SDKs.

To optimize the developers’ building experience, as well as demonstrate its easy integration with any single app. We are inviting the developers to

• Make repo for the relevant technical documentation or its SDKs.
• Or provide a demo case for integrating ONT Login to their existing applications, say setting ONT Login as one of their user login methods.

Tooling available here. 

 

Crossmint

Overview

This track explores the concept of reusable digital identities that can streamline various

processes such as KYC (Know Your Customer), KYB (Know Your Business), reusable claims for

compliance, and age verification. The goal is to create robust and secure identity solutions that

can be reused across different platforms and services.

Challenge

Leverage Crossmint’s Verifiable Credentials API to develop a reusable identity solution that

addresses the challenges of identity verification and compliance in various sectors. The solution

should emphasize security, privacy, and ease of use for both individuals and organizations.

Examples and tooling available here. 

 

Anonyome

This challenge encourages participants to create innovative solutions using Personhood Credentials (PHCs) based on the W3C Verifiable Credentials standard. The focus of this challenge is to build solutions that demonstrate privacy, security, and usability of PHCs in decentralized identity ecosystems.

Background Reading: “Personhood credentials: Artificial intelligence and the value of privacy-preserving tools to distinguish who is real online” https://arxiv.org/pdf/2408.07892

Challenge​

Design and implement a privacy-preserving approach to PHCs. Submissions should demonstrate the following PHC capabilities:

1. Credential Issuance: demonstrate PHC issuance using the following guarantees
   1. Credential Limits: One PHC is issued per person (e.g., ensure not duplicates are created for a single individual)
   2. (Optional) Unlinkable Pseudonymity (privacy): enable a user to interact with services anonymously through a service-specific pseudonym
2. Credential Verification: Zero Knowledge Proofs: demonstrate a holder proving possession of a PHC containing one or more elements contained in the credential schema without disclosing the element itself. Capabilities may also include selective disclosure, unlinkable disclosure, or non-correlatable identification of holder or subject.
3. PHC Usage: demonstrate PHC usage by using at least one of the DIF foundational standards (e.g., DIDComm)
4. (Optional) Aries Cloud Agent – Python integration: demonstrate integrating PHC functionality within ACA-Py
5. (Optional) AnonCreds Implementation: demonstrate PHC implementation using the AnonCreds Specification.

See full details of challenge and tooling here. 

 

cheqd challenge

Overview

In a world where generative AI is increasingly a part of our lives, ensuring the authenticity and trustworthiness of data is crucial. Our challenge for you is to use cheqd’s decentralized identity stack to build Verifiable AI concept solutions that tackle emerging societal and technical challenges.

Challenge Title

“Harnessing Decentralized Identity for Verifiable AI”

Examples and tooling available here.

 

 

What to Build - Hospitality and Travel Track

 

NetSys| H&T SIG Challenge

Overview

Explore how Decentralised Identity technology combined with traditional travel tech

can help make travel more enjoyable and rewarding for everyone.

Challenge

Friction-free travel using traveler personal data and preferences

Using the power of Decentralized Identity technology, demonstrate one or more steps in a future, frictionless and connected travel journey (looking->booking->arriving->enjoying->departing-reminiscing->returning). Teams should demonstrate the reusability and portability of traveler information along the travel journey and the benefits accruing to the traveler, travel providers (Transport. Accommodation, tourism etc.) or destination (the location in which the travel takes place).

Sponsor-defined additional submission requirements:

• A profile is to be used to specify traveler personal data and preferences which may be self-attested by the traveler.
• Teams can use a traveler profile of their own design or may use preferences and DIDComm services provided by Autoura.me. 

Examples and tooling available here. 

 

Extrimian

Overview

Secure Hotel Check-in System Using Verifiable Credentials (VC)

Problem Statement:

Hotels handle sensitive guest information during the check-in process, making security a top priority. Your challenge is to design a secure check-in system for hotels that leverages Verifiable Credentials (VC) issued by the government. The government of the guest's country will issue a VC Passport for travelers, and when they check into a hotel, the hotel will verify their credential and check its status from a list (valid, invalid, or under review). This ensures a seamless, secure, and privacy-focused check-in process.

Requirements:

• Use ID Connect by Extrimian to create both the credential issuer (government) and verifier (hotel).

• The system must include the following components:

• Credential Issuer: The government entity issues the VC Passport to the traveler.

• Credential Verifier: The hotel validates the VC when a guest checks in, ensuring it is genuine and up-to-date.

• Status Check: The system should check the credential’s status from a status list

• Upon successful verification, the guest is cleared to check in.

 

Examples and tooling available here.