ZKNW

Inspiration

Your concept focuses on simplifying the process where every user acts as a verifier, issuer, and holder in a decentralized system. By developing @tookey-io/piece-polygon-id, you aim to bridge the gap for common users by providing a no-code solution. This tool integrates with various data sources like Onchain Data, Google Sheets, Discord, Telegram, Airtable, and others, making it more accessible and user-friendly for people who aren't deeply versed in coding or blockchain technology. This approach could significantly lower the barriers to entry in the decentralized verification space.

What it does

How we built it

Preparation

I understand the main battlefield of DID and VC is authentication, such as membership, loyalty, governance. But it is soo boring to "real" to do in hackathon. Where else do issues of authentication and credibility arise? On social networks! Consider your LinkedIn connections, for example. Many of us have over 500 (I have almost 2,000), but how many are genuine connections, and what can we truly say about them? For me, it's next to none. Having 2,000 connections doesn't necessarily make me a more credible business partner compared to others. However, if a mutual friend shares something positive about me, that holds significantly more value.

An idea emerges from this. Let's construct our social profiles (DID) based on what our friends share about us in the form of Verifiable Credentials.

Tooling

I quickly realized there was a gap in tools for easily issuing Zero-Knowledge Verifiable Credentials (ZKVC) and linking them to user-managed validation logic. This is where a no-code tool becomes crucial. I developed a building block, Polygon ID, for Tookey Automation, enabling users to issue ZKVCs.

Proof of concept

ZKNW is a straightforward web-based application currently featuring two screens, with a third in development: 1) Creation of a claimable profile credential. 2) A page for claiming these credentials. 3) Profile page (COMING SOON) that will display a profile with partial disclosure, determined by the intersection of owner and visitor social networks. It will also feature a public overall text-embedding vector. This allows for searching profiles without revealing data and clustering networks to identify similar or diverse personas.

Challenges we ran into and accomplishments that we're proud of

1) Primarily reverse-engineered Web5.js protocols. Curious why all schemas aren't accessible? :) 2) Successfully integrated iden3comm and custom storages for @0xpolygonid/js-sdk (a challenging task).
3) Finally delved into working with DID (a concept I've been familiar with for some time).

What we learned

The documentation might not be crucial if the code is shared, but with PolygonID, why do not open source the verifier and mobile app? I'm struggling to understand how to generate the same key from an identical recovery phrase...

Built With

• typescript