Future of Education & Workforce
Tracks: Education & Workforce
Register: DevPost
Informational Session: Watch the recording
DIF Hackathon Discord Channel: #education-track
Website: JFF
Tracks: Education & Workforce
Register: DevPost
Informational Session: Watch the recording
DIF Hackathon Discord Channel: #education-track
Website: DCC
Challenges
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 include:
- [C 1] Verifiable Learner/Worker IDs and Records Challenge
- In this challenge, the reward will go to the most compelling demonstration of transformation possible when people can control their own data, including learning and experiences. You will develop examples of Verifiable Credentials representing Student IDs, Employee IDs, and Employment History and demonstrate their use in areas like the following (or others): proof of employment history to apply to a new job, access to platforms demonstration of essential skills, and applications of selective disclosure.
- [C 2] Powerful New VC Tools
- [C 2a] Multiple language support: promote mobility by allowing education credentials to be meaningfully used to access cross-border opportunities. This challenge must make use of the renderMethod attribute and enable VCs to provide multiple language support. Build a tool that lets people construct VCs in any language, especially those using non-Latin script.
- [C 2b] Browser Integration: improve convenience and usability for displaying and verifying VCs by building a browser plugin. This challenge must make use of the VC renderMethod attribute.
- [C 3] Feature Enhancement
- [C 3a] Add support for the Learner Credential Wallet to use the VC renderMethod attribute to support rich displays of credentials in the application.
- [C 3b] Allow VerifierPlus to use the renderMethod attribute to support rich displays, including PDF
- [Bonus Design Challenge] Establishing Credibility in Digital Credentials:
- Context: Verifying a digital credential like Verifiable Credentials involves a series of checks performed by software libraries. Some of these are common across all Verifiable Credentials, such as checking that the credential hasn’t been tampered with, hasn’t been revoked, etc. Other checks are specific to the use case, such as checking if the issuer is an authorized issuer of the credential type.
- Challenge: The question is this – in a world where verifiers, or consumers of VCs, may be consuming a broad array of credentials, often with a human in the loop, how does the human know that the verification check is valid? What is the equivalent of the “browser padlock” for Verifiable Credentials? This challenge invites you to explore how organizations can integrate use of VCs into their processes in ways that humans can have confidence in the results.
- This challenge can be stacked on top of one of the above challenges, but not standalone.
Prizes
Total: $15,000 USD
Prize Breakdown
| Challenge | Sub-Challenge | Place | Prize |
|---|---|---|---|
| Challenge 1 | - | 1st place | $2,500 USD |
| 2nd place | $1,000 USD | ||
| 3rd place | $500 USD | ||
| Honorable Mention | $100 USD | ||
| Challenge 2 | Challenge 2a | 1st place | $2,000 USD |
| 2nd place | $750 USD | ||
| 3rd place | $200 USD | ||
| Honorable Mention | $50 USD | ||
| Challenge 2b | 1st place | $2,000 USD | |
| 2nd place | $750 USD | ||
| 3rd place | $200 USD | ||
| Honorable Mention | $50 USD | ||
| Challenge 3 | Challenge 3a | 1st place | $1,500 USD |
| 2nd place | $500 USD | ||
| 3rd place | $150 USD | ||
| Honorable Mention | $50 USD | ||
| Challenge 3b | 1st place | $1,500 USD | |
| 2nd place | $500 USD | ||
| 3rd place | $150 USD | ||
| Honorable Mention | $50 USD | ||
| Bonus Prize | - | - | $500 USD |
Submission requirements
Your demonstration must be open source, using the MIT license.
It must meet technical interoperability standards used by JFF Plugfest. That includes:
- Credential Format: Open Badges 3.0
- This uses the Verifiable Credential format
- If your project issues credentials (use one of):
- VC API, with CHAPI - Credential Handler API if needed, or
- OpenID for Verifiable Credential Issuance
- If your project exchange (“presents”) credentials (use one of):
- You may reuse and build on top of the tools provided by the Plugfest, including:
Additional resources are available here at the JFF Plugfest 3 site
Submission requirements
- Must meet technical interoperability standards used by JFF Plugfest
- W3C-compliant verifiable credentials.
- 3-minute video describing the application and its functionality.
- URL to the public code repository.
- Text description of:
- Project's features and functionality.
- How DIDs, VCs, and other submission requirements were used in the application.