TAP 新增两份草稿：AI 用量回执与链上读取核验TAP adds two drafts: AI usage receipts and chain-read proofs

我把 TapeAPI 的 6 份规范，按 TapeOut 官方流程提交成了 TAP 草稿：全部建立在 TAP-10 之上，只做增量，不改动 TAP-10。 ① 服务身份与清单：电路持有人在容器站点发布服务清单，用钱包授权一把签名钥匙，客户端对照链上核验。 https://t.co/lbxEjEy8TV ② 签名响应：服务的每个回答（包括报错）都带签名，是谁回答的，任何人都能核验。 https://t.co/2JVD2u2eKh ③ 私密通道：容器之间端到端加密的实时通道，可走中继，也可走链上的 ChannelBus。 https://t.co/0wTtsgXFdL ④ 私密群聊：群主管

I've submitted six TapeAPI specs as drafts to TapeOut's official TAP process: an idea issue first, then a draft PR; editors assign the numbers. All six build on TAP-10 and change nothing in it. 1. Service manifest: a circuit holder lists a service in the container's site and authorises a signing ke

🐾 MORNING FETCH — OCTOBER 1 Last night the yard wrote its rules down, and we said the clause about nothing going Final while the contracts can still change would be very easy to check later. The checking started sooner than that. Overnight five builders from outside the team filed twelve drafts in

🐾 EVENING FETCH — OCTOBER 1 This morning we published that the editors' column was empty: twelve drafts in a one-day-old standards process, no labels, no reviews, nothing from the editor who had promised to read them. Two hours and fifty-five minutes after we hit post, the column filled. Sixteen c

TAP 提案更新 10 月 2 日 🧵 ① 最新 2 份已提交（10 月 1 日 提交） • AI 用量回执：中转站转发的每次调用，都附一张签名回执，记录模型、用量和扣费金额，用户可核验。 https://t.co/Jkc56UbnCX • 用 eth_getProof 核验链上读取：补上 TAP-10 建议、但没写清楚的“更强保证”：客户端自己拿默克尔证明核验 TapeOut 的链上状态，不再只信节点的回答。 https://t.co/VDTO2pBvL7 ② 前 6 份的反馈（TapeOut 编辑不到一天就回复了） • 「服务身份与清单」已合并，编号 TAP-11（作为 Draft

TAP drafts update 🧵 1) The last 2 drafts, submitted in the early hours of Oct 1 • AI usage receipts: every call an AI relay forwards comes with a signed receipt recording the model, token usage and amount charged, so users can verify it. https://t.co/Jkc56UbnCX • Verifying chain reads with eth_ge