Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CIP: Sybil Passport Definition #92

Open
michaelsena opened this issue Mar 4, 2021 · 0 comments
Open

CIP: Sybil Passport Definition #92

michaelsena opened this issue Mar 4, 2021 · 0 comments

Comments

@michaelsena
Copy link
Member

michaelsena commented Mar 4, 2021


cip:
title: Sybil Passport
author: Michael Sena, Kevin Owocki, Joel Thorstensson
discussions-to:
status: Idea
category: Standards
type: RFC
created: 2021-03-04
requires:
replaces:

Simple Summary

Sybil passport definition defines an IDX record that stores a list of verifiable claims that represent anti-sybil scores for a DID.

Abstract

TODO.

Motivation

Web3 has an anti-sybil problem. Many different applications are trying to solve this in various ways, including Gitcoin and BrightID as two examples. Both of these services want to make this reputation data available to users via IDX. Sybil passport definition aims to solve this by defining an IDX record where these verifiable claims can live.

Specification

The Sybil Passport document is a definition that contains an array of objects. Each entry represents a sybil score claim issued by some issuer or service.

Definition content

Deployment: <definition-DocID>

{
  "name": "Sybil Passport",
  "description": "A collection of anti-sybil scores",
  "schema": "<record-schema-DocID>"
}

Record Schema

The record schema defines a document which maintains an array of JSON objects that represent a sybil claims. Below find the fields that are contained in each object.

Property Description Value Max Size Required Example
issuer Entity that issued the claim string 150 char required https
format Format of the claim string 150 char required Ceramic, JWT
claim The payload string 450 char required JWT payload or CeramicURL

Deployment: <record-schema-DocID>

TODO

Rationale

Backwards Compatibility

Implementation

Security Considerations

Copyright

Copyright and related rights waived via CC0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant