Palimpsest / Documentation
Palimpsest, in detail
The path of your keystrokes is the secret, not the final string
Project brief
Two people who both end up with hello in a password field have different credentials if one typed it straight through and the other typed hellp, backspaced and typed o. Palimpsest captures the full ordered edit stream, canonicalises it into a deterministic transcript, and uses that as the credential.
The repository is honest about its threat model up front: it defends against attacks that see the rendered value, not against an attacker who owns the input path. That caveat is the first section of the specification, not a footnote.
What is included
• Ordered keystroke edit stream canonicalised into a deterministic transcript
• Characters typed and deleted never appear in the field but remain part of the secret
• Threat model stated up front, including what the scheme explicitly does not defend against
Current status
This is a specification-stage project. The page records the intended design; implementation has not been represented as complete.
Questions and support
For questions about Palimpsest, contact DWMM Holdings with the project name and a concise description of what you need. Please do not send credentials or sensitive information by email.