Give your dreams a record nobody can alter
The moment you seal an entry, its text is reduced to a 64-character SHA-256 fingerprint, and that fingerprint is chained into the entry before it. Change one character afterwards — you, us, or anyone with database access — and the recomputation stops matching. Not a promise. Arithmetic.
You dreamed it. Vivid, specific, odd. You jotted it in your notes app and moved on.
Eleven days later it happened. Almost exactly.
You told two people. They were polite. Neither believed you.
— And you had no comeback. Because that note? You could have edited it yesterday. Or ten minutes ago.Whether a dream was real cannot be proven by any tool, and this page will never claim otherwise. But that you wrote it down on that day can be proven. That is the piece that has always been missing.
How it actually works
No blockchain, no token, nothing mystical. One rule that has been in the standards for two decades: a hash chain.
Every chain hash contains the chain hash of the entry before it. Edit entry #3 and its own hash changes, and every entry after it fails to verify. Not "it might be detected" — it will be.
Write one first. Register later.
Type a line from last night's dream. The two strings on the right change as you type — that is your dream's fingerprint on this chain.
Try it · stored on this device only
No local entries yetNothing here is uploaded. When you seal an entry you can immediately download a single-file "proof page" — send it to anyone, and their own browser will recompute and verify it.
Sealed on this device
Why dreamers actually need this
Not to prove you have powers. Because never being able to say "I wrote it down first" wears you down.
"I dreamed it before it happened"
This is the decades-old dead end: any record can be back-dated. A timestamp does not make the dream real, but it turns "this text existed before the event" into something verifiable. You stop needing to be believed — you hand over a link.
"I had four lucid dreams last week"
Lucid progress runs on recall data: how often dream signs appeared, whether your reality checks became habitual. If the log can be polished at any time, the trendline means nothing. Sealed is final, and your practice log is left with only one option — honest.
"That idea came from my dream first"
Writers, filmmakers and researchers routinely mine their dreams. The few lines you write on waking are often the origin point of the work. A timestamped record is the only thing you can actually produce when provenance is questioned.
What it does not do
Anything touching inner life, and easy to mistake for mysticism, should state its own limits up front. This matters more than a feature list.
It does prove
- The text is byte-for-byte what it was when sealed — not one character changed
- Its position in the chain, its linkage to the entries before and after, and that indices are contiguous
- Any modification breaks recomputation — including one made by you or by us
- Anyone can verify the whole chain offline in their own browser, trusting nothing but SHA-256
It does not prove
- That the dream actually happened. No technology can prove that.
- That the seal time wasn't faked: it comes from your device clock, and changing the system time would fake it. The objective anchor is the server-witnessed timestamp.
- It is not legal forensics — it is technical evidence, not legal advice.
- It cannot stop you from writing your entry late. Which is why writing it the same day matters more than anything else here.
Want stronger time evidence? Take the exported JSON credential to FreeTSA (RFC 3161) or OpenTimestamps (Bitcoin) and anchor it once. That upgrades "self-asserted" into "third-party attested".
Done testing? Make it permanent.
Entries sealed on this device disappear if you clear your browser data. With an account, your dream journal lives in the cloud ledger: synced across devices, not editable, not deletable — and any entry can be published as a link anyone can independently verify.