Ariadne Identity Core Specification

Author: Yarmo Mackenbach
Version: 1
Last updated: 2022-09-01

Abstract

Status

This version of the specification is a draft. It is not recommended to base implementations on this version.

Copyright notice

Copyright (c) 2022 Yarmo Mackenbach. All rights reserved.

1. Introduction

Explain basic idea. Cryptography, identity, decentralized.

2. Identity claims

Claims are just URLs or URIs, links to account pages.

3. Identity proofs

Proof is data that verifies the claim. Can be plaintext or JSON.

3.1. Plaintext proofs

Plaintext proofs are just URIs of cryptographic fingerprints.

3.2. HTTP proofs

HTTP proofs are URLs that return cryptographic fingerprints as headers.

HTTP proofs should be URLs that contain some identity verification logic.

Aliases are allowed. Redirect page of your choosing DIRECTLY to the profile page. Multi-redirects strictly prohibited.

4. Identity verification process

Describe steps to perform an identity verification. Analyze claim, fetch data, find proof.

4.1. Server-side proxies

Use server proxy when needed. Inform users when proxies are used.

5. Profiles

Combine claims with cryptography to create Ariadne profiles.

5.1. OpenPGP profiles

OpenPGP keys, claims are notations inside them.

5.2. Signature profiles

Cryptographic signatures, claims are lines of text.

6. Service provider definitions

A preconfigured list of supported service providers. See ARCs on Ariadne website.