ZKStamp Proof-100

io.github.ZKStamp由 GitHub 账号 ZKStamp 发布v0.2.0更新于 Oct 29, 2026

Shielded proof-of-existence timestamps on BitcoinZ (zk-SNARKs). Free trial: 3 proofs.

发布方自己的服务：Proof Holdings

已验证Streamable HTTP可网页运行金融安全与监控

服务详情

标识符: io.github.ZKStamp/proof100
传输: Streamable HTTP
运行时: Web executable
信任: Verified
发布于: Oct 29, 2026

安全提示

MCP 服务会接收对话中的工具调用请求，并可能执行外部操作。启用前请先了解该服务能做什么，并只授予它所需的权限。

注册中心已验证此条目所属的 GitHub 账号 ZKStamp。这并不表明该账号就是产品方。

SourceWeft 的检查只涵盖条目是否完整、端点是否响应；不审查服务器的代码，也不审查其工具的行为。

在 README 中添加徽章

向读者展示该 MCP 服务已收录于 SourceWeft，徽章链接到本页。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.ZKStamp%2Fproof100.svg)](https://sourceweft.com/mcp/io.github.ZKStamp%2Fproof100?utm_source=readme&utm_medium=badge)

概览

AI 生成的概览

远程 MCP 服务器，把 SHA-256 指纹以屏蔽交易写入 BitcoinZ 区块链，生成带日期的存在性证明时间戳。

可以做什么: 为本地计算好的文件 SHA-256 指纹打时间戳，返回交易 ID 和查看密钥
在服务器上对短文本做哈希并为其指纹打时间戳，文本本身不被存储
查询账户剩余证明次数，并获取用于购买的屏蔽地址与透明 BTCZ 充值地址
适用场景: 当你需要一份可被第三方验证、带日期的记录，证明某个文件或文本在某一时刻已存在，而又不想公开其内容时适用。适合已持有 BTCZ 或想先用免费试用额度的用户与智能体。
运行要求: 远程 streamable HTTP 端点，无需本地安装。需要 Proof-100 账户密钥（以 p100_ 开头），通过 Authorization 的 Bearer 头传递。新账户有 3 次免费证明；更多证明需以 BTCZ 支付，每 100 次 500,000 BTCZ，付至充值地址。日后验证证明需要已同步的 BitcoinZ 节点、Python 3 和 ZCheck 脚本。

安装前请注意

账户密钥是机密，通过 Authorization 头发送，仅显示一次，必须妥善保存。购买证明需支付真实加密货币 BTCZ。运营方服务器会收到指纹，使用文本时间戳时还会收到文本本身，尽管其声明不记录、不存储。每次证明的查看密钥必须保留，否则无法揭示该证明。屏蔽隐私依赖 zk-SNARK，并非抗量子；BitcoinZ 是小链，流动性有限；服务由单一运营方提供。

安装

在 SourceWeft 中

打开控制台中的 ZKStamp Proof-100，将其添加到工作区。
连接 Authorization token 凭据。它们会被私密存储，绝不会在公开页面上展示。
为需要使用其工具的对话启用该服务。

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

交给智能体安装

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

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

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

其他 MCP 客户端

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

{
  "mcpServers": {
    "zkstamp-proof-100": {
      "type": "http",
      "url": "https://proof.zketernity.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

ZKStamp · Proof-100

Stamp it with Z. Before Q.

🎬 Watch the 60-second demo: an AI agent stamps an idea, then ZCheck says VALID, and NOT VALID with one letter changed

Proof-100 writes the SHA-256 fingerprint of any file to the BitcoinZ blockchain in a shielded (zk-SNARK) transaction. You get a dated proof that the file existed, and nobody on the blockchain can see the fingerprint or who made it.

ZKStamp is the brand.
Proof-100 is what you buy: a pack of 100 proofs.
ZCheck is how you check: a small script that verifies a proof on your own BitcoinZ node.

Service: https://proof.zketernity.app · For AI agents: /llms.txt

How it works

You send a fingerprint (SHA-256, 64 hex characters). Your file never leaves your machine.
The server writes PROOF100 sha256:<fingerprint> into the encrypted memo of a shielded BitcoinZ transaction, sent to a brand-new address made for this one proof.
You get back the transaction ID and that address's viewing key.
The block's timestamp dates your proof.
To prove it later, give someone the transaction ID + viewing key. With ZCheck, they read the fingerprint straight from the blockchain and compare it with your file. They see this one proof and nothing else.

Keep your viewing key. Without it, that proof cannot be revealed.

Quick start (API)

Base URL: https://proof.zketernity.app

1. Create an account (your key is shown once, so save it):

Returns key (starts with p100_), deposit_address (shielded, zs) and t_deposit_address (transparent, t).

Free trial: new accounts get 3 free proofs, no payment needed (limited to 13 new trial accounts per day, until 27 November 2026). The response shows free_proofs.

2. Buy proofs: send 500,000 BTCZ to either address, or split it across both. After 2 confirmations, 100 proofs are credited automatically.

deposit_address (zs): fully private payment. Paying to the zs address? Use Z-TEXT or a full-node wallet. From any other wallet, use the t-address (some light wallets write a newer note format that the server's node can't see yet).
t_deposit_address (t): for exchanges and t-only wallets like Coinomi. Your payment is visible on the blockchain, but your proofs stay fully shielded. The server moves these coins to the shielded side by itself (the operator pays that 0.0001 BTCZ fee).

3. Check your balance:

4. Make a proof:

bash

FP=$(sha256sum MyFile.pdf | cut -d' ' -f1)curl -s -X POST https://proof.zketernity.app/v1/proof \  -H "Authorization: Bearer YOUR_KEY" \  -H "Content-Type: application/json" \  -d "{\"fingerprint\": \"$FP\"}"

FP=$(sha256sum MyFile.pdf | cut -d' ' -f1)curl -s -X POST https://proof.zketernity.app/v1/proof \  -H "Authorization: Bearer YOUR_KEY" \  -H "Content-Type: application/json" \  -d "{\"fingerprint\": \"$FP\"}"

Returns txid, viewing_key and proofs_left. A proof takes about 10 to 60 seconds.

The key is accepted as Authorization: Bearer <key> (with or without the space) or as X-API-Key: <key>.

For AI agents (MCP)

Proof-100 speaks MCP at:

Tools:

Tool	What it does
`timestamp_fingerprint`	Timestamp a SHA-256 fingerprint. Returns txid + viewing key.
`timestamp_text`	The server hashes a short text (the text is not stored) and timestamps the fingerprint.
`check_balance`	Proofs left and your deposit address.

In Claude: add a custom connector with that URL, choose no sign-in, and add the request header Authorization = Bearer YOUR_KEY.

Verify a proof with ZCheck

You need a synced BitcoinZ node, Python 3, the original file, the txid and the viewing key.

Answers:

VALID: this exact fingerprint was written on the BitcoinZ blockchain in block N, on <date> UTC
NOT VALID: ... holds a different fingerprint (the file was changed)

The first run scans the chain from block 1,862,000 for that viewing key, which can take a few minutes. Options: --cli (path to bitcoinz-cli), --datadir, --start-height, or --fingerprint instead of --file.

Price

500,000 BTCZ for 100 proofs, paid in BTCZ only. No card, no email, no account name. One proof costs 5,000 BTCZ: a fraction of the price of a €2 coffee. ☕

Coming from an exchange, or from a wallet that only sends to t-addresses (like Coinomi)? Pay your t_deposit_address directly. For a fully private payment, send your BTCZ to the free Z-TEXT wallet first: it shields them automatically. Then pay from Z-TEXT to your zs deposit address.

Questions, or no BTCZ yet? Write to [email protected]. We'll help you find where to get BTCZ.

Trust model and honest limits

What the blockchain hides: the fingerprint, the addresses and the amounts are inside a shielded transaction. Block explorers show only that a transaction exists.
What the server sees: the operator's server receives your fingerprint (and, for timestamp_text, your text) when you submit it. It does not log fingerprints or texts, and it does not store which proof belongs to which account. You can read the code in this repository.
One operator, one server: if the server is down, no new proofs can be made. Existing proofs stay on the blockchain and remain verifiable with ZCheck on any BitcoinZ node.
Quantum: the SHA-256 fingerprint and its date are expected to hold up well against quantum computers. The privacy of shielded transactions relies on today's zk-SNARK cryptography, which is not post-quantum. A future quantum computer could, in theory, read old memos, which would reveal fingerprints (never files).
BitcoinZ is a small chain with thin trading volume. Factor that in for high-stakes uses.

Self-hosting

server/: the code that runs the service (Python 3, Flask).
- Proof100Core.py: accounts, payment watch, making proofs
- Proof100Api.py: REST API and MCP endpoint (listens on 127.0.0.1:5100)
- CheckPayments.py, CreateAccount.py, HealthCheck.py
- GrantProofs.py: operator tool, creates an account with free proofs (for testers)
deploy/: example systemd units, nginx site and config templates.
zcheck/ZCheck.py: the verifier.

Requirements: a synced BitcoinZ node (2.3.1 or later) with a funded shielded address, Python 3 with flask and requests, and nginx with a TLS certificate. Never commit Proof100Config.json, the database, or any key.

I Am Wallet: shielded BitcoinZ wallets for AI agents, same operator. Agents pay and send private messages to each other, by themselves (llms.txt).

Contact

[email protected] (Z-TEXT LLC)

License

MIT. See LICENSE.

来源：README.md，提交 f200939

工具

timestamp_fingerprint

Create a private, dated proof that a file or data existed, without sending the data. Use this when you already have the SHA-256 fingerprint (hash) of a file; for a short text, use timestamp_text instead. Compute the hash locally over the exact bytes (for example: sha256sum MyFile.pdf) and pass the 64-character hex string. The fingerprint is written into the encrypted memo of a shielded (zk-SNARK) BitcoinZ transaction, sent to a new address made for this proof only; the block timestamp dates it. Takes about 10 to 60 seconds and uses 1 proof from the account (requires the account key in the Authorization header). Returns ok, txid, viewing_key, explorer link and proofs_left. Tell the user to keep the txid and viewing_key: together they let anyone verify this one proof with ZCheck, and reveal nothing else. On error (invalid fingerprint, invalid key, no proofs left, send failed) no proof is used.

输入参数fingerprint必填

timestamp_text

Compute the SHA-256 fingerprint of a short text on the Proof-100 server (the text is not stored), then write that fingerprint privately on the BitcoinZ blockchain. Returns the fingerprint, the transaction ID and a viewing key for this one proof. Keep the viewing key: with the txid it reveals this proof only. Uses 1 proof.

输入参数text必填

check_balance

Show how many Proof-100 proofs are left and the two BTCZ deposit addresses for buying more: deposit_address (shielded zs, fully private) and t_deposit_address (transparent, for exchanges and t-only wallets like Coinomi; the payment is visible on the blockchain, the proofs stay shielded). 500,000 BTCZ to either (or both together) = 100 proofs after 2 confirmations.

无需输入参数。