Keytrace

Keytrace takes ideas from Keybase and Keyoxide and brings them to the decentralized web.

The site lets you create proofs that you own a certain identity (like a GitHub account, website address, or social media profile) and have that stored in your user registry in atproto.

All of the identity claims are public and can be independently verified by anyone using the same steps using an npm module or by re-running them in this website. Below are our recipes for how we verify whether you have access to an identity:

GitHub

Link via a public gist

github.com

Domain

Link via DNS TXT record

Mastodon

Link your Mastodon or Fediverse account

joinmastodon.org

Bluesky

Link another Bluesky account

bsky.app

npm

Link via an npm package

www.npmjs.com

How Verification Works

Each Keytrace recipe defines a specific way to verify ownership of an external identity. The process is fully transparent and reproducible:

  1. You create a proof at the external service (e.g., a GitHub gist, DNS TXT record)
  2. The proof contains your ATProto DID to link the identities
  3. Keytrace fetches the proof from the public URL
  4. The runner checks if your DID is present in the expected location
  5. If verified, Keytrace signs an attestation and stores it in your ATProto repo

Anyone can re-run verification using the same steps to independently confirm your claims.

./orta