Skip to content
This repository has been archived by the owner on Mar 5, 2024. It is now read-only.

Latest commit

 

History

History
64 lines (49 loc) · 5.11 KB

saturn-v-tip.md

File metadata and controls

64 lines (49 loc) · 5.11 KB
Raw

Saturn-V TIP Proposal

Name

  • Saturn-V
  • Repo Name: saturn-v-tip

This is the first TIP proposal under the TSWG and it represents the next evolutionary step towards the moon shot known as decentralized identity. Acknowledging the recently successful NASA/Space-X mission that has revitalized attention to space exploration, history reveals that our early success in space was significantly aided by the Saturn V multi-stage rocket platform. The Saturn V three-stage rocket served as a Heavy Lift Vehicle for space exploration. It was the most powerful rocket that had ever flown successfully. The  Saturn V was used in the Apollo program in the 1960s and 1970s. It also was used to launch the Skylab space station. Containing three (3) powerful fuel-stages, this massive rocket was used to propel man to the moon. Since we are in the early stages of the technology adoption lifecycle for decentralized identity and we seek a technical recipe to bootstrap an interoperable digital trust marketplace. Analogous to the first three layers of the ToIP Stack, this initial TIP represents an exemplar of a technical collaboration to help propel decentralized identity into mainstream adoption. In fact the Saturn V project required that three separate companies, each responsible for a separate fuel-stage, collaborated to integrate their fuel-engines into a single interoperable rocket platform that would propel Appolo and Skylab missions. Today, we seek to integrate technology for three ToIP Layers to achieve a common goal -- help propel the adoption of digital credentials.

Purpose

Today, the decentralized identity community continues the moon shot started by the Sovrin Foundation towards self-sovereign identity. This proposal is unique as it represents a vertical interoperable stack that is already familiar to most industry participants. This proposal is effectively receiving the baton that began with the Sovrin Network and will focus on evolving that effort into a network of networks model.

Convener(s)

  • Stephen Curran (nominated)
  • Richard Esplin (nominated)
  • Dan Gisolfi

Stakeholders

The following vendors are activity working on interoperability in support of this TIP:

  • esatus
  • Evernym
  • IBM
  • Main-Incubator (R&D Unit of Commerzbank Group)
  • Telus/ATB-Financial
  • Trinsic

Key Motivators

List the reasons that triggered the proposal.

  1. We need to describe an example TIP that is of interest to many in the ToIP Foundation.
  2. As the Sovrin Community transitions under the broader umbrella of the ToIP Foundation, we need a description of the architecture in which the community desires to embrace.
  3. We need a methodology that will allow alternative TIPs to be compared to the one most familiar with many in the ToIP Foundation.
  4. We need a forum for the Indy Interop-athon events that are focused on making the network of networks concepts reality of public identity utilities based on Hyperledger Indy.

Core Principles

The stakeholders believe that the proposed technical stack is purpose built to provide the foundational infrastructure necessary to support the 10 Core Principles that were adopted by the Sovrin Foundation. As the decentralized identity community evolves into a network of networks model, these principles will help shape the applicability of solutions.

Principle Description
Existence Users must have an independent existence.
Control Users must control their identities.
Access Users must have access to their own data.
Transparency Systems and algorithms must be transparent.
Persistence Identities must be long-lived.
Portability Information and services about identity must be transportable.
Interoperability Identities should be as widely usable as possible.
Consent Users must agree to the use of their identity.
Minimization Disclosure of claims must be minimized.
Protection The rights of users must be protected.

Technical Stack Proposal

Identify the technologies associated with each layer of the ToIP Stack that will help to define this TIP.

ToIP Technical Stack Layer TIP Technology
Three Hyperledger Aries
Two Hyperledger Aries
One Hyperledger Indy

Use cases to be validated

In addition to the common business patterns associated with decentralized identity, namely password-less auth and digital onboarding, this TIP proposal will build on existing proof-points to establish a generalized list of uses-cases that will help to demonstrate cross-industry adoption.