Nostr Mail

Remove gatekeepers from email. Use Nostr as transport instead of SMTP between users.


What is Nostr Mail?

Nostr Mail carries ordinary RFC 2822 email over Nostr. Your address is derived from your keys, your messages are gift wrapped end to end, and no provider stands between you and the person you write to. When the other side is not on Nostr, a bridge speaks SMTP on your behalf.


Architecture Overview

                    NOSTR NATIVE
┌──────────┐                              ┌──────────┐
│  Alice   │ ────── Nostr Relays ──────►  │   Bob    │
│ (Client) │      Kind 1301 + NIP-59      │ (Client) │
└──────────┘                              └──────────┘

                    WITH LEGACY EMAIL
┌──────────┐      ┌────────┐      ┌──────────┐
│  Gmail   │ ───► │ Bridge │ ───► │   Bob    │
│   User   │ SMTP │        │Nostr │ (Client) │
└──────────┘      └────────┘      └──────────┘

Components

Protocol
Bridge
SDK
Client

The email-over-Nostr specification using Kind 1301 events. Learn more

Bidirectional bridge between legacy email (SMTP) and Nostr. Learn more

Dart and JavaScript libraries for building Nostr Mail applications. Learn more

Nmail, the reference client for Android, Linux and the web. Learn more


Try it

Open Nmail nostrmail.org



NIPs Used

NIP Description Usage
NIP-01 Basic protocol Event structure
NIP-05 User discovery user@domain resolution
NIP-09 Event deletion Deleting emails and labels
NIP-17 Private DM relays Kind 10050 DM relays
NIP-32 Labeling Folders, read state, stars
NIP-44 Encryption Sealing and settings
NIP-59 Gift-wrapped events End-to-end encryption
NIP-65 Relay list metadata Relay discovery
NIP-78 Application data Settings sync

License

This project is licensed under the MIT License.