Encrypted messages, recorded on the blockchain.
Send a message, file, and payment together. Wallet to wallet, stored on-chain, no account required.
Three-way comparison
How DEEP Mail measures up against everyday email and mainstream encrypted chat.
| Gmail / Outlook | Signal / WhatsApp | DEEP Mail | |
|---|---|---|---|
| Payment and message in one on-chain transaction | No | No | Yes |
| No phone number or account required | No | No | Yes |
| No delete function for sent messages | No | No | Yes |
| Tamper-evident on-chain record | No | No | Yes |
| Only you and your recipient can read it | No | Yes | Yes |
Where it matters
From private conversations to privileged and professional communications.
Personal:
Send private messages, files, and payments wallet-to-wallet. No company holds your keys and no account is required.
Legal:
Send privileged communications with a cryptographic timestamp and a permanent record that no third party can alter or decrypt.
Business:
Send supplier orders, invoices, and payments with end-to-end encryption and a permanent integrity record, with no company holding the keys.
How it works
Connect a wallet, send, and let the blockchain hold the record.
- Your wallet connects in place of a username and password. Your encryption key registers on-chain for a 0.001 ETH fee.
- Send a message to any wallet address with a file or payment attached in the same transaction. No email address, phone number, or account name required.
- Only you and the people you send it to can decrypt the message, each with their own private key. USSE does not hold the keys.
- The message and timestamp are recorded on the blockchain, and no function in the contract edits or deletes them.
- The fee is $0.03 minimum per message, paid in ETH, plus 0.33% of any attached payment. No subscription. The recipient pays nothing per message.
End-to-end encryption, verified on-chain
No accounts, no key servers, your wallet holds the keys, the blockchain holds the proof.
Keys born from your wallet
One wallet signature deterministically derives your personal encryption keypair, right in your browser. The private key is never uploaded, never stored, and never leaves your device, there is no password to steal and no account to breach.
Registered Public Key
Your public key is registered on-chain in the USSE Public Key Registry, cryptographically bound to your wallet address. Senders fetch it directly from the blockchain, with no key servers and no directories.
Sealed end-to-end
Every message is sealed with a fresh one-time key: an ephemeral ECDH handshake with the recipient's registered key derives an AES-256-GCM cipher. Encryption happens in your browser before anything touches the network, only the recipient's wallet-derived key can open it. Not even USSE can read it.
Zero-knowledge proof gate
Every send carries a Groth16 zero-knowledge proof bound to the message's on-chain hash commitment, sender, and recipient. The smart contract verifies the proof before the message is accepted.
Built for what comes next: a hybrid post-quantum encryption layer (X25519 + ML-KEM-768, FIPS-203) is built and not switched on yet.