Guides

Your public key identifies the signer of your events and is meant to be shared.

NIPs are Nostr Improvement Proposals that document how clients and relays can implement shared features.

Nostr is a protocol, not one app.

Your keypair is independent of one client, and signed events can be copied to other willing relays.

There is no universal retention period.

Different clients, relays, and groups can make their own choices.

There is more than one community model.

A client signs an event with your key and sends it to one or more relays.

Use a client to publish profile metadata such as a display name, description, and picture under your key.

Use your client's mute controls, choose relays with policies you trust, and be cautious with unsolicited links and payment requests.

Open the new client using a trusted signing method for the same keypair, then check its relay settings and whether it can load your profile, follows, and posts.

Keep the private key out of posts, screenshots, cloud notes, and unfamiliar websites.

Ask for a person's `npub`, a profile link, or a NIP-05 identifier they publish through a trusted channel.

Choose a trustworthy Nostr client or signer and use its account-creation flow to generate a keypair.

Treat a public media URL as public unless the host provides real access controls or you encrypt the file before upload.

Start with relays your client can reach reliably, then consider their rules, retention, cost, location, and support for the NIPs you use.

Keep a secure record of your private-key recovery material, plus your public key, chosen relays, and any client export of follows.

A Nostr follow list is itself a signed event, defined by NIP-02.

Compare the full public key with a key the person has shared through a trusted channel.

No.