How to choose a Nostr username that actually works

Your Nostr username is more than a login handle. It is the thing people paste into search bars, write on business cards, tag in posts, and remember when they want to find you again three months later. Picking one poorly costs you discoverability for years.

This guide is how to pick one that works. Not the philosophy of self-branding, just practical constraints and a short decision process.

TL;DR. Pick a name that is 4 to 12 characters, all lowercase, only Latin letters and digits, and consistent with the handle you use on other networks. If it is already taken on nostr.blog, either pick a nearby variation or host your own NIP-05 on a personal domain.

When you are ready, grab your @nostr.blog address →

Two usernames, two jobs

Nostr has a split that confuses new users at first.

Display name is what appears at the top of your posts in big letters. Anything Unicode goes. Duplicates allowed. You can be Alice 🌻 or сергей or Jane Smith and update it anytime. This is the human name.

NIP-05 username is the local part of your verified identifier. Structured like an email address: alice@nostr.blog. This is unique within the domain. The characters are restricted to what email-like systems handle cleanly: lowercase a-z, digits 0-9, hyphen, underscore, period. No emoji, no spaces, no non-Latin scripts.

Clients show both. The display name is prominent. The NIP-05 is smaller, often next to a checkmark, often in a secondary color. The split means you can have an expressive display name and a clean, searchable identifier.

This article is about picking the NIP-05 username. The display name is whatever you want it to be, and you can change it anytime without consequences.

What makes a good username

Four hard constraints, in order of importance.

Constraint 1: You can say it out loud

A username you cannot pronounce cleanly fails at conversations. "Find me at three-dash-underscore-xl-ninety-nine at dot com" is not memorable. "Find me at alice at nostr dot blog" is.

Test it: say the full identifier out loud three times. If you stumble, pick a different one.

Constraint 2: It does not collide with your other identities

If you are @alice on Twitter, alice on GitHub, and alice.mastodon.social, you want alice@nostr.blog. Cross-platform consistency is how people find you without asking.

If your preferred handle is taken, use the same fallback you use on other networks. If on Twitter you are @alice99, alice99@nostr.blog is correct; alice@nostr.blog is wrong because it is not actually you.

Constraint 3: It is short enough to type

Long usernames work on paper but fail in chat. thealicemcdowell-productphotographer@nostr.blog is correct but nobody is typing that from memory. A working heuristic: shorter than ten characters is friction-free; ten to fifteen is fine; over twenty and you will regret it.

Constraint 4: It does not decode to something embarrassing

A classic trap: carrots@nostr.blog reads fine for someone who named it after a vegetable, but what reads fine to you may read badly split differently. Read the identifier out of context. If the letter grouping is ambiguous, pick different letters.

What names are available and what they cost

On nostr.blog, pricing by length. Shorter names are scarcer and priced higher.

Most users pick between five characters (alice) and eight characters (alicej99). Both tiers are priced in the range of "cheaper than lunch."

Premium single-letter and two-letter names are reserved for people who want a genuinely memorable handle and are willing to pay what scarce things cost. a@nostr.blog or bd@nostr.blog are the kinds of identifiers that do not need further explanation.

The decision process, concretely

Five minutes, in order:

1. Write down the handle you use on Twitter, Instagram, GitHub, and email.
2. If they are all the same, try that handle on nostr.blog.
3. If it is available at a price you like, take it.
4. If it is taken at a price you do not want to pay, try nearby variations: add a short suffix, add your real surname, add your year of birth.
5. If nothing you like is free on the domain, either settle for a slightly different handle on nostr.blog (the convenience wins) or register a personal domain (yourname.com) and run NIP-05 yourself with whichever local part you prefer.

The decision tree rarely takes more than a minute once you list the options.

Unicode, emoji, and other special cases

The NIP-05 spec restricts the local part of the identifier to a-z 0-9 - _ . with optional uppercase (though most implementations lowercase it). This means:

• Emoji do not work. 🌻@nostr.blog is not a valid NIP-05 even if the client lets you type it.
• Cyrillic, Chinese, Arabic do not work in the local part. The spec predates universal Unicode handling and changing it would break every existing verifier.
• Hyphens and underscores work. alice-mcdowell@nostr.blog is fine. alice_mcdowell@nostr.blog is fine.
• Dots work but are rare. j.smith@nostr.blog works; some clients handle the dot weirdly in search.

If your identity is tied to a non-Latin name, the standard workaround is: put the real-name rendition in the display name (which is Unicode-friendly), use a transliterated or adjacent version in the NIP-05 local part. Your display name can be сергей and your identifier sergei@nostr.blog; both work together.

What happens to the username over time

The username is stable as long as you renew the registration on nostr.blog (or keep the JSON file on your own domain). If you stop renewing, the name eventually returns to the pool.

Your underlying identity, the public key, is not tied to the username. If you move from alice@nostr.blog to alice@alicesdomain.com, your followers, your posts, and your reputation all carry over. The NIP-05 identifier is a pointer to the key, not the account itself.

This gives you flexibility. You can start cheap (a longer name on nostr.blog for $2.99), try Nostr for a year, upgrade to a shorter name later if you want to pay more, or move to your own domain entirely when you are ready. None of these transitions cost you your audience.

Avoid these mistakes

Four specific traps that look fine at signup and hurt later.

Picking a username that only makes sense to you right now. "wordsmith2022" was fine in 2022. In 2026 it is stale. Pick something timeless.

Using your work title or role in the name. "alice-designer@nostr.blog" locks you into a specific professional identity. If your career shifts, the name dates. Keep roles in the bio, not the handle.

Claiming a name that is someone else's. If "alice@nostr.blog" is taken and the person using it is a working writer named Alice, taking "alice-real@nostr.blog" to imply you are the "real" one is a bad look. Pick something that is clearly you.

Hoarding short names across domains. Grabbing a and aa on every domain you can find, hoping to flip them later, is neither profitable nor a good use of anyone's time. The single-letter premium tier exists because genuinely memorable short names are scarce; hoarding adds noise without adding value.

What matters more than the username

The username gets you found. After that, the content and interactions determine whether anyone cares. A brilliant x9z47@nostr.blog eventually gets remembered because the writing is memorable; a forgettable johnsmith@nostr.blog fades because the writing is not.

Pick a name that is serviceable, then spend your energy on what you actually post. The username is five minutes of work at the start; the rest is years.