Motivation

The EIP-5539 draft proposes a new RBAC-enabled revocation registry that can be used by any valid Ethereum address to maintain a set of revocation lists. In those, arbitrary revocation keys can be marked as either revoked or not. Additionally, the registry includes a set of management features that enables owners to have features like delegates, owner changes, and meta transactions.

This repository includes a well-tested reference implementation that implements all described features in EIP-5539.

Concepts

$3

A namespace is a representation of an Ethereum address inside the registry that corresponds to its owners address. All revocation lists within a namespace are initially owned by the namespace's owner address. All namespaces are already claimed by their corresponding owners.

$3

A namespace can contain an (almost) infinite number of revocation lists. Each revocation list is identified by a unique key of the type bytes32 that can be used to address it in combination with the namespace address.

$3

A revocation list can contain an (almost) infinite number of revocation keys of the type bytes32. In combination with the namespace address and the revocation list key, it resolves to a boolean value that indicates whether the revocation key is revoked or not. Revocations can always be undone.

$3

An Ethereum address that has modifying rights to revocation lists within its own and possibly foreign namespaces. An owner can give up modifying rights of revocation lists within its namespace by transferring ownership to another address. The revocation list will still reside in its original namespace though.

$3

An Ethereum address that received temporary access to a revocation list in a namespace. It has to be granted by the current owner of the revocation list in question.

$3

Owners and delegates can provide a signed payload off-band to another address (transaction sender) that initiates the Ethereum interaction with the smart contract. This might be helpful for services providing easy-to-use access to the registry.

Usage in Verifiable Credentials

The usage in Verifiable Credentials is defined in the EthrRevocationRegistry2022 specification found here: https://spherity.github.io/vc-ethr-revocation-registry/.

Interacting with the Registry

Implementers can call all methods of the registry directly with already existing web3 libraries. Alternatively, the Typescript library Ethereum-Revocation-Registry-Controller can be used as an easy-to-use interface to interact with the registry. A plugin for resolving credential states in Veramo can be found here: https://github.com/spherity/ethr-revocation-registry-veramo-plugin

Contract Deployments

| Network Name | name | chainId | hexChainId | Registry Address | Registry version |
|--------------|---------|---------|------------|--------------------------------------------|------------------|
| Mainnet | mainnet | 1 | 0x01 |||
| Goerli | goerli | 5 | 0x05 | 0x185D1Cf733e2C85A7Eda4f188036baA5b7a11182 | 1.0.0 |

Development

$3

To get the test suite running you need a local instance of Ganache.
This projects supplies a docker-compose that starts up a local instance:

``
npm run init
`

The migration will deploy the contract to the local chain:

`
npm run migrate
`

Then you can generate the contract's types:

`
npm run types
`

Everytime you change something at the contract and the interface changes you need to rerun the type generation.

$3

To start the test suite, you can call:

`
npm run test
`

To get a coverage report you need to run:

`
npm run test:coverage
`

$3

The Truffle migration feature is used to deploy the contracts to the different networks which ensures that the logic and proxy contract get upgraded correctly. Fot MINOR version updates, the contracts .sol file can be edited directly. The the following process has to be followed:
1. Copy the X_upgrade_contract.ts file from the migrations folder to a new file with an increased number at the front and telling description.
2. Run npm run types to generate the types for the updated contract.
3. Run npm run migrate to deploy the new contract to the local network.
4. If everything works, commit your changes.

For MAJOR version updates, the following steps have to be followed:
1. Copy the RevocationRegistry.sol file to a new file with the new version number attached to it. (like RevocationRegistryV2.sol)
2. Copy the X_upgrade_contract.ts file from the migrations folder to a new file with an increased number at the front and telling description. ALSO: Reference the new contracts artefact that should be deployed.
3. Run npm run types to generate the types for the updated contract.
4. Run npm run migrate to deploy the new contract to the local network.
5. If everything works, commit your changes.

When creating a new release, a GitHub action will automatically upgrade the contract on the networks. The files in the networks and .openzeppelin` are needed for the migrations to keep track what contracts are deployed to what addresses on which networks. Don't modify or delete them. The updated versions of those files will be committed in a new pull request that needs to be merged by owners or maintainers.

$3

This repository has three deliverables with versions:

* node module
* contract
* contract types

All of these leverage semantic versioning.

#### Node Module
The node module version is separated from the other ones.

#### Contract
The contract's version will always be bumped in a major version when the public interface changes (public methods, public fields).
If this happens, a new contract file should be used with the changes you intend to apply.

#### Contract Types
The contract types version will follow the contract's version accordingly, but will only carry the
major version in their name (V1, V2).