Typestamp creates verifiable proofs of effort by recording every keystroke made during a writing session with precise timestamps.
We call these proofs of writing effort 'typestamps'.
A typestamp tracks every key typed in a writing session with a precise timestamp. Once you save your session, it is validated. If accepted, the full keystroke audit is compressed, encrypted, and stored. You get a link so anyone can inspect the typestamp of your session.
A typestamp doesn't guarantee human authorship, but it does guarantee that someone made the effort to produce the written content of the proof.
A session is the process of producing a typestamp. Sessions are based on events. Each session records a timeline of events: when it started, every key pressed, content pasted, any pauses and resumes, and when it finished. This makes the audit trail transparent and a verifier can see not just what was typed, but the exact rhythm and flow of the writing, as well as the content length over time.
Sessions can be rejected if the system detects low human effort. The system is work in progress and may be too strict, so we accept feedback.
A reference scopes a typestamp to a specific purpose. An institution creates a reference with a label - for example, Software Engineer Cover Letter Uber Q2 2026 - and shares the resulting link with writers. Any typestamp created through that link is permanently tied to that reference, which prevents the typestamp from being reused in a different context.
Data in typestamps is encrypted with AES-256-GCM. The encryption key is derived from the typestamp ID and a server secret - neither is stored alone. Typestamps expire after 72 hours and are deleted automatically.