This EIP proposes a set of methods and standards for a role-based registry of indicators aimed for usage in revocations.
Revocation is a universally needed construct both in the traditional centralized and decentralized credential attestation. This EIP aims to provide an interface to standardize a decentralized approach to managing and resolving revocation states in a contract registry.
The largest problem with traditional revocation lists is the centralized aspect of them. Most of the world's CRLs rely on HTTP servers as well as caching and are therefore vulnerable to known attack vectors in the traditional web space. This aspect severely weakens the underlying strong asymmetric key architecture in current PKI systems.
In addition, issuers in existing CRL approaches are required to host an own instance of their public revocation list, as shared or centralized instances run the risk of misusage by the controlling entity. This incentivizes issuers to shift this responsibility to a third party, imposing the risk of even more centralization of the ecosystem (see Cloudflare, AWS). Ideally, issuers should be able to focus on their area of expertise, including ownership of their revocable material, instead of worrying about infrastructure.
We see value in a future of the Internet where anyone can be an issuer of verifiable information. This proposal lays the groundwork for anyone to also own the lifecycle of this information to build trust in ecosystems.
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
This EIP specifies a contract called EthereumRevocationRegistry that is deployed once and may then be commonly used by everyone. By default, an Ethereum address MAY own and manage a multitude of revocation lists in a namespace that MUST contain the revocation states for a set of revocation keys.
An owner of a namespace MAY allow delegates to manage one or more of its revocation lists. Delegates MUST be removable by the respective list's owner. In certain situations, an owner MAY also want to transfer a revocation list in a namespace and its management rights to a new owner.
namespace: 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.revocation list: A namespace can contain a 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.revocation key: A revocation list can contain a 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.owner: 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.delegate: 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.MUST implement a function that returns the revocation status of a particular revocation key in a namespace's revocation list. It MAY also respect the revocation lists revocation status.
MUST implement a function to change the revocation status of a particular revocation key in a namespace's revocation list
OPTIONAL implements a function to change the revocation status of a particular revocation key in a namespace's revocation list with a raw signature.
OPTIONAL implements a function to change the revocation status of a particular revocation key in a namespace's revocation list by a revocation list's delegate.
OPTIONAL implements a function to change the revocation status of a particular revocation key in a namespace's revocation list with a raw signature.
OPTIONAL implements a function to change multiple revocation statuses in a namespace's revocation list at once.
OPTIONAL implements a function to change multiple revocation statuses in a namespace's revocation list at once with a raw signature.
OPTIONAL implements a function to change multiple revocation statuses in a namespace's revocation list at once by a revocation list's delegate.
OPTIONAL implements a function to change multiple revocation statuses in a namespace's revocation list at once with a raw signature generated by a revocation list's delegate.
OPTIONAL implements a function that returns the revocation status of a particular revocation list in a namespace.
OPTIONAL implements a function to change the revocation of a revocation list itself. If a revocation list is revoked, all its keys are considered revoked as well.
OPTIONAL implements a function to change the revocation of a revocation list itself with a raw signature. If a revocation list is revoked, all its keys are considered revoked as well.
OPTIONAL implement a function to change the revocation status of a revocation list. If a revocation list is revoked, all keys in it are considered revoked.
OPTIONAL implement a function to change the revocation status of a revocation list with a raw signature. If a revocation list is revoked, all keys in it are considered revoked.
OPTIONAL implements a function to add a delegate to an owner's revocation list in a namespace.
OPTIONAL implements a function to add a delegate to an owner's revocation list in a namespace with a raw signature.
OPTIONAL implements a function to remove a delegate from an owner's revocation list in a namespace.
OPTIONAL implements a function to remove a delegate from an owner's revocation list in a namespace with a raw signature.
MUST be emitted when changeStatus, changeStatusSigned, changeStatusDelegated, changeStatusDelegatedSigned, changeStatusesInList, changeStatusesInListSigned, changeStatusesInListDelegated, or changeStatusesInListDelegatedSigned was successfully executed.
MUST be emitted when changeListOwner or changeListOwnerSigned was successfully executed.
MUST be emitted when addListDelegate or addListDelegateSigned was successfully executed.
MUST be emitted when removeListDelegate or removeListDelegateSigned was successfully executed.
MUST be emitted when changeListStatus or changeListStatusSigned was successfully executed.
This section uses the following terms:
transaction signer: An Ethereum address that signs arbitrary data for the contract to execute BUT does not commit the transaction.transaction sender: An Ethereum address that takes signed data from a transaction signer and commits it wrapped with its own signature to the smart contract.An address (transaction signer) MAY be able to deliver a signed payload off-band to another address (transaction sender) that initiates the Ethereum interaction with the smart contract. The signed payload MUST be limited to be used only once (Signed Hash + nonces).
The signature of the transaction signer MUST conform EIP-712. This helps users understand what the payload they're signing consists of & it improves the protection against replay attacks.
This EIP RECOMMENDS the use of a dedicated nonce mapping for meta transactions. If the signature of the transaction sender and its meta contents are verified, the contract increases a nonce for this transaction signer. This effectively removes the possibility for any other sender to execute the same transaction again with another wallet.
This provides every Ethereum address a reserved space, without the need to actively claim it in the contract. Initially addresses only have owner access in their own namespace.
The change of an owner of a list shouldn't break the link to a revocation key in it, as already existing off-chain data may depend on it.
No backward compatibility issues were found.
The signature of signed transactions could potentially be replayed on different chains or deployed versions of the registry implementing this ERC. This security consideration is addressed by the usage of EIP-712
The different roles and their inherent permissions are meant to prevent changes from unauthorized entities. The revocation list owner should always be in complete control over its revocation list and who has writing access to it.
Copyright and related rights waived via CC0.