Verifiable Credentials will play a key role in trust creation for generations to come. We invite developers across the world to come and build applications that generate secure, portable and privacy-preserving credentials enabling trust across entities.

What are we looking for? 

Your submission should be a Proof of Concept (PoC) application demonstrating a Verifiable Credential based use case that uses Affinidi's APIs and/or SDK.

The solution could be composed of portals or apps for issuer, verifier, and/or holder corresponding to your business use case.

Here are a few examples of Verifiable Credentials use cases:

1. Driver's License as a Verifiable Credential used to rent a car across geographies

2. Covid19 test results as Verifiable Credentials (QR code) to fly an airline

3. KYC data issued as a Verifiable Credential interoperable and accepted across different banks

Long list of verifiable credentials use cases: 25+ Use Cases of Verifiable Credentials

Categories

Developers have the possibility to submit solutions under the following categories

1. Healthcare 
2. Fintech
3. Open (other industries such as Education, Real estate, Travel, Retail, Insurance, International trade, etc.)

FAQs:

What are Verifiable Credentials (VCs)?

Verifiable Credentials are portable digital credentials that are cryptographically encrypted, interoperable and can be verified digitally on the internet. More here

What is an issuer, holder, and verifier?

1. Issuer: An entity that issues a credential. Eg: a test management facility like a hospital that issues a patient record like “Covid -ve“. Issuer has the right to revoke a credential

2. Holder: An entity that has lifecycle control over the issued credentials like sharing, deleting. Eg: A patient that holds a credential issued by an issuer on their wallet (a wallet could be an app that stores users credential data locally or a custodial wallet managed on behalf of a holder)

3. Verifier: An entity that verifies if the credential shared by a holder is valid (i.e. if the credential comes from a trusted issuer, not revoked by the issuer). Eg: An access management system installed at a facility like airport that allows / denies access based on if the holder is covid -ve/+ve. Verification could be a combination business logic like “is the credential is issued in the last 14 days” and “is it issued by an issuer that is recognized“

Note: One entity can play multiple roles. Eg: A hospital can play the role of a verifier and an issuer

What are the benefits offered by Verifiable Credentials?

Verifiable Credentials are:

• Tamper proof: Verifiable credentials cannot be tampered with 
• Portable: Easy to share with the click of a button or a few click(s)
• Verifiable: The verifier is able to verify the following aspects including
  • The issuer of the credential
  • Originality/authenticity of the credential
  • Validity of the credential

What does Affinidi offer developers?

Affinidi provides a set of APIs and an SDK that enable decentralised identity creation, verifiable credential issuance, cloud wallet storage, and verification.We have also created a postman collection with all our APIs for your convenience.

Affinidi’s stack contains:

1. Issuer utilities
2. Custodial wallet solution
3. Encrypted Data vault
4. API solutions for Issuers, Verifiers and Holders

---

About Affinidi

Affinidi empowers individuals and organisations with control of their verifiable data, to unlock value across platforms and geographies. Leveraging Affinidi's solutions, trusted institutions and entities can issue verifiable data to customers, which can in turn be shared with other service providers to access products and services in an open and interoperable manner.

Finally - Hackathons are meant to be an exploration of ideas, but also for everyone to have fun! Remember the hacker spirit - collaborate with your teammates, encourage the other teams, be open with your ideas, and have fun.

So, let's start building a PoC. Get started now!

$15,000 in prizes

• Use Case
  Does it solve an existing real-life problem? Is the problem clearly defined? Will the proposed solution make life better for its target audience? How easy is it for users to adopt and use it?
• Technology
  Does the PoC leverage Affinidi APIs and its open source stack? Are VC Schemas designed to be interoperable? Are consent and privacy built into the user journeys? (Bonus) Does the PoC leverage other non-Affinidi open-source SSI/VC components
?
• User Experience
  Is the userflow practical/realistic? Is the userflow designed to consider multiple scenarios? How well designed is the UI?
• Completion
  Is the Proof of Concept functional and fully working? Are different parties like issuer, holder, verifier able to interact with each other?