核验回执Verify a receipt

TapeAPI 服务的每个回答都有签名,MCP 工具结果还附带一份回执。本页在你的浏览器里重新从 BNB 链解析这个服务、从签名恢复签名者,再比对两者。回执自己说的任何话都不采信。Every answer from a TapeAPI service is signed, and MCP tool results come with a receipt. This page resolves the service again from BNB Chain in your browser, recovers the signer from the signature, and compares the two. Nothing the receipt says about itself is taken on trust.

1回执Receipt

可以粘贴:核验链接(https://tapeapi.fun/verify/#r=…)、它的 #r= 部分、回执 JSON,或整个 MCP 工具结果(含 _meta["fun.tapeapi/receipt"],也可以是外层的 JSON-RPC 回应)。最多 64 KiB。Paste the verify link (https://tapeapi.fun/verify/#r=…), its #r= part, the receipt JSON, or a whole MCP tool result (with _meta["fun.tapeapi/receipt"], or the JSON-RPC response around it). Up to 64 KiB.

本页核对什么What this page checks

  1. 从签名恢复签名者:签名覆盖容器、请求 id、方法与参数、成功或拒绝、结果、时间。改动其中任何一项,恢复出的就是另一个地址。Recover the signer from the signature, which covers the container, request id, method and params, success or refusal, the result, and the time. Change any of them and a different address comes out.
  2. 用回执里的电路合约和 #ID 在链上解析服务(3 个公共 BSC 节点,至少 2 个一致):容器由中枢推导,清单字节与 SiteRegistry 的哈希一致,委托由当前持有人签署且未过期。Resolve the service on chain from the receipt's circuit contract and #ID (3 public BSC nodes, at least 2 agreeing): the hub derives the container, the manifest bytes match the SiteRegistry hash, and the delegation is signed by the current holder and not expired.
  3. 比对:链上推导的容器等于回执里的容器;回执里的名字属于这个服务;恢复出的签名者等于清单今天指定的签名密钥。Compare: the container the chain derives equals the receipt's; the receipt's name belongs to this service; the recovered signer equals the signing key the manifest names today.

手上没有回执?在调试台里调用一个方法,或者用 MCP 端点 https://api.tapeapi.fun/mcp:每个工具结果都带核验链接。No receipt at hand? Call a method in the Playground, or use the MCP endpoint https://api.tapeapi.fun/mcp: every tool result carries a verify link.