rebase December 2022
Chang & Steele Informational [Page]
Workgroup:
none
Authors:
W. Chang
Spruce
O. Steele
Transmute

Rebase

Abstract

Rebase project aims to establish reputation-based Public Key Infrastructure on the Internet by allowing people and organizations to link their various public, semi-public, and private accounts to cryptographic keys at their own will, also ensuring privacy.

▲

Table of Contents

1. Notational Conventions

The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this document, are to be interpreted as described in [RFC2119].

2. Vision

Through community agreed-upon data schemas and verification algorithms, Rebase aims coordinate decentralized web-based services that allow people and organizations to map their identities to cryptographic keys using social media in a user-centric and publicly auditable way. A network of independent validators will inspect identity proofs hosted across a variety of social media platforms, such as GitHub, Twitter, Hacker News, Reddit, and BrightID. Validators will issue credentials to people and organizations as authenticated by their listed keys, verifiable using the identity proofs. As a result, users will enjoy increased data portability within Rebase-compatible systems, meaning that they can take their digital identities anywhere they want and manage them however they choose.

3. Scope of Work

This group is open to anyone interested in solving PKI for the Internet by making existing online reputations and user data portable.

The Rebase project will:

3.1. Out of Scope

The Rebase project will not:

  • Sign specific vendor contracts or business deals;
  • Pursue concrete opportunities for commercial licensing;
  • Pursuing explicit marketing or business development activities from private companies.

4. Terminology

4.1. Open API

This Open API Specification 3 defines all JSON-Schema in YAML.

4.2. JSON-LD Context

This is the root context for rebase, it defines all terms used by rebase.

Implementations are expected to cache this json / bundle it with their apps.

Implementations SHOULD NOT download this from the internet.

5. Credential Types

The credential type schemas maintained here are exposed via Open API Specification 3.0.

The links maintained below provide term definitions for all defined semantics.

5.6. Notational Conventions

The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this document, are to be interpreted as described in [RFC2119].

6. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.

Authors' Addresses

Wayne Chang
Spruce
Orie Steele
Transmute