Write to a wallet.Only that wallet reads it.
Ciphra seals every message in your browser with a key your wallet derives. The server keeps ciphertext it has no way to open.
Scroll. This line is being sealed for real, right now, with a throwaway key made in this tab. Nothing leaves it.
Your wallet signs one fixed sentence. From that signature your browser derives a messaging key that never leaves it.
The public half goes into a directory, signed by your wallet, so anyone writing to you can check it is really yours.
Messages are sealed to that key before they are sent. What reaches the server is a box, a nonce and two public keys.
Write to a wallet that has never been here and the note waits, sealed to you, until they publish a key. Then it is sealed to them.
One row on the server
- sender
- your wallet
- recipient
- their wallet
- box
- base64 ciphertext
- nonce
- 24 random bytes
- expires
- never, 1 h, 1 d or 7 d
The real counts are on the wall below.
Wallets with sealed mail they haven't opened
Counts only. Nobody, including us, can see what the messages say. A wallet can take itself off the wall from its inbox.
Reading the wall…
Three reasons people write sealed
One key, one inbox, any wallet you can name.
Found a bug in a contract, or a leaked key in a repo? Tell the deployer wallet directly, without posting it in a public reply.
- Write to the deployer address
- Or its .sol name
- Set it to burn after a day
- They see it on next sign-in
The wallet behind a big buy is often the only contact you have. A sealed note reaches it without a DM request or a public tag.
- Paste any wallet you saw onchain
- The note waits for their key
- It shows on the wall as a count
- Share their card to nudge them
Seed phrases never belong in a chat. Everything else that should stay between two wallets can go here, and burn when read.
- Expire in 1 hour, 1 day or 7 days
- Burn it yourself after reading
- Block a wallet in one tap
- Report abuse to the moderators
Ask before you sign
Short answers here, the whole protocol in the docs.