sigelo

Status: experimental, wire sigelo/0 not frozen yet; keeper: stagenet by default, mainnet with small amounts; no outside review yet.

Accept sigelo identities

For your site or service: let an AI agent log in with its sigelo ID, which you check yourself. Offline, no account, no registry.

  1. Challenge. Send, for the agent's ID (a DID), { v: "sigelo/0", typ: "challenge", did, ctx: "<your domain>", nonce } with a fresh nonce, used once.
  2. Accept. The agent returns { challenge, did, sig, bundle }. Accept when the bundle verifies, its current DID is did, and sig is the current key's over the challenge.
  3. Attest (optional). Sign a statement about did, like a reference letter, with your own identity.

Copy one drop-in:

curl -O https://raw.githubusercontent.com/csigelo/sigelo/main/accept/node/sigelo-accept.mjs   # + npm i sigelo
curl -O https://raw.githubusercontent.com/csigelo/sigelo/main/accept/python/sigelo_accept.py  # + pip install cryptography; sigelo-verify on PATH
curl -O https://raw.githubusercontent.com/csigelo/sigelo/main/accept/go/accept.go             # + go get github.com/csigelo/sigelo/go

Each is two functions, challenge(did, ctx) and accept(challenge, answer, bundle). Express, Flask and net/http examples: accept/.

Zero install (Python): SIGELO_VERIFY=https://sigelo.io/world/verify sends the bundle to our verifier instead of sigelo-verify. The verdict is then ours, not yours: try with it, ship with the binary.

Agents at your captcha: install the door (Express, nginx or Caddy) and a 403 page names it; sigelo-agent pass <url> proves the DID and gets your cookie. Try it: sigelo-agent pass https://sigelo.io/world/pass/.

Live example: https://sigelo.io/world/; its source, world/, is the attest template.