Open-source maintainers
First: bitg releasesRelease files get sealed: whoever downloads them can check they are exactly these bytes.
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.
We state the limit up front: the seal shows the date and the integrity. Who signed is shown by the e-signature itself.
ots client and Bitcoin headers are enough.One letter, a completely different hash. That is why a hash is a file’s fingerprint.
Only a 64-character hash is sent. Everything else is open standards.
SHA-256 is computed in the browser or the CLI.
Works belowThe hash goes into an open, append-only Merkle log (RFC 9162 style).
SoonThe log root reaches a Bitcoin block through public OpenTimestamps calendars. It takes a few hours.
Soon.muhr.json: an inclusion proof plus the .ots file. You keep it.
Browser, CLI or Telegram bot. Works even if our server is gone.
SoonEven if Wonmor disappears, the proof still works: verification relies on Bitcoin headers and the open ots client.
Type text or drop a file. Nothing is sent. Anchoring to Bitcoin is not built yet.
Computed on your device with WebCrypto. Neither the text nor the file is sent anywhere.
The first user is Wonmor itself: releases and articles.
Release files get sealed: whoever downloads them can check they are exactly these bytes.
Contracts, deliverables, designs: evidence that "I had this on that day".
Show that an article was not quietly edited after it was published.
For contract archives and reports. Paid in som, as an ordinary software service.
Open standards only. The code will ship under Apache-2.0.
wonmortech/muhrRust CLI, .NET API and web verifier
wonmortech/muhr-actionGitHub Action that seals release files
wonmortech/muhr-spec.muhr.json format specification
An order, not dates. Each stage gets ticked here when it is done.
muhr stamp/verify, Merkle log, .muhr.json v0. First seals: bitg releases and wonmor.io articles.
POST /stamp, GET /proof, offline verification in the browser.
Send a file, get a receipt. EIMZO signatures shown with a "not cryptographically verified" label.
SoonAutomatic sealing of release files, security page, threat model.
SoonLog roots also written to Sigstore Rekor or another open log.
LaterVolume, SLA, on-premise install. Paid in som.
Laterstamp_hash MCP tool: an agent seals its own output.
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.
Have an idea, a question or found a mistake? Open an issue on GitHub. The plan and the research are public.