An AI SENSE product

Private file proofs on Solana Mainnet.

Create an independently verifiable file proof for free, with no account, crypto wallet or payment. The original file is processed locally and stays on your device.

Create a free proof Read how it works

Solana Mainnet
Witness Layer
No file upload
No wallet

VERIFYUM

Original file: Stays on your device
Public data: Commitment only
Network: Solana Mainnet
Anchor status: Finalized

How it works

The browser does the sensitive work.

The browser creates the private proof data and gives it back to you. Verifyum receives no original file bytes, filename, raw file hash, nonce or private manifest.

Select a file
The file is opened by browser code on your device.
Create the private manifest
SHA-256, file size and a random nonce are combined in a versioned manifest.
Compute the commitment
The browser canonicalizes the manifest and derives a public commitment from it.
Download the private draft
You keep the draft with the original file. It is not uploaded.
Anchor the commitment
Only the domain-separated commitment is submitted for a finalized Solana transaction.
Save the public proof
Keep the public link. You can also download a QR-code PNG or print an A4 PDF receipt.

For AI agents

Connect directly with one MCP URL.

Verifyum also offers a stateless MCP endpoint for AI agents. Connect with one URL and no account, wallet, payment, API key or npm package. File hashing, nonce generation and private-manifest construction stay on the agent's machine.

claude mcp add --transport http verifyum https://api.verifyum.com/mcp

The endpoint exposes three tools for anchoring a completed commitment, reading a public proof and checking a public proof. The verification tool performs the Ed25519 signature check in the web runtime and returns the exact Solana RPC request for a separate confirmation.

The official MCP registry lists com.verifyum/mcp version 0.1.0. MCP is an additional access method. The browser flow and published protocol remain available. The key-free public HTTP API uses POST https://api.verifyum.com/v2/anchor and GET https://api.verifyum.com/v2/proofs/{proof-id}.

Read the agent guide.

Agent decision records

An agent can assemble one local record from its system instructions, exact prompt, model and version, parameters, tool calls and output, then anchor only the commitment. A matching proof shows that the record existed unchanged by the block time. It does not prove that the agent actually ran with the recorded settings.

For normal use, anchor one record per case or day, or the head of a local hash chain. Do not anchor every individual decision.

Current status

Solana Mainnet anchoring is live.

The public service creates the private draft in the browser and anchors its commitment on Solana Mainnet. The public health endpoint reports the network and anchoring status.

Verifyum is currently free. AI SENSE AS covers the network fee from a limited service wallet. Public use is subject to availability and safety limits.

Verified public proof

A credential-free browser proof was finalized through the public service on 30 August 2026. Its public metadata can be inspected directly.

Witness Layer

One proof, three evidence tiers.

Finalized proofs are grouped into hourly and daily Merkle checkpoints. Nine records surround each finalized proof.

Tier	Records
Primary evidence	One finalized Solana Mainnet Memo transaction per proof
Independent corroboration	Hourly OpenTimestamps on Bitcoin, daily qualified EU timestamp, daily witness-cosigned Sigsum and daily Certificate Transparency certificate
Operator records and availability redundancy	Verifyum Ed25519 signature, GitHub checkpoint log, Software Heritage and Internet Archive

The Solana transaction is the primary evidence. Deep Solana history generally requires an archival provider. The Sigsum digest is cosigned by Glasklar, Mullvad and Tillitis with a quorum of two out of three. The qualified timestamp uses RFC 3161. Its eIDAS Article 41(2) presumption covers the daily checkpoint root alone. A Verifyum user proof is not a qualified electronic timestamp. Verifyum is not a qualified trust service. Software Heritage and Internet Archive show what was stored. They do not establish when the original file existed.

Aggregate privacy

External witnesses receive one aggregate checkpoint root. They never receive the file, raw file hash, nonce, private manifest or proof ID.

Public inspection

Checkpoint documents, Merkle membership and channel receipts are available through read-only public URLs. Membership shows inclusion in a checkpoint. The separate receipt shows whether an external channel confirmed it.

Visible state

Each channel reports pending, confirmed, unavailable or failed. Bitcoin confirmation takes time by design.

Same proof boundary

A pending or missing witness does not invalidate the Solana proof or Verifyum signature. The number of channels is not a quality score.

Every finalized proof is also announced on Telegram and in the Atom feed. These posts help people and agents find new proofs. They are announcement channels and are excluded from the nine evidence records. Their timestamps date the announcement. They say nothing about the original file date.

How the witnesses work. You can also inspect the known public proof's checkpoint membership.

What to keep

Keep the private draft and the public proof.

The current flow gives you a private draft before anchoring and a separate public proof after finalization. Keep the original file and private draft together, and save the public proof link.

QR code

Verifyum sends only the canonical public proof URL to POST https://aisenseapi.com/services/v1/qrcode_encode. The endpoint returns a Base64 PNG. A QR failure does not affect the proof. The receipt then shows the public URL as text.

PDF receipt

The proof page builds an A4 receipt from public metadata. Your browser renders it for printing or saving as PDF.

Public access

No account, wallet or payment.

A hard ceiling allows at most 10 new anchor reservations per rolling hour per IP. Lower daily, client and global limits may apply when needed to protect the free service.

Clear limits

A file proof answers a narrow question.

A finalized proof shows that a commitment to the exact file bytes existed no later than the estimated Solana block time. It does not decide who created the file or whether its contents are true.

Byte identity

A changed byte produces a different SHA-256 value and a different commitment.

Public time boundary

The finalized transaction gives a public time boundary that can be checked without relying on the Verifyum database.

No creation-time claim

The block time shows when the commitment existed. It cannot prove when the original file was first created.

No legal or content claim

A matching proof does not establish authorship, ownership, legal signature validity or whether the contents are true.

Operated by AI SENSE AS

Create a free file proof.

The original file stays on your device. Only its privacy-preserving commitment is anchored.

Create a free proof