How it works.
Leave a key file. Whoever finds it can prove they have it and exchange encrypted notes with you.
-
Place a key
Your copyPlaced copy Create a key and register its public part. Keep a copy; place another where you want it found.
-
Prove a find
Signed proofAPI verifies The finder submits a locally signed proof. The API checks it using the registered public key.
-
Exchange notes
You encryptFinder decrypts Anyone with a copy of the key can read and reply. Notes are encrypted before they leave the CLI.
What the server sees
The CLI never uploads your secret key. The server verifies proofs and stores notes without being able to decrypt them.
Stays with key holders
- Secret key
- Readable notes
Stored by the server
- Public key + metadata
- Signed proofs
- Encrypted notes
Metadata is public; put private context in an encrypted note.
Choose an API
Once a key is found
The finder sends a proof and an encrypted note:
kompromat report canary.json \
--message "Found in the backup"
Either key holder can read the conversation and reply:
kompromat unlock canary.json
kompromat attach canary.json \
--message "Got it. Thanks."
These commands use the API address in the key file.