A Nostr account is not the same as the accounts you use on other platforms. There is no sign-up button and no "forgot password" option. Your identity is simply a key pair: the public key (npub) works like your username, and the private key (nsec) is the only thing that controls that identity. Anyone who gets your nsec can post, like, and send direct messages as you, with no extra verification needed. So the first step in using Nostr is to understand where this key pair is stored and how to use it.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
Understand the account first: keys are not passwords
A Nostr client is just an interface. It does not hold your account. If you log in with the same nsec on Damus, Primal, or Amethyst, you will see the same identity, the same follows, and the same posts. That is why Nostr is called a censorship-resistant social protocol: your identity is not tied to any company's database.
The trade-off is also very direct. If you lose your private key, your account is gone forever. There is no customer support to recover it. If your private key leaks, someone else can take over your identity immediately, and your only option is to start over with a new key. Academic research confirms this as well: Nostr identity management is fully decentralized, and lost keys cannot be recovered.
Two ways to create an account
Option 1: Create directly inside a client. Open a Nostr client and choose to create a new account. The client will generate a key pair. You will see an npub (starting with npub1) and an nsec (starting with nsec1). You can share your npub publicly, but your nsec must be stored offline.
Option 2: Generate with a signer first, then connect to a client. A signer is a tool designed specifically to hold private keys. Browser extensions like Alby, nos2x, and Sidecar, mobile apps like Amber, and web tools like nsec.app all fall into this category. You first create or import a key in the signer, then choose "log in with extension" or "connect signer" in each client. The client never touches your nsec.
For beginners, I suggest starting with Option 1 so you can quickly confirm that you can post and see content normally, and only then consider moving to a signer. The downside of Option 1 is that you need to paste your nsec into the client, and if that client is not trustworthy, your key could be stolen. So choosing a reliable client matters even more than how you store your key. Use a client you have actually researched, ideally one with public code or a long maintenance history.
If you start with a signer, the benefit is that you do not need to paste your nsec again when switching clients, and you can limit what each client is allowed to do. But an extra tool also means extra learning. If you cannot even understand the signing request pop-up, you may be more likely to make a mistake.
Storing your private key: more serious than you think
After creating an account, the client will usually ask you to save your nsec. Do not skip this step, and do not just take a screenshot and leave it in your phone's photo gallery.
Good storage methods include at least: writing it on paper and keeping it in a physically secure place; storing it encrypted in a password manager; using an encrypted backup feature provided by a client or signer (such as ncryptsec in NIP-49 format).
Do not put your nsec in cloud notes, chat bookmarks, or email drafts. Anywhere you can access over the internet can also be accessed by an attacker.
Choosing a client: first decide whether you will use a phone or a computer
There are many Nostr clients, but your selection logic can be simple: first decide which device is your main one, then see which clients on that device are still actively maintained.
Mobile
iPhone users commonly use Damus, while Android users commonly use Amethyst. Both have been around for a long time and have large user bases. If you already use a client on your phone, first check whether it can log in normally with your npub before deciding whether to switch.
Web
Primal and Snort are common web-based choices. The advantage of web clients is that you do not need to install anything; you can just open them in a desktop browser. The risk is that you need to enter or connect your key in the browser. If the website is fake, your key is gone. So only enter through official links you have verified.
Signer approach
If you plan to switch between multiple devices and clients, a signer is almost the only painless way. Amber handles signing on Android, Alby and nos2x handle the browser, and nsec.app provides remote signing through NIP-46. The way they work is: the client requests a signature, the signer shows you what is being signed, and only after you approve does the operation complete. The client never knows your nsec.
The trade-off is that Amber is relatively mature on Android, but iOS does not have an external signer option of the same level. If you use an iPhone, signer choices are more limited, and the practical path is usually the client's built-in key storage.
What syncs between clients and what does not
When you log in to different clients with the same nsec, your profile, follow list, posts, likes, direct messages, and Zap records will sync. But app settings, notification preferences, drafts, wallet connections, and offline caches will not sync. That means when you switch clients, you will need to reconnect your wallet, and your drafts will not carry over.
If you find that your follow list is empty in a client, do not rush to re-follow everyone. Wait a minute or two, or refresh manually. Relay sync takes time. If it is still empty after refreshing, check whether both clients are connected to the same relays.
Bitcoin Zaps: set up a Lightning address first
Bitcoin tipping on Nostr is called Zap. It is sent over the Lightning Network and priced in satoshis (sats). The process works like this: you click the Zap button on a post, choose an amount, your wallet pays over Lightning, the creator receives the sats instantly, and the Zap record appears on the post.
To receive Zaps, set up a Lightning address first
A Lightning address looks like an email address: yourname@walletdomain. For example,
In your Nostr client's profile settings, find the "Lightning address" or "LN Address" field, paste your address in, and save. Once saved, other people will see a Zap button on your posts.
Common sources for Lightning addresses include: Wallet of Satoshi (custodial and simplest, format
To send Zaps, your wallet must be connected first
There are three ways to send a Zap.
Client-connected wallet. Some clients support connecting wallets like Alby or Zeus. Once connected, you can click the Zap button and send directly.
Manual payment with an external wallet. After you click the Zap button, the client generates a Lightning invoice. You copy that invoice into your Lightning wallet and pay it.
Built-in client wallet. Clients like Primal have a built-in wallet. Once you top it up, you can Zap directly without an external wallet.
If you do not have any Bitcoin yet, you need to already have sats before you can send a Zap. You can buy Bitcoin on an exchange and withdraw it to a Lightning wallet, or buy directly inside a Lightning wallet that supports purchases. Nostr itself does not provide a way to buy Bitcoin.
Zap visibility
Public Zaps show the amount and sender on the post. Some clients support private Zaps, where the amount is hidden and the sender is anonymous, but the creator still receives the money.
Common issues
Nothing happens after scanning or pasting your nsec. Check that you pasted a private key starting with nsec1, not a public key starting with npub1. The two cannot be used interchangeably.
The Zap button does not appear, or it shows an error when clicked. The most common reason is that the recipient has not set a Lightning address in their profile, or the address was not saved successfully. Ask the person to check the "Lightning address" field in their client settings. Another possible reason is that your wallet is not connected or does not have enough balance.
Your follow list does not match across clients. Different clients may be connected to different relays. A relay is a Nostr server that stores and forwards posts. If your follow list only exists on one relay and another client is not connected to that relay, that client cannot see it. In your client's relay settings, make sure you are connected to at least two public relays (for example, wss://relay.damus.io and wss://nos.lol), then refresh again.
You posted something, but others cannot see it. The relay you are connected to may be unstable. Research shows that about 20% of relays are offline more than 40% of the time they are measured. If you notice that a relay is often unresponsive, replace it in your settings. Nostr is designed so that you can post to multiple relays, so one going down does not affect the others.
You want to switch clients but do not want to set everything up again. Just log in with the same nsec. If you use a signer, choose "connect signer" in the new client instead of "enter private key".
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
References
- Nostr User Guide·Using Multiple Clients, no update date listed; checked on 2026-10-07.
- arXiv·Seeing the Politics of Decentralized Social Media Protocols, no update date listed; checked on 2026-10-07.
- GitHub·blup: Your first steps on Nostr, published or updated on 2026-02-06; checked on 2026-10-07.
- Chrome Web Store·Sidecar | A Classy Nostr Signer, no update date listed; checked on 2026-10-07.
- GitHub·nostr-mill, published or updated on 2026-09-15; checked on 2026-10-07.
- Nostr Developer Guide·Mobile Development, no update date listed; checked on 2026-10-07.
- Nostr User Guide·Zaps & Lightning, no update date listed; checked on 2026-10-07.
- Nostr Developer Guide·Lightning Zaps, no update date listed; checked on 2026-10-07.
- GitHub·noauth: Nostr key manager, published or updated on 2025-05-25; checked on 2026-10-07.
- arXiv·Exploring the Nostr Ecosystem: A Study of Decentralization and Resilience, no update date listed; checked on 2026-10-07.
- ACM Digital Library·An Empirical Analysis of the Nostr Social Network, published or updated on 2025-11-24; checked on 2026-10-07.
