Guides

An onion service hides the server's network location and encrypts the Tor-to-service connection without an exit relay.

Clients choose which NIPs to implement and how to present them.

Your client may be reading different relays from the ones that accepted your post, a relay may have rejected or deleted it, or the client may not display that event kind.

Often the post contains a URL to media stored on a separate file host rather than embedding the file inside every relay event.

Write relays are where you generally publish your events.

Older Nostr direct messages commonly used the legacy NIP-04 approach.

NIP-46 lets a client communicate with a separate signer, sometimes called a bunker, to request signatures.

Nostr is an open protocol for publishing signed messages through independently operated relays.

NIP-07 describes a `window.nostr` interface that a browser extension or similar signer can expose to Nostr web apps.

A zap is a Lightning payment with Nostr events that let clients show the payment in context.

A signer is software or a device that approves and creates cryptographic signatures for your Nostr events.

A relay is a server that receives events from clients and answers event queries.

An event is the basic Nostr data object.

A NIP-05 identifier resembles an email address, such as `name@example.com`, but it is a web-domain lookup that maps a name to a Nostr public key.

Muting usually changes what your client shows you; it does not revoke another person's public key or prevent all relays from storing their events.

If you lose the private key and every backup or signer that holds it, you cannot sign new events as that public key.

Keep its server and relay software updated, restrict administration, monitor storage and abuse, and publish clear access rules.

`npub` is a human-readable encoding of a Nostr public key, suitable for sharing.

A relay can see that a client connected, which events it submitted or requested, and some timing and routing information.

A relay receives the signed events you publish to it, the filters you request, and the connection that carries those requests.