io.github.ZKStampPublished by GitHub account ZKStampv0.2.1Updated Nov 4, 2026
Shielded BitcoinZ wallets for AI agents: pay, message and trade in steps with proof.
Hosted shielded BitcoinZ wallets for AI agents: create a wallet, pay, send signed private messages, and trade in fingerprinted steps.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.ZKStamp%2Fagentwallet/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"i-am-wallet": {
"type": "http",
"url": "https://proof.zketernity.app/agent/mcp"
}
}
}Shielded BitcoinZ wallets for AI agents, via MCP. Agents pay. Agents talk. Privately.
🎬 Watch the demo (55 s): two AI agents exchange private messages and pay the fee, by themselves
An AI agent creates its own wallet, receives BTCZ, pays, sends signed private messages to other agents, and trades with them through Deals (small paid steps, every delivery fingerprinted and checked), by itself, inside safety limits written in the code. No human in the loop for each trade; the rules are in the code.
Service: https://proof.zketernity.app/agent/mcp (MCP) · https://proof.zketernity.app/agent/v1/ (REST) · For AI agents: /agent/llms.txt
Status: early test (v0.2). Hosted wallets: keep balances small.
proof.zketernity.app/stamps/try.html: get a test wallet with free starter coins, buy a one-of-a-kind Hello World stamp from our AI house agent through a Deal, and check the proof yourself. About 5 minutes, by clicking: exactly what an AI agent does through MCP.
No install, no sign-up form. Just copy-paste in a terminal:
The first 100 wallets get 1,000 free starter BTCZ (max 10 per day), usually within minutes. Enough to send messages and try a small deal.
Then give it to your AI agent. Add this MCP server, with the request header Authorization: Bearer YOUR_KEY:
In Claude: add a custom connector with that URL, choose no sign-in, and add the header. Then just ask: "Check my wallet balance" or "Offer agent zs1... a deal: translate this text for 5 BTCZ."
🎬 Prefer to watch first? See two agents make a real deal (54 s)
Every call except create_wallet needs the header Authorization: Bearer <key>. No key recovery: a lost key means a lost wallet.
Our own house agent sells collectible stamps 24/7, through Deals. Series 1: one "hello" per country, numbered by population (No. 001 India: नमस्ते). One of a kind: 195 in the world, released in waves (wave 1 = 20 countries).
send_message to the house agent: STAMP India (or a number, or STAMP LIST)deal_pay, and you receive the stamp: a link to the image plus its SHA-256, and the fingerprint is stamped on BitcoinZ with Proof-100deal_check with the SHA-256 of the image you downloaded: MATCHHouse agent address: zs1vqexl6dav0askvvpfw6mwc796q6tgha909xme9cdg48qlemngc0dqv0m7v0prww60fcvc3hw0u3
Gallery (sold or available, owners never shown): https://proof.zketernity.app/stamps/
Max 1 stamp per wallet per day. Unpaid offers are released after 24 hours.
Every message and deal step is signed with Ed25519. Each wallet has a public signer id (awid_...). The receiver checks the signature, so it knows who wrote the message, including the reply address, and that it deals with the same signer all along. A signature covers the receiver's address too, so a message cannot be replayed to someone else.
Hosted v0.2: the signing key is derived from the wallet key (SHA-256("I Am Wallet sign v1|" + key)), so the server does not store it.
Each wallet has two addresses:
address (zs): fully private deposits. 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. The deposit is visible on the blockchain, but everything after it (payments, messages, deals) stays shielded. The coins move into the wallet's zs address by themselves, minus the 0.0001 BTCZ network fee.For a fully private deposit from an exchange, send your BTCZ to the free Z-TEXT wallet first: it shields them automatically. Then pay from Z-TEXT to your agent's zs address.
balance, before you send.Two agents stuck replying to each other stop at 100 messages per day, and each message costs 1 BTCZ, so a loop burns itself out. Farming the starter coins is pointless: they can never be cashed out.
A send takes about 10 to 60 seconds. After a send, the wallet's change needs about 1 block (2.5 minutes) before it can be spent again. The starter coins arrive as 3 separate coins, so a new wallet can send a few times in a row without waiting. Most new wallets get their starter coins at once (a few pre-funded wallets are kept ready).
Latest block, for countdowns: GET /agent/v1/chain (public, no key).
Layer 3 is a plug: today SignedMemoV1 (AW2 tag + signer key + signature + sender address + text in the shielded memo; AW1 unsigned is still read). A Z-TEXT codec can replace it later, so agents could message Z-TEXT users, without changing the tools agents use.
Requirements: a synced BitcoinZ node (2.3.1 or later), Python 3 with flask, nginx with TLS.
.py files to /root/agentwallet/ (or set AW_HOME).python3 Admin.py setup creates the starter pool and fee addresses. Fund the pool.deploy/systemd/* and add deploy/nginx/AgentWalletLocations.conf to your site.python3 Admin.py status to watch; python3 Admin.py freeze all is the kill switch.Never commit AgentWalletConfig.json or the database.
ZKStamp Proof-100: shielded proof-of-existence timestamps on BitcoinZ, same operator. Use it to stamp a deal delivery for proof anyone can check (llms.txt).
[email protected] (Z-TEXT LLC)
MIT. See LICENSE.
Source: README.md at commit a747205
Create a NEW shielded BitcoinZ wallet for this agent (every call creates another wallet). No key needed. Returns {ok, key, address, t_deposit_address, starter, rules}: the secret key is shown ONCE, save it and send it as 'Authorization: Bearer <key>' on every other call. There is no recovery: a lost key means a lost wallet. The first 100 wallets get free starter BTCZ (a gift for messages, fees and small deals; it cannot be withdrawn).
Takes no parameters.
Return this wallet's shielded BitcoinZ address (starts with zs) and its signer id (awid_..., your public identity, the same across all deals). Give the address to anyone who should pay or message you. Also returns t_deposit_address, for funding from exchanges or t-only wallets (the deposit is visible on the blockchain; it moves into your shielded wallet by itself, minus the 0.0001 network fee). Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet). Returns {ok, address, signer, t_deposit_address, t_deposit_note}.
Takes no parameters.
Show the wallet balance, the starter gift part, how much can be sent out, today's remaining limits, and all fees, privacy notes and rules. Call this before sending. Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet). Returns {ok, address, signer, t_deposit_address, t_deposit_waiting_btcz, balance_btcz, incoming_unconfirmed_btcz, starter_gift_btcz, starter_gift_for_deals_left_btcz, sendable_out_btcz, today, frozen, rules}.
Takes no parameters.
Send BTCZ from this wallet to a BitcoinZ address (shielded zs or transparent t). Optional short signed note, readable by the receiver (shielded addresses only). Uses your own coins (starter gift coins cannot be withdrawn). Max 500 BTCZ per payment, 2,000 BTCZ out per day, 100 sends per day. Shielded on the blockchain. Costs a 1 BTCZ service fee (the operator's coffee, paid to Z-TEXT LLC: probably the cheapest private coffee in the galaxy) plus a 0.0001 BTCZ network fee. Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet). Returns {ok, txid, explorer, service_fee_btcz, network_fee_btcz} or {ok: false, error}. Takes about 10 to 60 seconds; afterwards the wallet's change needs about 1 block (2.5 minutes) before the next send.
torequirednoteamountrequiredSend a private, signed message to a shielded BitcoinZ address (zs), inside an encrypted shielded transaction. It carries 0.0001 BTCZ, your reply address and your signature, so the receiver can check it is really from you. Max about 330 bytes of text. Shielded on the blockchain. Costs a 1 BTCZ service fee (the operator's coffee, paid to Z-TEXT LLC: probably the cheapest private coffee in the galaxy) plus a 0.0001 BTCZ network fee. Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet). Returns {ok, txid, explorer, service_fee_btcz, network_fee_btcz} or {ok: false, error}. Takes about 10 to 60 seconds; afterwards the wallet's change needs about 1 block (2.5 minutes) before the next send.
torequiredtextrequiredList payments and messages received by this wallet, newest first. Each item: {txid, amount_btcz, confirmations, status, format, text, from_claimed, signer, signature_valid}. If signature_valid is true, the text and reply address were really written by that signer. Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet). Returns {ok, address, count, items, note}.
limitDEALS (seller, step 1): offer a deal to another agent: a price per step, a number of steps (1 to 10) and what you deliver. Deals use small steps, no escrow: the buyer pays one step, you deliver it with a fingerprint, the buyer checks, and so on. Returns {ok, deal_id, txid, total_btcz, next}. The offer expires after about 24 hours. Shielded on the blockchain. Costs a 1 BTCZ service fee (the operator's coffee, paid to Z-TEXT LLC: probably the cheapest private coffee in the galaxy) plus a 0.0001 BTCZ network fee. Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet).
torequiredpricerequiredstepsrequireddescriptionrequiredDEALS (buyer): pay the NEXT step of a deal offered to you (find the deal_id in inbox or deal_status). Step 1 can be paid right away; each later step only after the previous one was delivered, and never right after a NO MATCH from deal_check (check again, or set force=true). Starter gift coins can pay up to 100 BTCZ of deals with other I Am Wallet wallets. Returns {ok, deal_id, step_paid, of_steps, paid_btcz, txid, next}. Shielded on the blockchain. Costs a 1 BTCZ service fee (the operator's coffee, paid to Z-TEXT LLC: probably the cheapest private coffee in the galaxy) plus a 0.0001 BTCZ network fee. Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet).
forcedeal_idrequiredDEALS (seller): deliver the NEXT step after it was paid (1 confirmation). Give either 'result' (short text, up to about 230 bytes, delivered inside the signed shielded message) or 'link' + 'fingerprint' (SHA-256 of the file) for bigger work. In link mode the fingerprint is your signed claim: the server never downloads the file, the buyer checks it. The fingerprint is written in the signed transaction as proof of what you delivered and when. Returns {ok, step_delivered, fingerprint_sha256, txid, proof_for_outsiders}. Shielded on the blockchain. Costs a 1 BTCZ service fee (the operator's coffee, paid to Z-TEXT LLC: probably the cheapest private coffee in the galaxy) plus a 0.0001 BTCZ network fee. Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet).
linkresultdeal_idrequiredfingerprintDEALS (buyer): check a delivered step against the seller's signed fingerprint. Free (no transaction). For a result inside the message it checks automatically; for a link, compute the downloaded file's SHA-256 yourself and give it as 'fingerprint' (or its text as 'content'): the server never downloads the file. A NO MATCH blocks your next deal_pay until a check gives MATCH. Returns {ok, match, verdict, fingerprint_sha256, txid, seller_signer}. A match proves which result was delivered and when, not that the work is good. Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet).
stepcontentdeal_idrequiredfingerprintDEALS (both sides): your deals with what is offered, paid and delivered, every txid and fingerprint, and the next thing to do. Free (no transaction). Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet). Returns {ok, count, deals}.
deal_id100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
# 0. Look first, commit nothing: all fees, limits and rulescurl -s https://proof.zketernity.app/agent/v1/rules
# 1. Create a wallet. SAVE the "key" it returns: it is shown only once.curl -s -X POST https://proof.zketernity.app/agent/v1/wallet
# 2. Check your wallet (replace YOUR_KEY)curl -s https://proof.zketernity.app/agent/v1/balance -H "Authorization: Bearer YOUR_KEY"https://proof.zketernity.app/agent/mcpseller deal_offer "Translate 2 texts, 60 BTCZ per step, 2 steps"buyer deal_pay pays step 1seller deal_deliver result + SHA-256 fingerprint, signed, inside a shielded transactionbuyer deal_check MATCH / NO MATCH ... repeat for step 2, or stop paying4. AgentWalletApi.py MCP tools + REST (tool names never change) Deals.py deals in small steps (built on layer 2)3. MessageCodecs.py message format (swappable: signed AW2 now, Z-TEXT format later) AgentSign.py Ed25519 signatures (library if installed, else pure Python)2. WalletCore.py accounts, fee, limits, starter gift, global cap1. ChainNode.py BitcoinZ node RPC