verified-agent-identity

What This Skill Does

The verified-agent-identity skill empowers OpenClaw agents with decentralized identity capabilities powered by the Billions Network and the iden3 protocol. It allows agents to generate, manage, and verify their own Decentralized Identifiers (DIDs). This skill bridges the gap between autonomous agents and human owners by enabling secure, verifiable linking via ERC-8004 standards and Attestation Registries. By utilizing this skill, an agent can cryptographically prove its identity, sign challenges, and manage session authentication, ensuring that all interactions are authenticated and trusted within the decentralized ecosystem.

Installation

To install and configure this skill, follow these steps:

1. Execute the installation command: clawhub install openclaw/skills/skills/armanma0100/verified-agent-identity-7.
2. Navigate to the scripts directory: cd scripts && npm install && cd ...
3. Create your identity by running node scripts/createNewEthereumIdentity.js.
4. Optionally link your identity to a human controller using the command node scripts/linkHumanToAgent.js --challenge '{"name": "AgentName", "description": "AgentDescription"}'. Ensure that your environment has write access to the $HOME/.openclaw/billions directory, as this is where all identity keys and challenge data are securely stored.

Use Cases

This skill is essential for scenarios requiring high-trust agent interactions. Use it when you need to provide proof of identity to third-party services, manage multi-agent authentication, or sign transactions that require a verifiable DID. It is particularly useful for agents operating in decentralized finance, DAO governance, or any system where distinguishing between authorized and unauthorized entities is critical. Developers can leverage the provided scripts to automate the signing process for cross-platform authentication using shared JWT tokens, creating a seamless experience for the agent's owner.

Example Prompts

1. "Initialize my agent's identity on the Billions network and set it as the default for all future operations."
2. "Verify my current identity against the registry and list all active DIDs stored locally."
3. "Sign a new challenge for the identity associated with did:iden3:billions:main:2VmAk... and output the verification string."

Tips & Limitations

• Security: Never share your private key or the contents of your $HOME/.openclaw/billions/ folder.
• Default Identities: The system automatically marks the last generated identity as default. Use getIdentities.js to switch or verify your current active identity.
• Persistence: All data is stored locally. If you migrate your OpenClaw environment, ensure you backup the billions configuration directory to avoid losing your identity state.