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.

無需輸入參數。