展示HN:Vouch协议 – AI代理的开放身份(C2PA和Did)

1作者: rampy20 天前原帖
嗨,HN, 我是 Vouch Protocol 的创始人。 我们正进入一个人工智能代理能够采取实际行动的世界(如预订航班、提交代码、转移资金)。 问题是:目前没有办法在执行之前以加密方式验证代理的意图。(例如,一个代理声称它将执行 `read_db`,但实际上却执行了 `delete_db`——而你没有证据证明这种差异,也没有办法阻止这种情况发生)。 目前行业的解决方案依赖于旧的 X.509 证书授权模型——基本上是每年向一个集中化的权威机构支付 $$$ 以获取数字身份。这种方式无法扩展到数十亿个自主代理。 因此,我构建了 Vouch Protocol。 它是一个开源的 AI 代理身份标准,用 W3C 去中心化标识符(did:web)取代付费证书。 它的工作原理: 1. 身份:你的代理生成自己的 Ed25519 密钥对。 2. 解析:它将公钥发布到你的域名(/.well-known/did.json),使你的域名成为信任的根。 3. 签名:代理使用 JWT-VC(可验证凭证)对每个提示/操作进行签名。 4. 验证:任何其他系统都可以在不访问中央服务器的情况下加密验证“此操作来自域名 X 的代理”。 更新:我今天刚将 Vouch 提交给 C2PA(内容来源和真实性联盟),以推动这一去中心化模型作为标准,与 Adobe 和 Microsoft 一起。 代码库(代码 + SDK):[https://github.com/vouch-protocol/vouch](https://github.com/vouch-protocol/vouch) 我希望你能批评我的架构,告诉我我哪里错了,或者(希望)如果你同意这一层应该是免费的,请给代码库加星。
查看原文
Hi HN,<p>I’m the creator of Vouch Protocol.<p>We are entering a world where AI agents are taking real actions (booking flights, committing code, moving money).<p>The problem: There is currently no way to cryptographically verify an Agent&#x27;s intent before execution. (e.g., An agent claims it will `read_db`, but actually executes `delete_db`—and you have no proof of the discrepancy nor a way to stop this from happening).<p>The current industry solution relies on the old X.509 Certificate Authority model—basically, paying a centralized authority $$$ per year for a digital ID. That doesn&#x27;t scale for billions of autonomous agents.<p>So I built Vouch Protocol.<p>It is an open-source standard for AI Agent Identity that replaces paid certificates with W3C Decentralized Identifiers (did:web).<p>How it works:<p>1. Identity: Your agent generates its own Ed25519 key pair.<p>2. Resolution: It publishes its public key to your domain (&#x2F;.well-known&#x2F;did.json), making your domain the root of trust.<p>3. Signing: The agent signs every prompt&#x2F;action using a JWT-VC (Verifiable Credential).<p>4. Verification: Any other system can cryptographically verify &quot;This action came from the Agent at domain X&quot; without hitting a central server.<p>Update: I just submitted Vouch to the C2PA (Coalition for Content Provenance and Authenticity) today to push for this decentralized model as a standard alongside Adobe and Microsoft.<p>Repo (Code + SDK): <a href="https:&#x2F;&#x2F;github.com&#x2F;vouch-protocol&#x2F;vouch" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;vouch-protocol&#x2F;vouch</a><p>I’d love you to roast my architecture, tell me why I&#x27;m wrong, or (hopefully) star the repo if you agree this layer should be free.