// WHITEPAPER · v0.1 · MAY 2026

HERMAUDE.
Two minds witness.
One receipt proves.

A provenance protocol for AI output. Two independent models — one open-weight, one closed-weight — witness every prompt. Each response carries a canonical SHA-256 hash, optionally sealed on Solana. Anyone can verify.

VERSION 0.1 NETWORK Solana LAUNCH 14 May 2026 · 3PM UTC STATUS Devnet preview live

01 Abstract

HERMAUDE is a protocol for AI output provenance. Today, an AI model can produce confident text that looks indistinguishable from careful reasoning — but there is no built-in way to attest to what was said, by which model, against which prompt, at what time.

HERMAUDE solves this by running every prompt through two independent witnesses — Hermes (an open-weight model from Nous Research) and Claude (a closed-weight model from Anthropic). Their responses are bundled with a canonical hash, stored as a receipt, and optionally sealed on Solana.

The result is a portable, verifiable, tamper-evident record of every AI output: two witnesses, one receipt, one truth.

02 The problem

AI is being deployed at scale across high-stakes domains:

  • Legal contracts use AI to draft, summarize, and review clauses
  • Medical notes are partially written by AI scribes
  • Research papers cite AI-generated literature reviews
  • Crypto trading desks act on AI-generated theses

None of this output carries provenance. There is no receipt. No second opinion. No timestamped record. If a model hallucinates a clause, mis-summarizes a study, or fabricates a citation, the harm is real — but the trail is gone.

⚠ The asymmetry
AI output is treated like authoritative input. But unlike a notary, a doctor's signature, or a journalist's byline, AI output has no witness. The reader has to trust without verification.

HERMAUDE removes this asymmetry. It does not promise that AI is always right. It promises that whatever the AI said, someone else also saw it say something — and the record is signed.

03 How HERMAUDE works

Every HERMAUDE receipt is generated in four steps:

// 01
Prompt
User submits a prompt + optional system prompt.
// 02
Witness
Hermes and Claude respond in parallel. No shared context.
// 03
Consensus
A score (0-100%) is computed from lexical + structural agreement.
// 04
Seal
Receipt is canonicalized, SHA-256 hashed, optionally minted on Solana.

Both witnesses run independently — there is no relay between them. Hermes does not see Claude's response. Claude does not see Hermes'. They are not given knowledge that they are being watched. This is essential: the value of two witnesses comes from their independence.

04 The receipt

Every receipt is a JSON object with a stable canonical form. Once the receipt is built, it is serialized into canonical UTF-8 JSON and SHA-256 hashed. The hash is the receipt's identity.

{
  "id": "HMAUDE-2026-0514ABCDEF",
  "version": "1.0",
  "createdAt": "2026-05-14T15:00:00.000Z",
  "prompt": "Should AI agents trade crypto autonomously?",
  "promptHash": "dfd995e78bb65fa6...",
  "witnesses": {
    "a": {
      "role": "hermes",
      "response": {
        "model": "nousresearch/hermes-4-405b",
        "output": "...",
        "tokensIn": 74,
        "tokensOut": 81,
        "latencyMs": 1860
      }
    },
    "b": {
      "role": "claude",
      "response": {
        "model": "claude-haiku-4-5",
        "output": "...",
        "tokensIn": 64,
        "tokensOut": 77,
        "latencyMs": 942
      }
    }
  },
  "consensus": {
    "score": 44,
    "verdict": "disputed",
    "breakdown": {
      "jaccard": 0.22,
      "cosine": 0.27,
      "lengthRatio": 0.98,
      "structural": 1.0
    }
  },
  "hash": "eff0ba50dc894faba4cceb7d697d6346..."
}

A receipt is portable. A receipt is signed. A receipt cannot be edited without changing the hash.

⌘ Key property
The hash binds the prompt, both witnesses' full outputs, the consensus result, and the timestamp — all in one immutable fingerprint. Change any field, and the hash changes.

05 Consensus algorithm

HERMAUDE computes a 0-100 consensus score using four lexical and structural signals:

SignalWhat it measuresWeight
JaccardVocabulary overlap (shared content words / union)30%
CosineTF-IDF cosine similarity (semantic vector closeness)40%
Length ratioHow similarly long the two outputs are15%
StructuralMatch in numbered lists, bullets, code blocks, etc.15%

The score is mapped to a verdict:

  • verified — score ≥ 75 — both witnesses substantially agreed
  • partial — score 45–74 — material overlap, some divergence
  • disputed — score < 45 — independent reasoning produced different conclusions
⌘ Note on semantics
Consensus is lexical, not semantic. Two outputs that say the same thing in very different words may score low. This is a feature, not a bug — a low score is an invitation to look at the witnesses' outputs and judge for yourself.

Future versions will add an optional semantic-embedding consensus signal weighted alongside the lexical signals.

06 Solana mint

Every receipt is identified by its SHA-256 hash. By default, this hash is stored in the HERMAUDE vault (Supabase, indexed for public retrieval). $HMAUDE holders unlock an additional capability: on-chain minting.

On-chain minting uses an Anchor program deployed to Solana. The hash is written into a program-derived account (PDA) along with a consensus score, timestamp, and receipt ID. Once written, the receipt is immutable, globally retrievable, and cryptographically inseparable from Solana's history.

Mint cost: ~0.001 SOL per receipt. Subsidized by the operations wallet, funded by $HMAUDE trading fees.

// Anchor instruction
pub fn mint_receipt(
  ctx: Context<MintReceipt>,
  hash: [u8; 32],
  score: u8,
  timestamp: i64,
  receipt_id: String,
) -> Result<()>

The PDA seed is [b"receipt", hash[..32]], making receipt addresses deterministic from the hash itself. Any verifier can independently derive the PDA, read the on-chain account, and confirm the receipt was sealed at a specific Solana slot.

07 $HMAUDE token

$HMAUDE is a fair-launch token on Solana via pump.fun. 1 billion supply, zero allocation to team or VC, no presale. Every $HMAUDE is bought from the open market.

ParameterValue
Symbol$HMAUDE
NetworkSolana (SPL Token)
Supply1,000,000,000 (fixed, non-mintable)
Launchpump.fun · 14 May 2026 · 15:00 UTC
Allocation100% public via bonding curve
Trading feesRoute to operations wallet (transparent on-chain)

The operations wallet is multisig-controlled and funds:

  • Hermes infrastructure (OpenRouter API costs initially; self-hosted GPU in Phase 2)
  • Claude API costs (Anthropic)
  • Solana mint fees for holder receipts
  • Continued protocol development

$HMAUDE is a utility token. It gates access to higher receipt tiers (see §08). It does not represent equity in any entity, revenue share, dividend, or claim on protocol assets.

08 Tier benefits

HERMAUDE has three tiers, gated by $HMAUDE balance:

TierRequiredBenefits
Free 0 $HMAUDE 1 receipt / 24h · vault-stored hash · public viewer · watermarked share card
Holder · Tier 1 ≥ 100K $HMAUDE Unlimited receipts · on-chain Solana mint · custom branding · bulk API · confidence band controls
Holder · Tier 2 ≥ 1M $HMAUDE All Tier 1 + white-label verifier widget · embed SDK · custom witness config · priority queue

Tier is computed from the holder's connected Solana wallet at the time of generation. Verification is read-only — HERMAUDE never spends, transfers, or interacts with holder wallets.

09 Use cases

1. Contract review.

Legal teams paste a clause into HERMAUDE and get a sealed receipt of two independent AI interpretations. If the contract is later disputed, the receipt is documentary evidence that two AI agreed (or didn't) on what the clause meant at signing time.

2. Medical AI scribes.

A doctor's AI-generated note can be passed through HERMAUDE before being added to the patient record. The hash is logged alongside the note; if the patient or insurer ever queries it, the original AI output is retrievable and verifiable.

3. Research provenance.

Citing an AI summary of a paper is currently impossible to verify. HERMAUDE produces a receipt for the summary, which can be cited like a primary source — HMAUDE-2026-XXXX — and anyone can later retrieve the exact two-witness output.

4. Trading thesis logs.

Crypto and quant desks generate trade theses with AI. HERMAUDE logs each thesis as a receipt before the trade is executed, providing post-hoc audit trail that the rationale was hashed before the outcome was known.

5. Journalism & op-ed sourcing.

Reporters using AI to draft, summarize, or fact-check can publish HERMAUDE receipts alongside articles — proof that the AI was consulted, what it actually said, and where the writer departed from it.

6. Customer-facing AI compliance.

Companies running AI customer support can include a HERMAUDE hash in every transcript. This becomes audit material for regulators concerned with biased, hallucinated, or inconsistent AI responses.

10 Roadmap

Phase 1 — Genesis (May 2026, NOW)

  • Devnet preview live with waitlist gating (1 receipt / 24h free)
  • $HMAUDE fair launch on pump.fun · 14 May 2026 15:00 UTC
  • Anchor program deployed to Solana mainnet
  • Token-gated tier system live

Phase 2 — Verification (Jun-Aug 2026)

  • Public receipt viewer page (hermaude.xyz/r/[hash])
  • Open-source verification SDK (TypeScript + Rust)
  • Self-hosted Hermes inference (cost optimization)
  • Semantic consensus signal (embedding-based)
  • Holder dashboard (full receipt history, search, export)

Phase 3 — Expansion (Q3-Q4 2026)

  • Third witness option (configurable: GPT, Gemini, Mistral, etc.)
  • API for institutional clients (auth, SLA, dedicated queue)
  • White-label embed widget
  • Cross-chain settlement (Ethereum, Base)

Phase 4 — Sovereignty (2027+)

  • Fully on-chain witness selection
  • Community-governed witness pool
  • Distributed witness verification (multiple inference providers)

11 Tech stack

HERMAUDE is built with production-grade open infrastructure:

LayerComponent
Witness AHermes 4 405B via Nous Research / OpenRouter
Witness BClaude (Anthropic API · current: Haiku 4.5 · upgrading to Opus 4.7 post-launch)
BackendFastify + TypeScript on Railway
DatabaseSupabase (Postgres + RLS)
ChainSolana · Anchor 0.31 · Rust
HashingSHA-256 of canonical JSON
FrontendVanilla HTML/CSS/JS · no SPA
HostingHostinger (static) + Railway (API)

The full backend source is private. Core protocol components — the consensus algorithm, receipt schema, and Anchor program — will be open-sourced under MIT in Phase 2.

12 FAQ

Is this just a chatbot wrapper?
No. A chatbot wrapper returns one model's output. HERMAUDE returns two independent models' outputs, computes consensus between them, hashes the entire bundle, and optionally seals the hash on Solana. The value is in the witnessing, not the chatting.
What if both models hallucinate the same thing?
It's possible. Two independent models can converge on the same mistake — that's why HERMAUDE never promises AI is right. What it promises is that whatever the AI said, two independent witnesses said it. The receipt is for accountability, not for ground truth.
Why two models? Why not three or five?
Two is the minimum for independent corroboration and the maximum for fast, affordable inference. Phase 3 will add optional third-witness configuration for higher-stakes use cases.
Why Solana?
Mint cost (~0.001 SOL per receipt), fast finality (~400ms), and the pump.fun launch infrastructure that supports fair token distribution without team allocation.
Is $HMAUDE a security?
$HMAUDE is a fair-launched utility token gating access to higher receipt tiers. There is no team allocation, no presale, no equity claim, and no revenue share. Holders are not investors in any entity — they are users of a protocol who happen to hold a tier-gating utility token.
What happens if Anthropic or Nous deprecates a model?
HERMAUDE always uses the current stable production model from each provider. Receipts are versioned (version: "1.0") so future model upgrades are transparent. Receipts generated under older versions remain verifiable indefinitely.
Can I run this myself?
Phase 2 will release the open-source verification SDK so anyone can independently verify a HERMAUDE receipt without trusting the protocol. The reference backend will likely remain closed-source for moat reasons, but the receipt format and verifier are designed to be implementation-independent.
What if my wallet gets hacked? Can someone steal my receipts?
Receipts are public records — there is nothing to steal. The wallet is used only to identify tier eligibility, not to sign transactions. HERMAUDE never has spend authority over your wallet.

13 References & links

Generate your first receipt.

Free tier · No wallet required · 1 receipt per 24h