# Background & Problem Definition

#### Email's Legacy

Email remains the **most universal communication protocol** in the world, but its foundations are outdated and fragile:

* **Centralized Hosting** → Mailboxes are controlled by corporations like Google or Microsoft, creating choke points for censorship, surveillance, and lock-in.
* **Surveillance by Default** → Metadata and even message content are harvested for profiling, ads, and government requests.
* **Weak Authentication** → Legacy standards like SPF, DKIM, and DMARC are optional and inconsistent, leaving users vulnerable to impersonation and spoofing.
* **Spam & Phishing Epidemic** → Billions of spam emails cost the world billions in fraud, scams, and lost productivity.

👉 Despite being universal, **email is neither private, nor secure, nor owned by its users**.

#### Identity Fragmentation in Web3

Web3 today suffers from **disconnected identity silos**:

* **Wallets** → hold assets and sign transactions, but cannot natively communicate.
* **Domains** (e.g., `.sol`, ENS, `.com`) → provide names, but lack universal communication or trust guarantees.
* **Email** → remains separate from both, forcing users to juggle multiple accounts, identifiers, and credentials.

This creates **friction and value leakage**:

* A DAO might use Discord, a domain, and multiple wallets to coordinate.
* An enterprise juggles Google Workspace for communication, plus a wallet for treasury, plus custom tools for contracts.
* An individual may have multiple wallet addresses, a `.sol` name, and several emails — but no unified identity.

👉 There is **no standard, verifiable identity + communication system** that bridges Web3 and the familiar email metaphor.

#### Missing Primitives in Legacy Systems

Legacy email and identity systems are fundamentally **incapable of serving Web3’s needs**. They lack:

* **On-Chain Provenance** → No cryptographic proof of who actually sent a message. Reputation is off-chain and easily faked.
* **Programmable Settlement** → Payments, contracts, and invoices are disconnected from communication, forcing users into risky off-platform links.
* **Immutable Audit Trails** → No tamper-proof history of communication or agreements.
* **Sovereignty** → Identities are rented from providers, not owned by users.

👉 Web3 requires **communication as a native primitive**, secured by private keys and enforced on-chain.

#### Requirements for Web3 Communication

For communication and identity to be **native to Web3**, SolMail establishes four non-negotiable requirements:

1. **Cryptographic Identity** → Usernames, inboxes, and domains must be secured by private keys, not rented accounts.
2. **End-to-End Encryption (E2EE) by Default** → Messages and attachments are encrypted client-side; only sender and receiver can access them.
3. **Composability** → Communication must seamlessly integrate with DeFi, NFTs, DAOs, payments, and decentralized storage.
4. **Final Settlement** → Messages, invoices, and agreements must **settle on-chain**, with the same security guarantees as asset transfers.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.solmail.so/background-and-problem-definition.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.