On-Chain KYC Credential Issuer (Institutional Use)

WHAT IT DOES

On-Chain KYC Credential Issuer (Institutional Use) enables institutions to issue, renew, and revoke on-chain KYC/AML credentials for verified users. The tool reads your connected wallet address (the institutional issuer), the credential contract address, the recipient wallet address, credential level (Basic/Enhanced/Full), credential expiry, current block timestamp, and credential revocation status. It provides a complete interface for managing the credential lifecycle: issuing credentials to verified users, renewing expiring credentials, and revoking credentials when necessary. Each credential is recorded on-chain and can be verified by any protocol or counterparty that integrates with the credential contract.

HOW TO USE

Connect your wallet (must be registered as an issuer on the credential contract). Enter the KYC credential contract address and the recipient's wallet address. Select the credential level—Basic, Enhanced, or Full—and set the expiry period in days (leave 0 for no expiry). Click "Check current credential" to view the recipient's existing credential status, including their current level, expiry, and revocation status. If the recipient has no credential or their credential has been revoked, click "Issue credential" to issue a new credential. To update an existing credential, click "Renew credential" with a new level or expiry. To revoke a credential, click "Revoke credential"—this immediately invalidates the credential and prevents the user from relying on it.

THE REAL MECHANISM — ON-CHAIN CREDENTIAL MANAGEMENT WITH ISSUER ACCESS CONTROL

Unlike simple KYC attestations that only record a single status, this tool implements a full credential lifecycle management system with role-based access control. The credential contract stores a mapping of user addresses to credential structs containing level (uint8), expiry (uint256), revoked (bool), and issuedAt (uint256). The contract uses an issuer registry to track authorized institutional wallets, and the onlyIssuer modifier restricts issue, renew, and revoke functions to registered issuers. The issueCredential function sets the credential for a recipient, and renewCredential updates the level and expiry while preserving the issuance timestamp. The revokeCredential function sets the revoked flag, immediately invalidating the credential. The isActive function checks that a credential is not revoked and has not expired. The tool reads all credential data via getCredential, which returns the full struct, and uses isActive for quick status checks. All operations are recorded on-chain, providing an auditable history of credential issuances, renewals, and revocations. Gas costs are reported using receipt.effectiveGasPrice.

WHAT IT CANNOT SEE

Cannot verify off-chain KYC process integrity—the tool has no visibility into how KYC checks were conducted or whether proper procedures were followed. It cannot ensure identity verification accuracy—the tool cannot confirm that the physical identity documents match the wallet owner. It cannot validate physical identity documents—the tool does not accept or review identity documents. It cannot detect if the credential contract contains vulnerabilities or malicious code—the tool does not audit the contract logic. It cannot prevent unauthorized issuances if an issuer wallet is compromised.

PLEASE NOTE — EVM CHAINS ONLY

This tool exclusively supports EVM-compatible chains where ethers.js can connect via standard JSON-RPC. It does not support non-EVM chains such as Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, or XRP. The credential contract must implement the specific interface expected by this tool (issueCredential, revokeCredential, renewCredential, getCredential, isActive, isIssuer). This tool is for institutional use only—you are responsible for conducting proper KYC/AML checks before issuing credentials. Consult with legal counsel regarding your compliance obligations.