Nostr4 growth and infrastructure 4 social apps
Get in touch

Contact Us

Phone

We are still setting up a phone contact method. Please message us directly for best results.

Email

Click to send an email message to our company inbox.

hello@nostr4.social

Nostr

Click to copy our pubkey into any Nostr client.

npub1n0str479lul4smnvquvy33f8ljxkw073fmd0x7tspvkpssjmyggqjdv79a

Send an encrypted message

This private message will be encrypted and sent over Nostr. It is sealed in your browser, carried by public relays, and opened only by the recipient who holds the private key. No account is required, and no server holds a copy with any traceable information.

How it travels
  1. Your browser

    Seals the message with NIP-44. A one-time key also stamps the wrapper with proof of work, so a flood costs something and a visitor does not.

  2. Relays

    Carry a wrapped event they cannot open, addressed to the recipient you chose.

  3. Nostr4

    The recipient opens it with their own key, and replies the same way.

Sign with a one-time key, generated in this browser and discarded after use.

How this works No server · NIP-17 over NIP-44 · what relays see · what we keep

There is no server.

This page is static files. Your message is encrypted in this tab and published straight to relays. Nothing we run ever holds a plaintext copy, because there is nothing to hold it.

The encryption is NIP-44, and it happens here.

Your message becomes an unsigned kind 14 rumor, sealed to the recipient as a kind 13, then wrapped in a kind 1059 under a key that exists only for that one event. Only the recipient can unwrap it.

Why sending takes a few seconds.

A message signed with a one-time key carries a NIP-13 proof of work: your browser repeats a hash until the wrapper’s id begins with enough zero bits. That costs a visitor a few seconds, once. It costs a flood the same for every message, which is what lets an inbox relay refuse the cheap ones. A message signed with your own key skips it.

Who can read it.

The recipient you chose, and nobody else. Every name offered is listed in this domain’s NIP-05 file. If you are signed in, you get a copy too, so the conversation appears in your own client.

What the relays see.

An encrypted blob, the recipient it is addressed to, and your IP address, the same as any other connection you make. They cannot see who sent it, what it says, or when it was written.

What we keep.

Nothing this page can give us. No analytics, no logs, no third-party requests. The only network traffic this page makes is to nostr4.social and to the relays named on screen.

What this does not do.

There is no forward secrecy in NIP-44: a key that leaks later can decrypt messages sent earlier. Relay operators can see metadata about the wrapper. If that matters for what you are about to say, say less here and more on a call.

Scan this with your signer, or open it directly. The page asks for two permissions only: seal one message and sign it.

Or paste a bunker URI

A name@domain identifier is not accepted here, because resolving it would mean this page making a request to someone else's server.

Waiting for your signer...