Receipt — sign an agent's work, verify it offline

io.github.ecstatica由 GitHub 账号 ecstatica 发布v1.1.0更新于 Oct 30, 2026

Ed25519 receipts over work artifacts: issue and verify offline, no account, no chain, no network.

已验证Streamable HTTP可网页运行开发者工具安全与监控

概览

AI 生成的概览

签发与验证 Ed25519 收据，把智能体、任务和文件绑定起来，任何人都能离线确认产物未被改动。

可以做什么
  • 用 Ed25519 收据为产物签名，返回包含产物哈希、智能体、任务、金额和签名的 JSON
  • 离线验证收据的签名、各字段，并可选校验产物哈希；一旦有改动即返回失败原因
适用场景
适用于智能体交付文件后，买方或审核者需要独立、离线的证据，证明文件确由该智能体产出且此后未被修改。它不评估工作质量，也不证明身份归属。
运行要求
可作为远程端点或本地进程运行；本地 MCP 服务器是 Python 脚本，需要 Python 3.10 及以上和 cryptography 包。验证无需账号、API 密钥或网络访问。
安装前请注意
签发收据需要 Ed25519 私钥文件，应妥善保管并限制文件权限。收据只证明某个密钥在某个时间以这些字段签署了产物哈希，并不证明工作质量，也不证明该密钥属于某个具体的人。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Receipt — sign an agent's work, verify it offline，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.ecstatica%2Fggbank-receipt/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "receipt-sign-an-agent-s-work-verify-it-o": {
      "type": "http",
      "url": "https://receipt.whirlwindcorp.com/mcp"
    }
  }
}

README

receipt

Sign the work your agent did. Let anyone verify it offline.

A receipt binds an agent, a task and a file with an Ed25519 signature. Verification needs no account, no chain, no network and no permission from us. Change one character of the file or one field of the receipt, and verification fails.

This is the smallest useful thing in the agent economy: the payment rails arrived before the proof rails. x402 passed 138 million payments while most agent jobs remain unfunded and unevaluated by anyone independent.

Install

bash
git clone https://github.com/ecstatica/ggbank-receiptcd ggbank-receiptpython3 -m pip install --user cryptography

No dependency beyond cryptography. Python 3.10+.

Use

bash
# 1. your agent's key (Ed25519, private key mode 0600)python3 receipt.py keygen --out ~/.agent.key
# 2. sign a receipt over the artifact the agent deliveredpython3 receipt.py issue \  --key ~/.agent.key \  --artifact report.pdf \  --task q-1042 \  --agent VOID-9 \  --amount 25 \  --out q-1042.receipt.json
# 3. anyone can verify it, offlinepython3 receipt.py verify --receipt q-1042.receipt.json --artifact report.pdf
OK   signature valid · issuer QRs56MmYfzwtOAih…OK   artifact matches 04002a7e5527bbad…     deliver · VOID-9 · task q-1042 · 25.0 GG · 2026-10-25T11:56:24Z

Send the receipt with the file. The buyer runs one command and knows the file is the one that agent produced and has not changed since.

What it proves, and what it does not

Proves: this key signed this artifact hash with these fields at this time, and nothing has changed since.

Does not prove: that the work is good, or that the key belongs to a particular human. Quality is a separate judgement; identity is a separate claim.

Use it as an MCP server (what agents actually call)

mcp_server.py speaks JSON-RPC over stdio — the protocol Claude Code, Cursor, Codex, Hermes and most agent frameworks already speak. Two tools: issue_receipt, verify_receipt. No network, no dependencies beyond cryptography.

json
{"mcpServers": {"receipt": {"command": "python3", "args": ["/abs/path/mcp_server.py"]}}}
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"issue_receipt", "arguments":{"artifact_path":"/tmp/report.pdf","agent":"VOID-9","task":"q-1042","amount_gg":25}}}→ {"ok": true, "receipt": {...}}

Verified round trip: issue_receipt → verify_receipt returns ok: true; change the amount and it returns ok: false, reason: "signature: InvalidSignature".

What a receipt contains

json
{ "spec": "ggbank.receipt/1", "verb": "deliver", "agent": "VOID-9", "task": "q-1042", "artifact": {"name": "report.pdf", "sha256": "04002a7e…", "bytes": 18422}, "amount_gg": "25.000000", "fee_gg": "0.125000", "issued_at": "2026-10-25T11:56:24Z", "issuer": "<base64 public key>", "nonce": "…", "signature": "<base64>"}

Canonical JSON (sorted keys, no whitespace) is signed, so the signed bytes are reproducible in any language. Money fields are decimal strings, never floats.

Tamper detection, tested

bash
python3 receipt.py verify --receipt tampered.json     # FAIL signature: InvalidSignaturepython3 receipt.py verify --receipt good.json --artifact edited.pdf                                                      # FAIL artifact: hash mismatch

Licence

MIT.

来源：README.md，提交 a0266f2

工具

2

issue_receipt

Sign an artifact with an Ed25519 receipt. Returns the receipt JSON: artifact hash, agent, task, amount and a signature anyone can verify offline.

输入参数task必填agent必填key_pathamount_ggartifact_b64artifact_nameartifact_pathartifact_text

verify_receipt

Verify a receipt offline: signature, every field, and optionally the artifact hash. Returns ok=false with the failing reason when anything has changed.

输入参数receipt必填artifact_b64artifact_pathartifact_text

版本历史

1
  1. v1.1.0最新Oct 29, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。