Privi Anchor: On-Chain Proof-of-Existence

    1

    Anchor file hashes to the Base blockchain for immutable proof-of-existence and integrity verification.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Privi Anchor: On-Chain Proof-of-Existence

    Example session with this skill installed

    Anchor the SHA-256 hash 5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8 for the project design spec.

    • Read your context and instructions
    • Compiled the privi anchor

    I have anchored the hash for your project design spec on the Base blockchain. The transaction was successful, and I have generated the receipt details for your records.

    Anchor Receipt

    FieldValue
    Labelproject-design-spec
    SHA-256 Hash5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8
    Transaction Hash0x7a2d...e4b1
    BlockchainBase (Mainnet)
    Block Number12458932
    Merkle Proof["0xbf3...","0xde1..."]
    StatusConfirmed

    Next steps

    1. Save the receipt data as design-spec.anchor.json in the same directory as the source file.
    2. Use the anchor_verify command if you need to audit the file's integrity in the future.
    3. Ensure you keep the original file unchanged; any modification will result in a hash mismatch during verification.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Manual proof-of-existence workflows are slow and prone to record-keeping errors. This skill enables agents to generate immutable timestamps and cryptographic proofs for files, documents, or datasets by anchoring their hashes directly to the Base blockchain. It provides a verifiable trail of integrity for intellectual property, legal contracts, and versioned data without exposing the raw content to the network.

    What it does

    • Immutable anchoring records SHA-256 hashes on the Base blockchain for permanent proof-of-existence.
    • Batch processing handles up to 100 hashes in a single transaction to optimize gas usage and latency.
    • Cryptographic verification validates existing receipts against on-chain data to confirm file integrity.
    • Status monitoring checks chain health and wallet gas levels to ensure transaction reliability.
    • Receipt management generates structured data including transaction hashes and Merkle proofs for local storage.

    How it works

    1. Hash generation involves calculating the SHA-256 of local files or using the text anchoring tool for non-sensitive strings.
    2. Anchor execution sends the hash to the Base network via the Privi Anchor MCP server.
    3. Receipt storage saves the returned transaction hash and Merkle proof as a JSON sidecar file.
    4. Verification recomputes the file hash and compares it against the stored proof and on-chain records.

    Frameworks & tools

    Built for agents using the Model Context Protocol (MCP). It interacts with the Base blockchain (Chain ID 8453) via a hosted endpoint.

    Why this beats prompting it yourself

    Standard agents cannot interact with blockchain state or perform cryptographic verification against live networks. This skill provides the specific tool definitions and receipt-handling logic required to interact with the Privi Anchor API reliably.

    Use cases

    • IP protection by anchoring creative assets or codebases at specific milestones.
    • Legal compliance by timestamping signed PDF contracts or agreements.
    • Data integrity for machine learning datasets to prove they haven't been tampered with.
    • Audit trails for regulatory documents that require third-party verification.

    Known limitations

    Requires an API key for anchoring operations. The skill only transmits hashes to the network, meaning the original file must be stored locally to perform future verification.

    Requires an API key for anchoring. Supports up to 100 hashes per batch. Original files must be retained locally for verification.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 20 days ago

    Permissions

    Network Access
    Listed20 days ago

    What's inside

    Frequently Asked Questions

    This skill solves the 'timestamping problem' by anchoring file hashes to the Base blockchain, providing a permanent, tamper-proof record that a document existed in a specific state at a specific time without revealing the file's contents.

    Privi Anchor is built on the Model Context Protocol (MCP), making it compatible with any MCP-enabled AI environment, including Claude Desktop, IDE-based agents, and custom autonomous agents.

    No, the original file is never uploaded; the skill only calculates and transmits the SHA-256 hash. You must retain the original file and the generated receipt locally to perform future integrity verifications.

    Setup involves adding the MCP server to your agent's configuration file and providing a valid API key for the Privi Anchor endpoint. The skill then automatically handles the complex blockchain interactions and receipt management for you.

    The skill includes a 'Batch Processing' tool that allows your agent to anchor up to 100 hashes in a single transaction, significantly reducing gas fees and processing time compared to individual requests.

    New in APIs & Backend