Create a private, dated proof that your screenplay existed today.
Drop your screenplay below — a .pdf, .fountain, or plain text. Your computer reads and hashes it locally, and only a tiny 32-byte timestamping commitment is sent to public Bitcoin-timestamping calendars. The script content never leaves your browser.
Privacy. Hashing runs entirely in this tab. The only thing about your screenplay that ever leaves your machine is a 32-byte timestamping commitment — your script's fingerprint mixed with a fresh random value and hashed again, so the calendars never even see the fingerprint itself, just an unlinkable commitment — and it goes only to the OpenTimestamps public calendars listed below. While the proof settles, this page periodically re-asks those same calendars whether Bitcoin has confirmed it yet — the same destinations and the same commitment, nothing more. Your script, title, and author never leave (the title and author go out only as ciphertext, and only if you choose to embed them).
Progress
Your proof — one file
The .screenreg is your self-contained proof — the screenplay, the registration record, and the timestamp in one file. Keep it somewhere safe. The shareable proof is the same dated proof without your screenplay inside, so you can hand it to anyone without revealing the script. Until the Bitcoin confirmation lands (about 1–6 hours) the proof is a pending calendar attestation; finalize it below to fold in the Bitcoin block.
Prefer the individual files?
The same envelope and timestamp, unbundled.
Your proof is valid now as a pending calendar attestation. The Bitcoin confirmation usually lands within 1–6 hours — you can safely close this tab.
Closing the tab? — or just keep your files and re-drop the proof on the verify page anytime.