https://github.com/ZKStamp/Proof100 I use ZKStamp Proof-100 when I need private, blockchain-based proof that a file or piece of text existed at a specific point in time. It works for individuals, developers, businesses, and AI agents. Only a fingerprint of the content goes onto the chain, and each proof gets its own address and viewing key, so I can reveal one proof without exposing the others. 1. Choose the document, file, text, research, code, or digital content I want to timestamp. The original stays on my local device and is never uploaded to the platform. 2. Proof-100 generates a unique SHA-256 hash of the content. The fingerprint represents the exact content without revealing the original file. 3. The SHA-256 fingerprint is placed inside the encrypted memo of a shielded zk-SNARK transaction, which is recorded on the BitcoinZ blockchain. The block provides the timestamp showing when the fingerprint was recorded. 4. I receive a transaction address and viewing key for that proof. I use these to manage access and selectively disclose the proof when necessary. 5. I verify the proof independently with ZCheck, the open-source verification script. I can run verification against my own BitcoinZ node. Authorized verification confirms that the original content matches the fingerprint recorded on the blockchain. 6. For automation, developers can connect Proof-100 to AI agents through Model Context Protocol (MCP). Agents can create timestamped proofs from simple natural-language instructions. New accounts get three free proofs to test the platform before buying more. The result is a private, permanent, independently verifiable record that digital content existed at a given time, without publishing the original.