Introduction
bMail is end-to-end encrypted mail that lives on BNB Chain. Your wallet is the address, gas is the only cost, and no server ever holds anything readable.
Conventional mail is a tenancy. A provider holds your messages, controls the namespace your address lives in, and can read, scan, suspend, or delete on terms you do not set. bMail replaces the tenancy with ownership: a name minted to your wallet in a registry contract, and messages that are sealed in your browser before they ever exist anywhere else.
The contracts are deployed and the app is open. No independent audit has been completed yet, so treat the amounts you put through it accordingly. Security sets out what protects your mail and what does not.
The three properties that matter
You own the address
A name is minted to your wallet in MailRegistry. There is no
renewal, no rent, and no operator who can reassign it.
Gas is the only cost
Message bodies ride in event logs rather than contract storage. Names of five characters and up cost nothing beyond the transaction.
The chain carries ciphertext
Sealing happens in your browser against the recipient's published key. The chain proves delivery; it never learns the contents.
What the system is made of
What is genuinely private, and what is not
Being precise about this matters more than sounding secure. The message contents are protected by end-to-end encryption. The metadata is not, because a public ledger is public.
| Visible on chain | Never on chain |
|---|---|
| Sender and recipient wallet addresses | Subject line |
| Timestamp and block number | Message body |
| Envelope size, rounded to 256-byte blocks | Attachment contents |
| Whether a stamp was escrowed, and its value | Your mailbox private key |
| That a message replies to another message | Anything that identifies a contact by name |
Anyone can see that address A mailed address B at a given time. This is inherent to writing to a public chain and is not something encryption fixes. Stealth addressing and sealed sender are on the roadmap to address it; they are not in v1.
Where to go next
How it works
The full life of a message, from typing it to reading it, with the contract calls and cryptography at each step.
Encryption
Key derivation, the envelope, the threat model, and what an attacker who holds the entire chain history can and cannot do.
Contract reference
Every external function, event, error and constant across both contracts.
Roadmap
What is built, what is next, and the open decisions that gate a mainnet launch.