# anoncreds-revocation

**Repository Path**: hyperledger/anoncreds-revocation

## Basic Information

- **Project Name**: anoncreds-revocation
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: Apache-2.0
- **Default Branch**: main
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2023-07-12
- **Last Updated**: 2025-06-22

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# AnonCreds Revocation

![AnonCreds Logo](/spec/images/logo/hl_anoncreds_colour.svg)

This repository contains the requirements for a verifiable credential revocation
scheme suitable for use with AnonCreds. We are looking for a replacement for the
[AnonCreds v1.0 Revocation Scheme], known formally as CKS Signatures. The
existing scheme is not sufficiently scalable and privacy preserving for the
anticipated "jurisdiction-level" use cases for AnonCreds--one or more
credentials for every resident of jurisdiction. In looking for a replacement, we
need to define what the requirements are for a sufficiently privacy-preserving
and secure scheme. The purpose of this repository is to capture and document
those requirements.

[AnonCreds v1.0 Revocation Scheme]: https://github.com/hyperledger/indy-hipe/blob/main/text/0011-cred-revocation/README.md

- This work is being conducted under the [Community Specification License v1.0](1._Community_Specification_License-v1.md)
- The draft specification can be found here: [https://hyperledger.github.io/anoncreds-revocation/](https://hyperledger.github.io/anoncreds-revocation/)
- The source specification documents can be found here: [Specification Source](/spec)

This repository contains guidelines for [contributing](#contributions) to the specification and submitting [edits via GitHub pull requests](/EditingTheSpec.md).

## Background

The scope and background for this work can be found in the [Scope](2._Scope.md) in
this repository. The <tl;dr> summary is the following:

We are looking for a replacement for the [AnonCreds v1.0 Revocation Scheme], known formally as CKS Signatures. The scheme is not sufficiently scalable and privacy preserving for the anticipated "jurisdiction-level" use cases for AnonCreds--one or more credentials for every resident of jurisdiction. In looking for a replacement, we need to define what the requirements are for a sufficiently privacy-preserving and secure scheme.

## Contributions

This work is being carried out under the [Community Specification License
v1.0](1._Community_Specification_License-v1.md). Any person or organization
willing to adhere to this license is welcome to participate in this Working
Group and contribute to the development of the specification. Please read the
[Contributions](6._Contributing.md) document in this repo for details. For those
unfamiliar with the Community Specification License, you can think of it as
analogous to an open source code license, such as Apache 2.0, but for
specifications.

All participants in this working group must follow the group's [Code of Conduct](8._Code_of_Conduct.md).

## Meetings

Meetings of the Working Group are held weekly on Mondays at 7AM
Pacific/Vancouver time. That is 16:00 CET for most of the year, except for the
periods around the daylight savings time changes. Meeting details, agendas,
notes and links to the recordings are posted on the repository Wiki (to be done).

## Working Group Communications

The working group has an [AnonCreds Specification](https://discord.com/channels/905194001349627914/1037471404586709042) Discord channel for participants. Invitations for those interested: [https://discord.gg/hyperledger](https://discord.gg/hyperledger).