返回资讯中心
外部精选
软件工程
#开发者实时流

Keytrace 将 atproto 账号与 GitHub、DNS 等外部账号绑定并生成签名凭证

来源标题:Keytrace – One identity, many proofs

Keytrace 推出一项验证服务,可将用户的 atproto 身份与已有账号(如 GitHub、DNS、npm、Mastodon、PGP)绑定,并生成可移植的签名凭证。用户通过 atproto PDS 登录后,只需将短令牌放入 gist、DNS TXT 记录或置顶帖,验证程序便会核对并把 dev.keytrace.claim 记录写入用户仓库。该记录可供任何人验证,目前已有多位用户完成绑定。

Hacker News 最新figmert2026/11/16 · 2 天前16 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

Keytrace links your atproto handle to the accounts you already own — GitHub, DNS, npm, Mastodon, PGP — with signed, portable proofs. You be you, everywhere.

keytrace.dev/add/github

live

linking orta.io → @orta on GitHub

⠋resolving DID for orta.io

✓did:plc:t732otzqvkch7zz5d37537ry

··fetching gist gist.github.com/orta/b7dccdfb...

··matching proof token against handle

✓proof valid · signature matches DID

··writing dev.keytrace.claim to your PDS

§1 How it works

A proof is a link you control, connecting your atproto identity.

01

Sign in with your internet handle

OAuth with your atproto PDS. No new account. No PGP keys to generate.

Drop a short token into a gist, a DNS TXT record, a package README, a pinned post.

Our runner verifies the proof and writes a dev.keytrace.claim record to your repo.

Every claim here was written to its author's PDS. Stored in their repo, verifiable by anyone.

liljalice.neocities.org→LilJalicevia Discord

signed

22h agosocial.epmills.com→epmillsvia Bluesky

signed

1d agotynanpurdy.com→Tynan Purdy ⁂via Mastodon

signed

2d agoantoniopinto.eu→Antonio Pintovia Steam

signed

3d agozac0511.com→PGP Keyvia PGP Key

signed

3d agodanyn.dev→danyn.devvia Domain

signed

3d agobenjamin.bckr.me→tartarus.usvia Domain

signed

4d agop12r.com→p12r.comvia Domain

signed

4d agopatrickkrueger.com→Patrick Kruegervia Bluesky

signed

6d agoseremegu.me→seremegu.mevia Domain

signed

1w agofixeq.dev→fixeq.devvia Domain

signed

1w agokrill0w.garden→krill0w.gardenvia Tangled

signed

··· from keytrace.devlearn about the lexicon →

§3 For atproto developers

Same lexicon. Same libraries. Your identity layer.

Keytrace is built on dev.keytrace.* — an open atproto lexicon. Anything Keytrace can read, your app can read. Everything we verify, you can re-verify. Nothing is locked behind our API.

Open lexicons

Schemas published in the orta/keytrace monorepo.

Convenience packages

@keytrace/claims · @keytrace/lexicon

Run the runner

Use @keytrace/runner in your own projects to verify claims. npmx →

Portable across PDSes

Records live in the user's repo. Keytrace is not a silo.

Read the docs → orta/keytrace

Lexicon Claims Runner Claim record

dev.keytrace.claim.json json

{ "lexicon": 1, "id": "dev.keytrace.claim", "defs": { "main": { "type": "record", "key": "tid", "description": "An identity claim linking this DID to an external account", "record": { "type": "object", "required": [ "type", "claimUri", "identity", "sigs", "createdAt" ], "properties": { "type": { "type": "string", "knownValues": [ "github", "dns", "activitypub", "bsky", "npm", "npmorg", "tangled", "pgp", "twitter", "linkedin", "instagram", "reddit", "hackernews", "orcid", "itchio", "discord", "steam" ], "description": "The claim type identifier" }, "claimUri": { "type": "string", "description": "The identity claim URI (e.g., for github: https://gist.github.com/username/id, dns:example.com)" }, "identity": { "type": "ref", "ref": "#identity", "description": "Structured data about the claimed identity, derived from the claimUri and knowledge inside the verification process. This is not the raw claim data, but a normalized set of fields that can be used for display and more." }, "sigs": { "type": "array", "items": { "type": "ref", "ref": "dev.keytrace.signature#main" }, "description": "Cryptographic attestation signatures from verification services, for example from @keytrace.dev. These are optional, and so you can pass an empty array. Keytrace will place its attestation signature in the claim here so that the library @keytrace/claims can be used by external developers to not have to implement their own verification logic." }, "comment": { "type": "string", "maxLength": 256, "description": "Optional user-provided label for this claim" }, "status": { "type": "string", "description": "Current verification status of this claim. Absent on legacy records, treated as 'verified'.", "knownValues": [ "verified", "failed", "retracted" ] }, "lastVerifiedAt": { "type": "string", "format": "datetime", "description": "Timestamp of the most recent successful re-verification by the system" }, "failedAt": { "type": "string", "format": "datetime", "description": "Timestamp when the claim last failed re-verification or was retracted" }, "createdAt": { "type": "string", "format": "datetime", "description": "Datetime when this claim was created (ISO 8601)." }, "nonce": { "type": "string", "maxGraphemes": 128, "description": "Random one-time value embedded in the challenge text posted to the external service. Used by verifiers to confirm the proof was created specifically for this claim session. Keytrace itself does not use this, but other services making claims may require it for their verification process." }, "prerelease": { "type": "boolean", "description": "Whether this claim was created during the prerelease/alpha period" }, "retractedAt": { "type": "string", "format": "datetime", "description": "Datetime when this claim was retracted. Present only if the claim has been retracted (ISO 8601)." } } } }, "identity": { "type": "object", "description": "Generic identity data for the claimed account", "required": [ "subject" ], "properties": { "subject": { "type": "string", "description": "Primary identifier (username, domain, handle, etc.)" }, "account": { "type": "string", "description": "The platform account that demonstrated control of the subject, when the two differ. Used by claim types where the subject is a shared namespace rather than a personal account — e.g. for npmorg the subject is the org scope ('babel') and the account is the npm user who published the proof ('alice'). Absent when the subject is itself the account." }, "avatarUrl": { "type": "string", "format": "uri", "description": "Avatar/profile image URL" }, "profileUrl": { "type": "string", "format": "uri", "description": "Profile page URL" }, "displayName": { "type": "string", "description": "Display name if different from subject" } } } } }

Model the claim yourself. The whole schema lives in an open repo.github.com/orta/keytrace/lexicon

§4 — /signup

Keep the handle. Prove the rest.

Two minutes, one proof, one signed claim in your repo.

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →