Deep Skills Protocol

  • Crypto / Web3

Updated 587 days ago

Ethereum · DAO / Community
Updated 587 days ago
Ethereum · DAO / Community


Professional Reputation Protocol


Our goal is to enable portability and verifiability of professional reputation to reduce the transaction costs of establishing trust. Whether you’re looking for job, want to hire a freelance, networking, looking for investor or mentor — professional identity will help you makes those decisions in an informed, quantifiable and cheaper way.

Problem Statement

Currently, professional reputation in web3 is limited by organizational domain. Although some reputation systems already exist (CoordianApe, Colony, Mazury), most of them are not interoperable and hard to use across multiple applications, blockchain ecosystems and DAOs.

Deep Skills Protocol solves these problems by aggregating multiple reputation systems, recording data in decentralized network. This way, professional identity data becomes reusable, portable and accessible by any application as long as user gives such permissions.

Solution Overview

Project Contains:

  • Multiple connectors (pulling data from connector specific data hub)
  • Issuer module: recieves data from trusted data connector and issue (sign) strctured Ceramic data according to the specific schema and store that data at the Ceramic Stream
  • Frontend App 1
  • Frontend App 2 (at this iteration just '../profile' page of main application)

Protocol supports flexible way of adding new data connectors. Currently supported connectors:

  • Github
  • Coordinape
  • Sourcecred
  • Discord
  • Poap

Solution architecture is available here:


We leverage IPFS store data in decentralized way, Ceramic Network to tie it to DIDs and give ability for any 3rd party application to request and re-use data, and Lit Protocol as permissions layer.


When designing the decentralized professional identity system, the following properties should be considered.

  • Decentralized — there is no single owner or beneficiary of the protocol; protocol should be governed by the builders and users
  • Permissionless — anyone is able to use the system
  • Composable — components of the system can be used for various use cases (hiring, networking, assessment, education) and can rely on external protocols (social graph, decentralized data storage, DIDs)
  • Privacy-preserving — protocol users should be able to change privacy settings based on who they want to be able to see their identity and reputation details
  • Affordable — the system should be free for identity holders and not prohibiting for other parties to use
  • Interoperable — the system should provide ability for 3rd party apps and protocol to leverage identities and data in the protocol

Team Information

Kishore — Integration, tech lead

Denis — Ceramic, Lit, overall architecture

Stepan — Data structure, user flows

Dima — frontend, backend, deployment