Muhr
Planning · nothing released yet

This file existed on this day. Unchanged.

Muhr binds only a file’s hash to Bitcoin and an open log. Anyone can check the proof without our server.

No tokenNo custodyYour file never leaves

Illustration: a 64-character SHA-256 hash lifts off a document, becomes the rim of a wax seal, and the seal is linked through a Merkle branch into a Bitcoin block.

01 · What it proves

It proves when. Not who.

We state the limit up front: the seal shows the date and the integrity. Who signed is shown by the e-signature itself.

Proves

  • It existed by this dateBy Bitcoin block time, accurate to a few hours.
  • Not a single byte changedIf the hash differs, so does the file.
  • Checkable without usThe receipt, the open ots client and Bitcoin headers are enough.

One letter, a completely different hash. That is why a hash is a file’s fingerprint.

Does not prove

  • Who wrote or signed itAn EIMZO (PKCS#7) signature does that. Muhr only displays it.
  • That the content is trueMuhr does not read or judge the file.
  • NotarisationIt is extra, independently checkable evidence. It does not replace an official RFC 3161 timestamp.
02 · How it works

Five steps. Your file stays on your device.

Only a 64-character hash is sent. Everything else is open standards.

  1. Hash

    SHA-256 is computed in the browser or the CLI.

    Works below
  2. Log

    The hash goes into an open, append-only Merkle log (RFC 9162 style).

    Soon
  3. Bitcoin

    The log root reaches a Bitcoin block through public OpenTimestamps calendars. It takes a few hours.

    Soon
  4. Receipt

    .muhr.json: an inclusion proof plus the .ots file. You keep it.

    Soon
  5. Verify

    Browser, CLI or Telegram bot. Works even if our server is gone.

    Soon

Even if Wonmor disappears, the proof still works: verification relies on Bitcoin headers and the open ots client.

03 · Try it

The hash is computed right here, now.

Type text or drop a file. Nothing is sent. Anchoring to Bitcoin is not built yet.

or drop it here

SHA-256 · 64 hex

.muhr.jsonPreview · format v0 not final

Computed on your device with WebCrypto. Neither the text nor the file is sent anywhere.

04 · Who it is for

For work that has a signature and needs a date.

The first user is Wonmor itself: releases and articles.

Open-source maintainers

First: bitg releases

Release files get sealed: whoever downloads them can check they are exactly these bytes.

release-x64.msisoon
release_amd64.debsoon
release-universal.pkgsoon
SHA256SUMSsoon

Lawyers and freelancers

Planned

Contracts, deliverables, designs: evidence that "I had this on that day".

Writers and researchers

First: wonmor.io articles

Show that an article was not quietly edited after it was published.

v1 sealed9f2c…a07e
v2 different hash41d8…3b10

Businesses, via API

Later

For contract archives and reports. Paid in som, as an ordinary software service.

POST /stamp {"hash": "9f2c…a07e"} GET /proof/9f2c…a07e → .muhr.json
06 · Roadmap

Eight weeks to v0.1, in the open.

An order, not dates. Each stage gets ticked here when it is done.

  1. Week 1–2

    CLI and log

    muhr stamp/verify, Merkle log, .muhr.json v0. First seals: bitg releases and wonmor.io articles.

    Soon
  2. Week 3–4

    API and verifier page

    POST /stamp, GET /proof, offline verification in the browser.

    Soon
  3. Week 5–6

    Telegram bot and PKCS#7

    Send a file, get a receipt. EIMZO signatures shown with a "not cryptographically verified" label.

    Soon
  4. Week 7–8

    GitHub Action and v0.1

    Automatic sealing of release files, security page, threat model.

    Soon

A second log

Log roots also written to Sigstore Rekor or another open log.

Later

Business API

Volume, SLA, on-premise install. Paid in som.

Later

For agents

stamp_hash MCP tool: an agent seals its own output.

Later
07 · Honest status

Today this is a plan. No code yet.

What exists and what does not. Updated monthly.

Muhr will never ask for money, keys, a seed phrase or crypto, and will never message you first. The only official addresses are muhr.wonmor.io and github.com/wonmortech.

Research and plan
done
Hash demo on this page
works
CLI, API, log
soon
Anchoring to Bitcoin
soon
Users
none yet
Security audit
planned
Legal opinion
questions ready

Let’s press the first seal together.

Have an idea, a question or found a mistake? Open an issue on GitHub. The plan and the research are public.