Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 23 additions & 1 deletion documentation/docs/concepts/trust-frameworks.md
Original file line number Diff line number Diff line change
@@ -1 +1,23 @@
# Trust frameworks
# Trust
Trust is hard. It becomes infinitely more challenging when we introduce strangers on the internet into the mix. We expect to have some certainty or confidence with claims made about an entity. As an example, a stranger claims they are a doctor. How do you know? Is it because they are wearing scrubs with a white coat? Is it the paper hanging on the wall? Could that document be fake? What makes us comfortable with a doctor claiming they are a doctor? In today's world, typically, it's an accumulation of things, referrals, an office, the equipment in the office, staff, attire, license on the wall, etc.

These things give us comfort and a sense that we are dealing with an entity claiming to be a doctor. Sure, it could be a scam, but there's a reasonable expectation this entity is a doctor. None of this exists in the digital world today, but in digital identity, it's necessary because it gives us comfort and some level of certainty in the digital world.

## Trust/Governance Framework
Trust is hard in the digital world, and this is where the role of a Trust/Governance Framework becomes useful. Before we begin, the terms Trust/Governance in this context are the same. Some prefer the word trust because governance implies government, which isn't necessarily the case.

A Trust/Governance Framework does govern an ecosystem. An example in practice today is a medical board. In the United States, states have a medical board that derives its authority from the state, typically via law or regulation. In a digital world, the state could issue the medical board a verifiable credential that is presentable and verifiable.

This board consists of legal experts and practicing attorney's this board agrees collectively to determine what qualifies a person to be a lawyer in that state. This board issues a law license or a verifiable credential to the attorney.

The attorney can then present that document or verifiable credential to clients, law firms, etc., for verification, typically through a website checking license number and name.

> We should have a diagram here showing a hierarchy. Will work on a doodle to provide to design.

## Trust registry
A trust registry exists because a Trust/Governance Framework creates and manages it. Its sole purpose is to make a transparent trail of trusted issuers and, in some cases, verifiers. Trust registries not only establish a mechanism to verify issuers and their authority, but it also keeps blockchain transactions to a minimum, keeping costs down.

> **Note:** Repositories are the best candidate for distributing a single source of truth across many sources and maintaining transparency. Another benefit of the repository is that the Trust/Governance Framework could have its governing rules and processes published, maintain a versioning history, and efficiently distribute updates.

> Will link to the PPPGF as an example.

2 changes: 0 additions & 2 deletions documentation/docs/concepts/what-is-digital-identity.md

This file was deleted.

35 changes: 35 additions & 0 deletions documentation/docs/concepts/what-is-identity.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# What is identity?
Identity is the essence of who we are. Identity consists of mutable and immutable traits. Immutable traits are sex, height, eye color, and genealogy. Mutable characteristics also contribute to our lives, such as where we bank, who we are insured by, where we are citizens, and where we went to primary, secondary school, and university.

Today, most mutable traits have a physical representation via a document issued by an appropriate authority that stores that information in a centralized storage medium (i.e., servers).

Identity is so ingrained in our daily lives we rarely think about how deeply intertwined with everything we do. When we get a driver's license, it is issued to us by a governing authority. Then, we may present that license to an entity that verifies the information on the document. The verifier trusts the issuer because, typically, physical copies have watermarks, seals, etc.

## What is Digital Identity?
Digital identity is a digital representation of an entity via a decentralized identifier (DID). An entity is a person, place, organization, digital or physical thing. Instead of physical documents, digital documents, called verifiable credentials, represent mutable characteristics.

## Principles of SSI
The roles we discussed in the driver's license example still exist in digital identity. It works similarly but with additional security, privacy, interoperability, portability, transparency, and agency layers. A key difference is that digital identity requires no central authority to provide an identity, nor is there any centralized registry.

> Figure x.x 12 Principles of SSI

## Using digital identity
### Holder
The term holder is an entity with a DID. Typically the DID is stored or held in a digital wallet. Every player in a digital identity ecosystem will have a DID.

> Figure x.x Holder, Wallet, DID

### Issuer
An issuer is an entity that issues verifiable credentials (VCs) to holders with whom they have a connection.

> Figure x.x Issuer, holder, VC

### DID pair
The connection between a holder and an issuer is unique. A DID pair represents each side of this relationship, one going to each entity. It is essential because neither party knows the other entity's DID, only the DID pair. This key point is a privacy feature ensuring that your doctor won't know where you buy books, the bookstore won't know where you buy groceries, etc.

> Figure x.x DID pair

### Verifier
The verifier verifies a VC presentation. There is an assurance question regarding the data presented and what would be acceptable to each verifier. For example, one verifier may accept verifying the issuing DID as being a proper authority for a specific type of credential, and another may require an additional check or knowledge of the information on the VC itself.

> Figure x.x Verifier, holder, issuer, trust framework, trust registry
15 changes: 14 additions & 1 deletion documentation/docs/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,17 @@ sidebar_position: 1

# Getting Started

Welcome to the ATALA Prism V2 SSI ecosystem! This guide will walk you through the process of setting up and using your digital identity within the ATALA Prism V2 ecosystem.
Atala PRISM is a decentralized identity platform. It is a layer-2 blockchain solution built upon Cardano. PRISM is rooted in the principles of self-sovereign identity (SSI). PRISM empowers users to own and control their identity, and personal information, which they can share securely, using private-key encryption, and privately opting with whom to share their data.

The documentation herein will explain the following:
* The concepts of SSI
* How PRISM works
* Setting up a PRISM environment
* Begin developing with PRISM

For a complete learning experience, including Q&A, workshops, and networking, we do have training available via the Atala PRISM Pioneer Program, which covers the following:
* Foundations of Self-Sovereign Identity
* Building with Atala PRISM
* Human-centric Design
To register interest in the program, register [here](https://atalaprism.io/#start-journey).