Skip to content
Skills Library
Law & compliance · Review & audit

verifyum-proofs

/verifyum-proofs

Create and check Verifyum proofs that exact file bytes existed at a point in time, anchored on Solana Mainnet without uploading the file. Use when the user asks to timestamp, seal or prove a file, dataset, contract draft, log or agent decision record, or asks to check a Verifyum proof ID or proof URL. An anchor is a permanent public transaction, so never create one during setup, tests or exploration.

Licence
MIT
Last repository change
05.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
8
Deprecation

No signals detected. Repository changed on 05.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Create and check Verifyum proofs that exact file bytes existed at a point in time, anchored on Solana Mainnet without uploading the file. Use when the user asks to timestamp, seal or prove a file, dataset, contract draft, log or agent decision record, or asks to check a Verifyum proof ID or proof URL. An anchor is a permanent public transaction, so never create one during setup, tests or exploration.

Original author description

Create and check Verifyum proofs that exact file bytes existed at a point in time, anchored on Solana Mainnet without uploading the file. Use when the user asks to timestamp, seal or prove a file, dataset, contract draft, log or agent decision record, or asks to check a Verifyum proof ID or proof URL. An anchor is a permanent public transaction, so never create one during setup, tests or exploration.

How it works

  1. If the tools are missing
  2. Which tool for what
  3. Rules
  4. What a proof shows
  5. Check the connection
Original SKILL.md headings · 98 lines, 736 words
SKILL.md preview
---
name: verifyum-proofs
description: Create and check Verifyum proofs that exact file bytes existed at a point in time, anchored on Solana Mainnet without uploading the file. Use when the user asks to timestamp, seal or prove a file, dataset, contract draft, log or agent decision record, or asks to check a Verifyum proof ID or proof URL. An anchor is a permanent public transaction, so never create one during setup, tests or exploration.
compatibility: Needs the verifyum MCP server (https://api.verifyum.com/mcp, Streamable HTTP, no authentication), which this plugin's mcp.json declares as `verifyum`. The file tool needs `verifyum-local` as well (npx -y verifyum-mcp@0.1.1, Node.js 20 or later). Clients prefix the tool names, for example mcp_verifyum_verifyum_get_proof in Hermes Agent or mcp__verifyum__verifyum_get_proof in Claude Code.
license: MIT
---

# Verifyum proofs

Verifyum proves that a commitment to exact file bytes existed no later than a
Solana Mainnet block time. The file stays on the machine. Only a
domain-separated commitment is sent, and the public proof holds nothing that
identifies the file.

## If the tools are missing

If no `verifyum_` tool is available, the servers are not connected. Tell the
user to add the hosted server and start a new session, for example:

```bash
claude mcp add --transport http verifyum https://api.verifyum.com/mcp
hermes mcp add verifyum --url https://api.verifyum.com/mcp
```

The file tool comes from the local server, `npx -y verifyum-mcp@0.1.1`, which
needs Node.js 20 or later.

## Which tool for what

The plugin declares two servers. `verifyum` is the hosted server with three
tools. `verifyum-local` runs on this machine and has the same three plus the
file tool. When both are connected, use `verifyum-local`.

- **Prove a local file**: `verifyum_create_proof_from_file` on
  `verifyum-local`, with `path` and a `private_draft_path` that does not exist
  yet. It hashes the file, builds the nonce and private manifest, saves the
  private draft and anchors only the commitment. The answer has `proof_id`,
  `status`, `proof_url` and `private_draft_path`.
- **Anchor a commitment that already exists**: `verifyum_anchor_commitment`
  with `commitment` and `idempotency_key`. Use it only for a commitment built
  by Verifyum's own code: the local server, the single-file clients
  https://verifyum.com/clients/verifyum.py and
  https://verifyum.com/clients/verifyum.mjs, or
  https://verifyum.com/assets/verifyum-protocol.js. Never build the manifest
  or the commitment by hand. A wrong commitment is anchored all the same and
  will never match the file.
- **Follow a proof until it settles**: `verifyum_get_proof` with `proof_id`.
  The status is `queued`, `submitted`, `finalized` or `failed`.
- **Check a proof**: `verifyum_verify_public_proof` with `proof_id`. On
  `verifyum-local` it checks the Ed25519 service signature against the
  published key registry and also reads the transaction from a public Solana
  RPC endpoint without going through Verifyum. On the hosted `verifyum`
  server, Verifyum checks its own data and returns the exact RPC request, so
  the chain part can be confirmed separately. Tell the user which one ran.

## Rules

- Anchor only when the user has asked for a proof of that specific file or
  record. Never anchor while testing the connection, exploring, guessing what
  the user might want, working in bulk, or as a side effect of another task.
- Every anchor is a real, public and permanent Solana Mainnet transaction. It
  cannot be withdrawn. Public use is currently free and AI SENSE AS pays the
  network fee. That is current policy, not a guarantee.
- Never send the file, its name, its raw hash, the nonce or the private
  manifest to Verifyum, to a URL or into a message. The tools take only a
  commitment, an idempotency key, a public proof ID, or a local path on
  `verifyum-local`.
- The private draft ties the proof to the file and cannot be recreated. Tell
  the user to keep it next to the original. Do not print its contents.
- Retry with the same commitment and the same idempotency key. For the file
  tool, call again with the same `path` and `private_draft_path`, which
  resumes the saved draft. Never retry in parallel. Honor HTTP 429 and
  `Retry-After`.
- Public creation allows at most ten new anchors per rolling hour per IP
  address, with lower daily caps. For many records, keep a local hash chain
  and anchor its head.
- If the file tool answers that it is not configured, `VERIFYUM_MCP_ALLOWED_DIRS`
  is not set for `verifyum-local`. Tell the user which folder needs to be
  listed there and stop. Do not compute the commitment some other way.

## What a proof shows

A finalized proof shows that a commitment to the exact file bytes existed no
later than the estimated Solana block time, and that those bytes have not
changed since. It does not prove authorship, ownership, legal signature
validity, when the file was first created, or that its contents are true. Say
this plainly when you hand over a proof URL.

## Check the connection

This check reads a public proof and never anchors anything.

1. Call `verifyum_get_proof` with proof ID `72c38s8rrqa4vjhw6dxsvmbqkq`. The
   answer is status `finalized` on network `mainnet-beta`.
2. Call `verifyum_verify_public_proof` with the same ID. The verdict is
   `valid`. On `verifyum-local` the chain checks report slot `442907852` and
   block time `2026-08-30T14:59:44Z`. The hosted server gives the same slot
   under `chain_check.expect`.

Any other answer means the call did not reach Verifyum or something is wrong.
Stop and tell the user.

Reference: https://verifyum.com/agents and https://verifyum.com/docs/agent-api.md

Versions

The database has no other skills named verifyum-proofs.

Database snapshot: 13.11.2026 · package version 98072f8343df (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90Solana Security & Mainnet
    Guide users on security best practices, mainnet considerations, and risk management for blockchain operations. Activate when discussing mainnet operations, security concerns, or risk acceptance.
  • 90solana-accept-risk
    Accept or revoke explicit risk acknowledgment for mainnet-beta operations. Use this skill when the user runs /solana-accept-risk, asks to "enable mainnet", "accept risk", "revoke risk", or when mainnet operations are blocked.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.