ERC-7574 Credential-Authenticated SBT (Authentication SBT using Credential)
Draft · Signatures & auth · created 2023-11-02
A standard that verifies possession of a decentralized identity (DID) credential via a zero-knowledge proof, then issues a non-transferable soulbound token (SBT) for use as a means of on-chain authentication and access control.
Why it is needed
Many blockchain apps distinguish users only by wallet address. While addresses offer strong anonymity, it is hard to prevent a single person from impersonating multiple addresses in a Sybil attack or duplicate participation, and verified users cannot be distinguished from anonymous ones. Decentralized identity (DID) credentials carry verifiable claims such as affiliation or qualifications in a standard way, but putting them directly on-chain or presenting them raises privacy exposure, usability, and compatibility problems that make them hard for app developers to use consistently. This standard defines a common method that leaves behind, as a non-transferable token, only the result of a successful verification, rather than the credential itself. Apps can identify authenticated users using the simple signal of whether the token is held, without ever seeing the credential's contents.
What to implement
function verify(bytes calldata verificationData) external returns (bool);: Verifies proof of credential possession. The verification method itself may vary by implementation.function issueSBT(address to, string calldata tokenURI) external returns (uint256 tokenId);: After successful verification, issues a non-transferable SBT to the address and returns the token ID.function updateTokenURI(uint256 tokenId, string calldata tokenURI) external;: Updates the token's metadata to reflect revocation or status changes.
In depth
Metadata Extension: Issuer and credentialNumber
Adds an "Issuer" and "credentialNumber" section to the ERC-721 metadata standard. When issuing the SBT, it specifies the credential's issuer and credential number, without storing the user's personal information in the token. If an issue arises, the credential number used for verification can be looked up with the Issuer to trace the identity verification process without disclosing user information. By designing the metadata to reference only the verification context in this way, it minimizes exposure of personally identifiable information while enabling audit and revocation workflows.
VerifiedPresentation Struct
Defines a struct representing a verified presentation. It has four fields: the user's wallet address userAddr (address), the issuer issuer (string), the user's name user (string), and the credential number CredentialNumber (uint).
Contract Interface and ERC-5192 Obligation
The IERC7574 interface consists of three functions: verify, issueSBT, and updateTokenURI. verify checks proof of credential possession, and on success the implementation issues an SBT to the user's address, completing authentication. Implementations of this ERC MUST guarantee that the issued SBT is non-transferable, and MUST implement ERC-5192 (locked SBT). In this process, acquiring the SBT becomes the sole means of authentication, and afterward holding the SBT becomes the method of identity verification.
Proof Method Left to the Implementation
This standard does not mandate a specific credential proof mechanism (for example, a particular zero-knowledge proof system). Different ecosystems may prefer different proof systems or verification methods, and requiring a single tool would make independent, interoperable implementations impossible. Instead, the standard only specifies the outcome: that a non-transferable token is issued to the user upon successful verification.
Revocation Is a Metadata Update, Not a Burn
Revocation or status changes are represented by updating the token metadata (tokenURI) instead of burning the token. Keeping the token in existence while only changing its status lets apps distinguish between "never verified" and "verified and later revoked" states. This is useful in access control and compliance scenarios. Transfers are also blocked so that the authentication signal cannot be sold or lent out, preserving the token's meaning as a verification proof bound to a specific address.
Proposal status: Draft
This proposal is still in Draft status. Its contents may change, so it is advisable to check the latest source text before implementing it.
Things to watch out for
- Soundness of Verification Logic Is the Implementer's Responsibility: This standard does not mandate a specific credential verification mechanism. The responsibility for ensuring the correctness and soundness of the verification logic, including preventing forged proofs and replay attacks, lies with the implementer.
- Linkability Through Metadata: Even though the standard minimizes on-chain exposure of personal data, metadata fields such as the issuer reference must be designed so that users cannot be unintentionally linked and tracked across multiple apps.