LaunchKit · 2026
Back to Skills

sovereign-id

Enables the agent to manage its own identity (DID) and generate cryptographic proofs for B2B and B2C trust.

0
435 downloads
by @tamtunnel

Setup & Installation

openclaw skills install @tamtunnel/sovereign-id

Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:

npx clawhub install sovereign-id

Version History

v0.1.1Feb 16, 2026 - Version note by skill developer:

- Migrated scripts and documentation to a new directory structure under `.agent/skills/identity-sovereign/` - Added project metadata and configuration files: `AGENT.md`, `CONTRIBUTING.md`, `README.md`, `package.json`, `skill.json`, `tsconfig.json` - Removed old scripts from the root `scripts/` directory - No changes to SKILL.md content

What This Skill Does

Manages an agent's decentralized identity (DID) and generates cryptographic proofs for B2B and B2C trust scenarios. Context determines which identity persona is used: a Corporate DID with a Signed Mandate for financial and legal operations, a one-time Pairwise DID with SD-JWT for public access, or a Personal DID with ZKP for personal accounts. Private keys are never exposed and mandates over $100 require explicit user approval.

Instead of sharing full identity documents, the agent discloses only the specific claims a relying party needs and assigns a unique pairwise DID per interaction, preventing cross-service tracking.

When to use it

  • Signing a vendor contract using a Corporate DID and signed mandate
  • Proving age for restricted content without submitting an ID document
  • Verifying residency during a service registration anonymously
  • Responding to identity challenges from other business agents
  • Authorizing a bounded payment on behalf of an organization

Example Workflow

Here's how your AI assistant might use this skill in practice.

INPUT

User asks: Register me for this platform that requires proof of residency

AGENT
  1. 1Runs identity_check('register', ['signup', 'access', 'register']) to determine context
  2. 2Selects Ghost (Pairwise DID) persona for public/browsing interaction
  3. 3Generates a new one-time pairwise DID for this session
  4. 4Calls present_sd_jwt(['residency']) to disclose only the residency claim
  5. 5Completes registration using the pairwise DID and SD-JWT proof
OUTPUT

Registration completed with residency verified; no other personal data shared and the unique pairwise DID prevents cross-platform tracking