Seal a dreamwrite it, declare the target, lock it
Write the dream while it is still fresh, and say in advance what would count as it coming true. The moment you seal, its exact words are fixed to now and cannot be moved.
1 · THE DREAM · the exact words, as you remember them
Write it plainly. Detail is what makes a later hit meaningful.
2 · COUNTS AS TRUE IF · declared now, before the event
This is the whole discipline. You are calling the shot before you take it. A vague condition is not a prediction.
3 · SEAL
On seal, your browser computes SHA-256 over the dream, the condition, a random nonce, and the timestamp. Only that fingerprint is ever made public. The dream text is end-to-end encrypted in your browser with your passphrase before it is saved, so the server stores only ciphertext until you choose to reveal it.
What you geta proof, the moment you seal
no dream sealed yet
text ●●●● hidden until you choose to reveal
counts if –
nonce –
sealed –
sha-256 – (recomputable)
anchor –
bitcoin –
○ awaiting your dream
Write a dream above and seal it. Its exact words get locked to this moment; reveal only when the condition is met, or let it lapse honestly as a miss.
Before you seal, know this
- It stays private. The dream text is hidden until you choose to reveal it. Only the fingerprint is public.
- It cannot be altered. Change one character later and the fingerprint no longer matches. That is the point.
- A miss still counts. If the condition lapses, it is recorded honestly. The misses are what make the hits mean anything.
Your sealsreveal, publish to the Registry, resolve