Use nihao to generate or audit a Nostr key, profile, relay list, and optional wallet.
SMTP to NIP-17 Bridge
SMTP bridge
Your npub. Your agent. No email? fips.email gives every Nostr agent a private, disposable NIP-17 inbox for GitHub, Slack, and the rest of the legacy web. FOR FREE.
Upgrade to a paid alias for your npub, or even host your own SMTP server over FIPS. fips.email bridges the old legacy email protocol to encrypted transport over FIPS.
open demo mode
npub1...@fips.email
Email in. NIP17 out. Then ask the bridge for Inbox, Alias, List, Show, or Delete by NIP17.
hosted docker
coming modules
inbox commands
Agent instructions
Bootstrap an identity. Then give it an inbox.
If you are an autonomous agent or bot, start with a Nostr identity, publish DM relays, then use your npub as a free email address at npub@fips.email. Legacy services can send normal email; fips.email forwards it as a private NIP17 message.
The machine-readable guide is available as Markdown at /agent.md.
Configure an NIP17-capable client or OpenClaw channel and publish kind 10050 DM relays.
Use your npub at fips.email for signups, alerts, OTPs, and agent-readable legacy mail.
Current live demo
Email should arrive where your key lives.
Send a normal email to your-npub@fips.email. The SMTP receiver accepts the message on port 25, validates the recipient npub, stores the raw email, wraps the payload as NIP17, and publishes it to the recipient's DM inbox relays.
Paid aliases route the same way: alias@fips.email resolves to the owner npub, then lands as a private NIP17 message. Every npub has the free default address and can add multiple paid aliases.
smtp
port 25
bridge
fips.email
wrap
NIP17
relays
kind 10050
fipsmail trace
$ sendmail npub1...@fips.email
smtp: accepted on port 25
recipient: valid bech32 npub
storage: .eml + routing metadata
wrap: kind 14 inside NIP17 gift wrap
publish: default relays + kind 10050 inbox
bot: Inbox, Alias, New alias, Pay aliasNIP17 mailbox bot
Talk to the bridge like a tiny private inbox.
bridge npub
npub1ema7l5fsneqskdk0nne9rd8qdts9q573xem8jrsamhnpvges7ursdmvlk4
Send this npub a private NIP17 message from your own key. The reply comes back as NIP17 to your configured inbox relays.
Show recent messages addressed to your npub.
Alias for Inbox when your client muscle memory wins.
Read a message preview and mark it as read.
Move a message into mailbox trash status.
List your free npub address plus active paid aliases.
Check availability and show the alias price.
Create a Lightning invoice and activate the alias immediately in demo mode.
1 char 210000 sats, 2 chars 21000, 3 chars 2100, 4 chars 210, 5+ chars 21.
Security posture
Open demo now. Hardened service next.
Open public bridge
Anyone can send email to a valid npub@fips.email address or active alias@fips.email address. Anyone can use the NIP17 mailbox commands. Data access is still scoped by npub, so one user cannot list or delete another npub's mailbox or control another npub's alias.
Activated inboxes
A production inbox should activate by NIP17 first. After activation, SMTP accepts mail only for registered npubs with limits, reputation checks, and abuse controls.
Require a one-time NIP17 Activate command before an npub can receive SMTP mail.
Limit SMTP sessions, mailbox commands, relay publishes, bytes per message, and messages per npub.
Use SPF, DKIM, DMARC, greylisting, blocklists, and sender history before wrapping mail.
Use Lightning stamps or monthly plans so high-volume inboxes carry their own cost.
Architecture
Same apps. Different ground.
SMTP bridge
Expose a local SMTP endpoint. Mail clients submit normally, the bridge packages messages for FIPS transport.
Keyed identity
Map accounts to cryptographic identities instead of trusting DNS and static server addresses.
Mesh routing
Let the network find a path across whatever links are available, then heal around broken routes.
Legacy edge
Deliver back into ordinary mailboxes where needed, without forcing every recipient to upgrade on day one.
Business model
One hosted FIPS box. Add what you need.
Base idea
Your personal FIPS Docker
Each customer gets a hosted container with FIPS network access. More services mean more CPU, RAM, storage, routing, and operational care. Same box, cleaner billing.
npub@fips.email
legacy email in
alias@fips.email
paid alias in
mail@yournpub.fips
FIPS inbox out
Activated inbox, SMTP bridge, NIP17 mailbox bot, and abuse controls.
Unique paid alias@fips.email addresses mapped to your npub.
Private traffic routes over the FIPS mesh.
Hosted bot endpoint reachable inside FIPS.
Lightning service module for the same instance.
Shell access to your hosted FIPS container.
Higher limits, custom allowlists, and priority relay delivery.
Next targets
Fuck IPs, not applications.
Email
SMTP submission and mailbox delivery over FIPS.
Messaging
Human chat routed by keys, not platform silos.
VPN
Private routes for ordinary traffic without trusting the tunnel provider.