Decentralized Identifiers (DIDs) - These are like aliases for our existing addresses (Ethereum address, email address, website, Bitcoin address, etc.) that make it easy to prove ownership and control over other identifiers.
DID Method - There a number of different ways to create DIDs (over 100 in fact!) but because different types of identifiers (like Ethereum addresses or Bitcoin addresses) work slightly differently and are rooted in different system we need a set of rules about how to create and interact with DIDs made out of the different identifiers. A DID Method is simply those rules!
DID Document (DDO) - DIDs need DID Documents. A DID Document is a file that lists the current state of the DID as well as other public keys and endpoints for how to interact with that DID. The DID Document is where the magic of DIDs really happens!
DID Communication Protocol (DIDComm) - This is a protocol that allows two DIDs to open a secure channel between them and send messages back and forth.
Verifiable credentials are specially formatted data that you can put on your Disco profile. Think of them like a digital version 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 and because the credential is signed it means nobody can tamper with the credential.
Also Known As: Verifiable Credentials are the official name of the technical standard for this type of data but you might hear them referred to as Attestations, Claims, or even Badges.
Encrypted: A VC can be encrypted using the subject’s DID so that only the subject and the issuer know what is in the credential.
Credentials need to be stored somewhere! Because putting personal information on a blockchain ranges from suboptimal to dangerous (for a number of reasons), the credential needs to be stored somewhere else. Disco currently uses the Ceramic network for storage but will be integrating many different storage solutions over time.
Your data is yours! It’s the whole point of Disco. If you have a Verifiable Credential on your Disco profile, you can take your Verifiable Credentials along with you to unlock access in other apps and spaces. Because your VC is signed, encrypted and tamper-evident, you can safely for move it across storage solutions and environments without damaging its integrity.
Disco is here to enhance your privacy. By default, a credential that you receive is encrypted so that only you can see it. You can decrypt this credential and add it to your Disco profile so that the whole world can see it but then if you change your mind, you can re-encrypt the credential so that it is no longer on your profile. Just remember, once you make a credential public anyone can copy the data to an archive, that’s just the nature of the internet.
Sometimes referred to as the “Credential Holder”. The subject is the person or entity that a Verifiable Credential is written about. For instance, you are the subject of your Passport and your home country is the issuer.
A Relying Party is an individual or organization who relies upon data presented in a Verifiable Credential to inform app logic, unlock access to certain privileges, or other form of access enabled by data verification.
A schema is a template for a Verifiable Credential. For example, driver’s licenses, passports, or diplomas all contain similar data organized in similar ways. This allows relying parties to interpret them easily no matter who the issuer. Schemas allow us to do the same thing for Verifiable Credentials.
You can write Verifiable Credentials about yourself. This means that the issuer and the subject of the credential are the same — both you. Self-attested credentials are commonly used to assert personal preferences like your favorite color or music genre.
In the context of DIDs and VCs, a “signature” is a digital watermark on piece of data that is unique for every DID. The signature uses complicated cryptography to work but the end result is that someone who looks at the data that has been signed can trust that the data has not been altered in any way, additionally they can look at the signature and find out the DID that performed the signing.
Technically you can issue whatever credential you want, but it doesn’t mean others will recognize you as an authority for that credential and trust it. For example, I can create a diploma and sign it with my name, but no one will recognize me as a trusted source of that information! Additionally, Disco only offers the ability to issue a subset of the possible credential types via the Disco web app. This list will grow with time, but as a rule of thumb, only issue credentials that you are an authority for!
Right now we offer the ability to link together a few different types of accounts and identifiers: Twitter handle, Discord handle, and domain name. However, we will be expanding this list shortly to allow you to link many more different types of credentials.
Just for now! However, Disco’s aim is to create interoperability across lots of different ecosystems! In the near future you will be able to use Disco with wallets from a number of different blockchains and you will be able to present credentials issued to one blockchain identifier (like your Ethereum address) from a different blockchain identifier (like your Solana address)!