The Ostrich, the Purple One, and the Key to Your Own Name
In 1993, Prince drew a symbol on his face in eyeliner, told the world his name was now an unpronounceable glyph, and spent the next seven years as “The Artist Formerly Known As Prince” — all because Warner Bros. owned his name.
Not his music. Not his image. His name.
He wrote “SLAVE” on his cheek during live performances. He released albums under the symbol because his legal name belonged to a corporation. The most gifted musician of his generation couldn’t call himself what his mother called him, because a contract said otherwise.
It was the most purple act of rebellion in the history of intellectual property. And twenty years before anyone had heard of a blockchain or a relay, Prince understood something fundamental: if someone else controls your identity, you don’t really have one.
Enter the Ostrich
If you spend any time in the Nostr community, you’ll notice the ostriches.
Purple ostriches, specifically. On profile pictures. In memes. As the unofficial mascot of a protocol that most people outside of it haven’t heard of yet. The origin is exactly as internet as you’d expect — someone noticed that “Nostr” kind of sounds like a portmanteau involving an ostrich, the community thought it was funny, and now there are purple ostriches everywhere. (Protocol governance at its finest.)
But here’s the thing about ostriches: the one fact everyone knows about them is wrong.
Ostriches don’t bury their heads in the sand. That’s a myth — Pliny the Elder started it in the first century, and we’ve been repeating it for two thousand years. What ostriches actually do is lower their heads to the ground to check on their eggs. They’re not hiding from danger. They’re protecting the next generation.
Which, if you squint hard enough — and on the internet, someone is always squinting hard enough — is a decent metaphor for what Nostr is trying to do.
The Protocol That Gives You Your Name Back
Nostr stands for “Notes and Other Stuff Transmitted by Relays,” which is both an accurate technical description and the most aggressively unsexy name a protocol has ever been given. (The naming committee was clearly focused elsewhere.)
Here’s what it actually does: instead of a company giving you an account — and retaining the right to suspend, delete, or lock it whenever their terms of service change or their content moderation team has a bad day — you generate a cryptographic keypair. Two keys. One public, one private. The public key is your address. The private key is your proof of identity.
No company issues it. No company can revoke it. Your posts are signed with your private key and broadcast through relays, which are just simple servers that pass messages along. If one relay goes down or kicks you off, your posts are on a dozen others. Your identity is yours because you hold the math, and math doesn’t have a trust and safety team.
Prince would have loved this. (He’d also have found a way to make the keypair unpronounceable, but that’s a separate engineering challenge.)
What We Built
Our Nostr Keypair Generator creates a fresh keypair in your browser using the same elliptic curve cryptography (secp256k1) that secures Bitcoin. Nothing is sent to a server. Nothing is stored. You generate the keys, you back them up, you own them.
What you get:
- nsec (bech32 private key) — your master password, masked by default, with a warning icon on the reveal button because we take this seriously
- npub (bech32 public key) — your address, shareable, QR-code-ready
- Hex equivalents of both — for developers who work at the protocol level
- Format converter — paste any Nostr key format, get all the others. Auto-detects nsec, npub, or raw hex
What you don’t get:
- A QR code for your private key. We won’t generate one. A photograph of a QR code is all it takes to steal someone’s identity, and we’re not building that footgun. (The ostrich would not approve.)
- A signup form. Or a login. Or an email prompt. Or a cookie banner. Or a reason to trust us with anything beyond rendering some math in your browser tab.
The Purple Thread
The Nostr community picked purple as its color the way the internet picks anything — through the accumulated weight of a thousand individual choices that nobody explicitly coordinated. The early clients used it. The relay maps use it. The ostriches are wearing it. It just… happened.
But purple has always been the color of sovereignty. Roman emperors wore Tyrian purple because the dye was worth more than gold. Byzantine law restricted it to the imperial family. Prince chose it because — well, Prince chose it because he was Prince, and if anyone was going to claim a color as an extension of their identity, it was going to be a five-foot-two genius from Minneapolis.
In Nostr, purple represents something similar. Not royalty, but self-sovereignty. The idea that your digital identity shouldn’t be rented from a corporation any more than your name should be owned by a record label. Your keys are yours. Your posts are signed by you. Your identity is as portable as the 63-character string that starts with npub1.
The Practical Part
If you’ve never heard of Nostr, our tool includes a Getting Started guide with everything you need to go from “I have keys” to “I’m posting on a decentralized network” in about ten minutes:
- Back up your nsec. This is the non-negotiable step. There’s no “forgot password” flow. There’s no customer support. Write it down, put it in a password manager, do both.
- Install a signing extension — Alby or nos2x — so you never paste your private key into a website again.
- Pick a client. We list six: Damus (iOS), Amethyst (Android), Primal, Iris, Snort, Coracle (all web). They all talk to the same network. Switching between them doesn’t reset your followers, because your followers follow your key, not your account.
- Connect to relays. We list five popular ones to start with, plus a link to nostr.watch for the live directory.
And if you’re already deep in the Nostr ecosystem — running your own relay, debating NIP proposals on GitHub, strong opinions about relay economics — the format converter is what you came for. Paste an npub, get the hex. Paste a hex private key, get the nsec plus the derived public key. It auto-detects everything and validates checksums before converting.
The Garden Connection
We also built NostrGardn, a Nostr-native photo community for the people who actually use this protocol every day. The keypair generator links to it because the two tools serve the same ecosystem — one gives you your identity, the other gives you somewhere to use it.
It’s a small corner of the internet where your photos are signed by your keys and your identity doesn’t belong to an algorithm. Purple ostriches welcome.
What Prince Understood
Prince didn’t fight Warner Bros. because he was difficult. He fought them because he understood that an artist who doesn’t own their name isn’t really an artist — they’re an employee with good stage presence. The battle cost him seven years, a chunk of his catalog, and the right to call himself by the name on his birth certificate.
Nostr solves that problem with 32 bytes of randomness and an elliptic curve.
It’s less dramatic than writing “SLAVE” on your face. It doesn’t look as good on a magazine cover. But it works — quietly, mathematically, irreversibly. No one can take your npub any more than Warner Bros. could take the symbol. (They tried. The math won.)
Your keys, your name, your identity. Generated in your browser, stored in your hands, recognized by every relay on the network.
The ostrich isn’t burying its head. It’s checking on the eggs.
Go generate your keypair. Back up your nsec. Join the network. And if you see a purple ostrich in your feed, you’ll know you’re in the right place.
(Prince would have posted as a glyph. But he’d have zapped generously.)