Soulbound Credential Revoker

WHAT IT DOES

The Soulbound Credential Revoker enables authorized entities to revoke soulbound credentials on-chain. It reads soulbound credential contract state, user address, wallet balance, credential ID, credential issuer, credential holder, credential type, and credential status. The tool processes revocation reasons, gas price, base fee, block timestamp, chain ID, transaction nonce, approval state, contract owner state, and revoker authority. It supports revokeCredential for standard revocation, batchRevokeCredentials for multiple revocations in one transaction, and revokeWithReason for attaching a reason to the revocation. The tool reads the credential's issuer, type, and status before execution.

HOW TO USE

Connect your wallet and select the target network. Enter the soulbound credential contract address, the credential ID, and the holder address. Optionally provide a revocation reason. Choose the execution method (revokeCredential, batchRevokeCredentials, or revokeWithReason). The tool will fetch the credential state, display the issuer, type, and current status. Once confirmed, it submits the revocation transaction. The tool checks if the credential has already been revoked and warns before proceeding.

TECHNICAL MECHANISM

Unlike generic revocation tools, this executor is purpose-built for soulbound credential workflows. It first reads the contract's isActive() to ensure the contract is operational. The tool fetches credential details via getCredential() to display the issuer, holder, type, and revocation status. It checks isRevoked() to prevent double revocation. The tool selects the optimal method: revokeCredential for standard revocation, batchRevokeCredentials for multiple revocations in one transaction, or revokeWithReason for revocations with a reason string. The revocation reason is passed as a string and stored on-chain for transparency. Gas costs are calculated using receipt.effectiveGasPrice for accurate post-EIP-1559 fee accounting. The tool displays the credential status and revocation reason before confirmation.

WHAT IT CANNOT SEE

This tool cannot verify that the revocation reason is valid or that the credential should be revoked. It cannot detect if the credential has already been revoked or if the revoker has sufficient authority. It also cannot guarantee that the revocation will be accepted or recognized by other contracts. The tool cannot verify the revoker's authority or detect if the contract has been paused. It also cannot detect if the credential type affects the revocation process.

PLEASE NOTE

This tool supports EVM-compatible chains. Revoking a soulbound credential is irreversible—verify all data carefully before signing. The credential contract must implement the revocation functions expected by this tool. The revoker must have sufficient authority (owner, issuer, or authorized role). Batch revocation requires arrays of credential IDs and holder addresses. This tool does not create credentials—for that, use the Soulbound Credential Issuer Tool. Always verify the credential status before revoking.