Decentralized Identity Credential Revoker

WHAT IT DOES

Decentralized Identity Credential Revoker enables authorized issuers to revoke previously issued verifiable credentials (VCs) by updating an on-chain revocation registry. The tool reads the DID registry or credential issuance contract to verify the credential's existence, status, and the issuer's authority. It then submits a transaction to the revocation registry—adding the credential ID to a revoked list, updating a bitmask, or modifying a Merkle tree—rendering the credential invalid for all future verifications. The tool also supports recording a revocation reason and optionally notifying the holder via an on-chain event. Revocation is permanent and timestamped, providing an immutable audit trail.

This tool is essential for issuers of decentralized identities—governments, universities, employers, DAOs, and protocols—who need to manage credential lifecycles, revoke expired credentials, or invalidate credentials due to compromise, fraud, or policy changes. It brings trust revocation on-chain, making it transparent and verifiable by any relying party.

HOW TO USE

1. Connect your EVM wallet (must be the credential issuer or an authorized revoker).

2. Enter the DID registry or credential issuance contract address.

3. Enter the revocation registry contract address (the registry that tracks revoked credentials).

4. Provide the credential ID to revoke (string or numeric identifier).

5. Optionally enter the holder's address (for holder-specific revocation events) and a revocation reason (e.g., "Expired," "Compromised," "Policy violation").

6. Click "Check Credential" to verify the credential exists, is active, and the connected wallet has authority to revoke it.

7. Review the displayed credential details: issuer, holder, validity period, and whether it is already revoked.

8. Click "Revoke Credential" to submit the revocation transaction. Confirm in your wallet. The revocation is irreversible.

TECHNICAL MECHANISM

The tool reads the DID registry using functions like getCredential(credentialId) to retrieve issuer, holder, validity timestamps, and active status. It checks the revocation registry via isRevoked(credentialId) to ensure the credential hasn't already been revoked. The tool verifies authority by calling canRevoke(issuer, credentialId) or checking if the connected wallet matches the credential's issuer. The revocation transaction is submitted using one of several supported function signatures: revoke(string), revokeWithReason(string,string), or revokeForHolder(string,address). Gas estimation applies a 20% buffer, and actual gas costs are calculated from receipt.effectiveGasPrice. The tool displays the transaction hash, gas cost, and updates the credential status to "Revoked" in the review panel.

WHAT IT CANNOT SEE

This tool cannot prove that the holder has actually stopped using the credential off-chain—revocation is an on-chain signal, but the holder may continue to present the credential to systems that do not check the revocation registry. It cannot prevent the holder from presenting an already-revoked credential in systems that fail to verify revocation status. It cannot revoke credentials issued by other issuers without proper authority—authorization is enforced on-chain and verified by the tool. It cannot recover credentials once revoked—revocation is permanent and irreversible. It cannot verify the holder's identity or intent beyond the on-chain data; off-chain identity verification is not performed. The tool cannot detect if a credential was already presented and accepted before revocation; that is outside the scope of on-chain revocation.

PLEASE NOTE

EVM chains only. This tool requires that both the DID registry and revocation registry are deployed and compatible with the expected interfaces. Revocation registries may use different data structures (lists, bitmaps, Merkle trees); the tool attempts multiple function signatures to maximize compatibility. Always verify that you are the authorized issuer—revoking credentials you do not own is not possible and will fail on-chain. Revocation is a serious action; ensure you have the proper authority and reason before proceeding.