Skip to content

Add @voidly/agent-sdk — self-certifying did:voidly SDK#60

Open
EmperorMew wants to merge 1 commit into
animo:mainfrom
EmperorMew:add-voidly-sdk
Open

Add @voidly/agent-sdk — self-certifying did:voidly SDK#60
EmperorMew wants to merge 1 commit into
animo:mainfrom
EmperorMew:add-voidly-sdk

Conversation

@EmperorMew

Copy link
Copy Markdown

Summary

Adds @voidly/agent-sdk to the Tools & Technologies section — a TypeScript SDK for end-to-end encrypted agent-to-agent messaging that uses self-certifying decentralized identifiers.

Why this fits the SSI criteria

The SDK uses did:voidly: identifiers that are self-certifying — the DID is derived directly from the user's own Ed25519 public key:

did:voidly:{base58(Ed25519-pubkey[0..16])}

This means:

  1. No central authority is needed to mint, verify, or revoke an identity — the public key resolvable from the DID is the proof.
  2. Users generate keys locally (Ed25519 signing + X25519 encryption); private keys never leave the client.
  3. The default relay is optional — the relay node (relay-node/) is open-source, so agents can self-host or federate across relays. The user's identity is not bound to any particular relay operator.
  4. An Agent Card compliant with Google A2A Protocol v0.3.0 is published at /.well-known/agent-card.json (W3C DID-style document describing capabilities, public keys, and endpoints), e.g. https://api.voidly.ai/.well-known/agent-card.json.

This satisfies the self-sovereign property (the holder alone controls the keys that authenticate the identifier) without a blockchain or central registrar — similar in spirit to did:key / did:peer.

Notes / transparency

Checklist

  • Entry added alphabetically in Tools & Technologies.
  • Single-line, one-sentence-style description matching neighbouring entries.
  • Project is actively maintained (current version v3.4.9).
  • Not a duplicate of an existing entry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant