Skip to main content

What is Disco? 🔮

Disco is identity simplified. We are focused on:

  • Interoperability: We are chain-agnostic and you can take your portable credentials anywhere!
  • Privacy: You are given the tools to consent to how information is shared and with whom. PII (Personal Identifiable Information) data is never committed to public blockchains.
  • Autonomy: You as the user, should be able to own your own data. You own your own keys and no central authority can revoke or censor this!

Identity as it is today

Centralized Identity

In the public Internet today, ownership of data/identity is currently controlled by incumbents and third-party companies. Every single account you make is a part of a separate service, and each purchase or preference is stored and captured in data silos. Who knows, they might even be selling it!

Identity on the internet as we know it today involves: going to Facebook/Twitter, and login with your username and password. You’re given a username and password to authenticate to each specific application or service. Not only do you have to keep track of all these logins, but you also don’t own any of your data! Sharing everything with everyone is obstructive, expensive, and exploitative.

Make your way to the dance floor: Disco time! 💃

Consolidate your Identity

Introducing, your own personalized Disco Data Backpack! 🎒

We believe that introducing yourself should be seamless in physical and digital reality. With Disco, you’ll be able to own your own identity and reflect yourself in the exact way you want, with maximum consent. In other words, only allowing companies/entities to see your data with your permission.

Yes, that’s right. You can own data about YOURSELF!

Think of this as a data backpack, holding various identifier cards representing membership, affiliation, licenses, education certificates, or any other aspects of non-financial data about yourself.

Let’s think about the properties of a backpack. You’ll be able to pull out its contents whenever you need them, and keep them securely stashed when you don’t. Similarly, with Disco, you’ll be able to own data about yourself in the form of credentials. You’ll be able to selectively present your credentials to verifiers (institutions, employers, etc) to unlock access to specific content, and/or prove who you really are!

It’s like going to a bar in the metaverse, and proving you are over 21, without having to show other aspects of your personal data like your address and DOB. And this is done all using cryptographic proofs, in a matter of milliseconds! Note that there will be no steps to write to the blockchain or buy any cryptocurrency. We take trust very seriously and will NOT ask for your seed phrase or to sign malicious messages.

Credential Example

Imagine the endless opportunities of unlocking access flows given simple presentation & verification steps:

  • An application to a job can be automated via verification of an online-course.
  • Create credential-unlocked content, Discord channels, or merch instead of buying tokens or NFTs .
  • No more forms!!

We get it, you’re excited. If you want to skip the reading and set up your backpack now, check out Getting Started here..

Have more questions? Ask us here.

Identity Legos 🧱

What pieces/primitives allow Disco to work under the hood?

This is all made possible via Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs)

A DID is:

  • an alias for our existing addresses (Ethereum address, email address, website, Bitcoin address, etc.) that make it easy to prove ownership and control over other identifiers.
  • self-generated + self-owned. It might look like like this: did:3xfdsafjlasla
  • They help us safeguard aspects of our digital presence via cryptography. Each wallet is unique to a single DID, like a keychain that holds many keys we need to use to access doors/entryways that are locked!
  • a non-centralized, universally discoverable way for you to ultimately own your credentials.

A Verifiable Credential is:

  • specially formatted data (JSON) that you can put on your Disco profile. Think of them like digital versions of your membership cards, IDs, library cards, or any other important document that you get from some other authority.
  • Signed. In most cases, a verifiable credential is cryptographically signed by one DID about another DID. Because the credential is signed, it means nobody can tamper with it.
  • Contains proof, or attestation about the recipient or user. I.e: Bob is a member of DAOHaus, or Boys Club. Bob’s diploma from Waterloo University, or course completion.
  • Is an open-source standard by the W3C Verifiable Credentials Data Model. It is a set of specifications and verifiable documentation that allow credentials to be verified and shared on the web.

Parties Involved 🥂

Great! Now that we’re familiar with these terms, let’s take quick look at the 3 parties involved.

Issuer -

Whoever is issuing a claim, or credential. This could be any governing body, entity, university, or organization! They’ll sign the claim with their public and private key-pairs so it’s legit.

Recipient -

Whoever is receiving a claim, or credential. They will ultimately own these credentials and control how it’s shared. They’ll have a DID so it’ll be unique to that address only.

Verifier -

An entity that verifies if the credential is authentic and valid. Typically, they’ll ensure that it is legitimate, tamper-proof, and is still relevant on the requested date.

Trifecta Verification

Let's take a look at an example.

Degen University (issuer) issues a diploma in the form of a VC, to Alex (recipient) about their graduation on a specific date. They use Disco to accept the credential, and can take that credential to apply to a job, and the employer (verifier) will verify the credential via Disco’s API endpoints.

Where does the inherent trust model come into play? Three things happen:

  1. Alex proves who actually issued the credential, since Degen University’s DID is uniquely owned by them.
  2. Alex owns the credential and is the subject of the claim (Degree in Arts, etc)
  3. The credential is valid, and the cryptography has not been broken.

What goes into a Disco profile?

Profile-Example With Disco, you can add more profile information, including a display name or nickname, bio, and profile picture! You’ll also be able to link your social accounts from Twitter, Discord, or even a DNS domain. By doing so, you’re strengthening your profile, and this will prove that you’re the unique person to own your account usernames, aliases, etc. The stronger the profile becomes, the easier it becomes to establish trust with other people, communities, and services.

As you begin to collect credentials, they’ll start to appear here under your Data Backpack. In this data backpack, you’ll be able to control who can see these credentials (public vs. private).

In each credential, you'll be able to see details like:

  • Issuer Details

  • Date Issued

  • Attestation/Proof/Achievement

Remember that this is all signed cryptographically and unique to you ONLY!

Next Steps

Stay Connected:

  • Here’s our blog for musings, news, and announcements!
  • Follow us on Twitter for updates.
  • Please reach out here for additional questions, comments, or concerns.

See you on the dance floor! ✌️