Decentralized Identifier (DID) Registration Tool

WHAT IT DOES

Decentralized Identifier (DID) Registration Tool enables authorized issuers to register decentralized identifiers (DIDs) on-chain for users, creating verifiable digital identities that can be used across decentralized applications. The tool reads the DID registry contract to check existing registrations, schemas, and expiration dates, then registers new DIDs with associated metadata—including public keys and service endpoints—for each user. The DIDs are issued as EIP-4973 soulbound tokens or EIP-1155 attestations, and the tool supports batch registration to multiple users in a single transaction using the shared BotGentz bulk sender contracts.

This tool is essential for identity platforms, DAOs, and decentralized applications that need to manage verifiable digital identities for their users. It provides a transparent, immutable record of identity registration that can be verified by any party.

HOW TO USE

1. Connect your EVM wallet to the network where the DID registry is deployed.

2. Enter the DID registry contract address and the DID method (e.g., "did:example:").

3. Add users by entering address, public key (hex), and service endpoint per line.

4. Click "Check Users" to verify which users are eligible—the tool checks for existing registrations and expiration status.

5. Review the user status table showing each user's current registration status.

6. Click "Register DIDs" to approve the fee payment and register DIDs for all eligible users.

7. Track progress via the status bar and confirmation of the transaction hash upon completion.

TECHNICAL MECHANISM

The tool reads the DID registry contract using view functions: getDID(address) or hasDID(address) to check existing registrations, and getSchema() for the DID method schema. It verifies whether a user already has a DID or if it has expired. For registration, the tool attempts batchRegisterDID(recipients[], publicKeys[], endpoints[], method) if available, falling back to sequential registerDID(recipient, publicKey, endpoint, method) calls. The tool uses the BotGentz bulk sender contract to handle fee payments, reading fee() live from the sender contract and displaying the owner before execution. Gas estimation applies a 20% buffer, and actual gas costs are calculated from receipt.effectiveGasPrice.

WHAT IT CANNOT SEE

This tool cannot verify the user's off-chain identity or real-world credentials—it relies on the issuer's assessment. It cannot guarantee that the DID is unique or universally resolvable; DID resolution depends on the registry and method. It cannot revoke DIDs if the user's identity changes or if the user requests revocation; revocation requires separate governance actions. It cannot verify that the user's public keys are secure or functional; the tool assumes the keys are valid. It cannot manage DIDs across multiple DID methods or registries with different schemas; each registry may require different parameters. It cannot validate the user's legal or regulatory compliance; the tool assumes the issuer has performed the necessary checks.

PLEASE NOTE

EVM chains only. This tool requires that the DID registry contract implements the standard interfaces used by the tool. The tool attempts multiple function signatures for compatibility. DID registration is irreversible—ensure the user's data is accurate before registering. The fee for the bulk sender contract is read live and displayed before execution; the tool does not hardcode the fee. DIDs are for informational purposes and do not constitute legal identity verification.