Create a private, dated proof that your screenplay existed today.
Drop your .fountain file below. Your computer hashes it locally, and only the 32-byte fingerprint is sent to public Bitcoin-timestamping calendars. The script content never leaves your browser.
Privacy. Hashing runs entirely in this tab. A 32-byte SHA-256 of the canonical bytes is the only data that leaves your machine, and it goes only to the OpenTimestamps public calendars listed below — the same destinations the screenreg CLI uses.
Progress
1
Normalize bytes (v1-strict)
UTF-8, NFC, LF, BOM strip
2
Content hash (SHA-256)
—
3
Build committed claim
—
4
Claim hash (canonicalized)
—
5
Submit digest to OpenTimestamps calendars
—
6
Assemble .proof.ots
—
Your proof artifacts
Keep both files together — verification requires the original screenplay file plus these two artifacts. In about 1–6 hours, run screenreg upgrade proof.ots (or come back to the verify page) to fold in the Bitcoin block attestation.