-
Notifications
You must be signed in to change notification settings - Fork 460
Commit
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,13 @@ | ||
--- | ||
eip: 7734 | ||
title: Decentralized Identity Verification (DID) | ||
description: A standard for decentralized identity verification on the Ethereum blockchain. | ||
author: Anushka Yadav <[email protected]> | ||
discussions-to: https://ethereum-magicians.org/t/erc-7734-decentralized-identity-verification-did/20392 | ||
eip: xx | ||
Check failure on line 2 in ERCS/erc-7734.md GitHub Actions / EIP Walidatorpreamble header `eip` must be an unsigned integer
Check failure on line 2 in ERCS/erc-7734.md GitHub Actions / EIP Walidatorfile name must reflect the preamble header `eip`
Check failure on line 2 in ERCS/erc-7734.md GitHub Actions / EIP Walidatorpreamble header `eip` must be an unsigned integer
Check failure on line 2 in ERCS/erc-7734.md GitHub Actions / EIP Walidatorfile name must reflect the preamble header `eip`
|
||
title: Decentralized Identity Verification (DID) Standard | ||
Check failure on line 3 in ERCS/erc-7734.md GitHub Actions / EIP Walidatorpreamble header `title` value is too long (max 44)
Check failure on line 3 in ERCS/erc-7734.md GitHub Actions / EIP Walidatorpreamble header `title` should not contain `standard` (or similar words.)
Check failure on line 3 in ERCS/erc-7734.md GitHub Actions / EIP Walidatorpreamble header `title` value is too long (max 44)
Check failure on line 3 in ERCS/erc-7734.md GitHub Actions / EIP Walidatorpreamble header `title` should not contain `standard` (or similar words.)
|
||
description: A standard for decentralized identity verification on the blockchain. | ||
Check failure on line 4 in ERCS/erc-7734.md GitHub Actions / EIP Walidatorpreamble header `description` should not contain `standard` (or similar words.)
Check failure on line 4 in ERCS/erc-7734.md GitHub Actions / EIP Walidatorpreamble header `description` should not contain `standard` (or similar words.)
|
||
author: Anushka Yadav <@64anushka> | ||
Check failure on line 5 in ERCS/erc-7734.md GitHub Actions / EIP Walidatorauthors in the preamble must match the expected format
Check failure on line 5 in ERCS/erc-7734.md GitHub Actions / EIP Walidatorpreamble header `author` must contain at least one GitHub username
Check failure on line 5 in ERCS/erc-7734.md GitHub Actions / EIP Walidatorauthors in the preamble must match the expected format
Check failure on line 5 in ERCS/erc-7734.md GitHub Actions / EIP Walidatorpreamble header `author` must contain at least one GitHub username
|
||
discussions-to: https://ethereum-magicians.org/t/discussion-on-decentralized-identity-verification-did-standard/20392 | ||
status: Draft | ||
type: Standards Track | ||
category: ERC | ||
created: 2024-07-02 | ||
created: 2024-06-26 | ||
--- | ||
|
||
## Abstract | ||
|
@@ -16,7 +16,7 @@ This proposal introduces a standard for decentralized identity verification (DID | |
|
||
## Motivation | ||
|
||
Centralized identity verification methods are often cumbersome, prone to data breaches, and do not give users control over their identity data. A decentralized identity verification standard will allow users to maintain control over their identity information while ensuring security and privacy. | ||
Centralized identity verification methods are often cumbersome, prone to data breaches, and do not give users control over their identity data. Current DID solutions, while innovative, often come with complexity and additional requirements that can be burdensome for dApp developers and users. Our proposal aims to address these issues by providing a straightforward, minimalistic approach to decentralized identity verification. This standard focuses on user control and privacy, ensuring that users can manage their identity information securely without unnecessary overhead. By leveraging cryptographic hashes and events, we provide a transparent, traceable, and efficient method for identity verification. This simplicity encourages wider adoption and integration into various dApps, fostering a more secure and user-centric ecosystem on the Ethereum blockchain. | ||
|
||
## Specification | ||
|
||
|
@@ -69,6 +69,41 @@ interface IDecentralizedIdentity { | |
``` | ||
|
||
### Usage | ||
#### Who Would Want to Implement It | ||
##### dApp Developers: | ||
Developers creating decentralized applications that require identity verification can implement this standard to provide users with secure, decentralized identity management. | ||
|
||
##### Service Providers: | ||
Platforms offering services such as decentralized finance (DeFi), gaming, or social networking can integrate this standard to verify user identities without relying on centralized authorities. | ||
|
||
###### Enterprises: | ||
Companies looking to integrate blockchain-based identity solutions into their existing systems can use this standard to ensure secure and privacy-preserving identity verification. | ||
|
||
##### Developers of Interoperability Solutions: | ||
Developers working on cross-platform and cross-blockchain interoperability can implement this standard to enable a unified identity verification mechanism across different systems. | ||
|
||
### How It's Supposed to Be Used | ||
#### Creating an Identity | ||
|
||
To create a new decentralized identity, a user calls the createIdentity function with the hash of their identity data. The contract stores this hash and emits the IdentityCreated event. This step ensures that the user's identity is registered on the blockchain. | ||
|
||
#### Verifying an Identity | ||
|
||
To verify an identity, a user calls the verifyIdentity function with two verification hashes. These hashes could be derived from proofs or attestations. The contract updates the identity's verification status and emits the IdentityVerified event. This process ensures that the identity is verified using off-chain proofs, maintaining privacy and security. | ||
|
||
#### Revoking an Identity | ||
|
||
If a user wishes to revoke their identity, they can call the revokeIdentity function. The contract marks the identity as not verified and emits the IdentityRevoked event. This feature allows users to manage their identities actively and revoke them if necessary. | ||
|
||
#### Retrieving an Identity | ||
|
||
Anyone can retrieve the details of a user's identity by calling the getIdentity function with the user's Ethereum address. This function returns the identity details, including whether the identity is verified. This feature allows dApps and services to check the identity status of users securely. | ||
|
||
## Differentiation | ||
Check failure on line 103 in ERCS/erc-7734.md GitHub Actions / EIP Walidatorbody has extra section(s)
Check failure on line 103 in ERCS/erc-7734.md GitHub Actions / EIP Walidatorbody has extra section(s)
|
||
|
||
This proposal distinguishes itself from other DID standards by focusing on a minimalistic approach, emphasizing user control and privacy. Unlike other proposals that might include a broader scope of identity attributes and interactions, this standard keeps the identity structure simple and relies on off-chain mechanisms for detailed identity management and verification. This simplicity encourages wider adoption and integration into various dApps, fostering a more secure and user-centric ecosystem on the Ethereum blockchain. | ||
|
||
## Rationale | ||
|
||
The design leverages cryptographic hashes to represent identity information, ensuring that sensitive data is not stored directly on the blockchain. The use of verification hashes allows for flexible identity verification mechanisms, and the inclusion of events ensures transparency and traceability. | ||
|