The resistance moves in the clear. The Suits are watching every relay.
Here is how we stay ghosts.
In the neon sprawl of Los Soluna, the underground coordinates over Nostr because it is decentralized, pseudonymous, and resistant to single points of failure. But the same properties that make it powerful also make it dangerous if you do not treat it like the battlefield it is.
One reused key. One sloppy relay choice. One browser that phones home. That is all the Suits need to link your operations to your flesh.
Move through Nostr as if every relay is tapped and every pubkey is a warrant. Use the tools below to test your current posture, then internalize the protocols until they become muscle memory.
Nostr is a simple protocol for global, uncensorable public broadcast notes ⓘ signed with cryptographic keys. You publish to relays ⓘ — they are not your friends. Your npub is your public handle. Your nsec is the nuclear launch code.
Modern clients use NIP-07 browser extensions ⓘ so the dangerous secret never touches the page. Everything else (relays, zaps, follows, DMs) is layered on top of this primitive.
It is the most powerful public square the resistance has ever had. It is also one of the easiest places to accidentally paint a target on your back.
Your pubkey is a permanent fingerprint. Every note, every zap receipt, every relay list you publish carries it. The only way to break the graph is to stop giving them the same fingerprint in different contexts.
That is why the first deep section of this briefing is the Identity Forge — multiple distinct keys, remote signers, and correct backup hygiene. Everything else (Tor, gift wrap, client choice, relay strategy) is layered on top of that foundation.
Your first and most important operational decision on Nostr is never reuse the same identity across different risk contexts.
The pubkey on every event is a permanent fingerprint. Same key + any correlation (style, timing, relays, zaps, follows) = linkable. This is why the resistance runs on ephemeral, context-specific keypairs.
Generate fresh keys with trusted FOSS tools:
nak key generate ⓘ,
nostril --gen ⓘ,
or use Amber ⓘ for signing without ever exposing the nsec.
Your nsec is the only thing standing between you and total compromise. Back it up like your life depends on it — because in the resistance, it might.
Never store an nsec in any cloud service, password manager, email, or notes app that syncs. The second it touches the internet unencrypted, assume it is burned.
Store high-value keys on encrypted USB drives or metal backups (titanium plates, fireproof seed plates). Keep at least two copies in separate physical locations.
For true one-time or high-risk ops, generate the key, use it, then destroy all backups. Do not keep anything that can link it back to you later.
Periodically verify that you can actually restore from your backups. A backup you cannot restore from is worse than no backup at all.
Rate your current backup habits. This is saved only in your browser.
Every note you publish travels through one or more relays. Choose poorly and the Suits get a map. Choose carefully and you stay a ghost.
Your distinct keys (from the Identity Forge above) only protect you if the way those keys move through the network does not betray the separation.
Toggle your habits below. This is a simplified educational model — real risk is always higher than the number shows.
Your keys are isolated. Your relays are chosen. Now the actual weapons: the clients you run and the way you sign, zap, and coordinate.
Everything below is how you turn good identity and relay hygiene into real operational capability.
Once you have a good client, these are the habits that actually keep you alive.
In the resistance, your signature is your identity. One mistake and the Suits can own you.
If a website, app, or person asks you to paste your private key, walk away. The moment your nsec leaves your device, operational security is dead.
The correct way to sign events:
In the resistance, zaps are one of the few ways to send real value without asking for permission. Treat them with the care they deserve.
When zapping from high-risk identities, always route through Tor if possible.
Zaps can be one of the easiest ways to correlate identities if you're not careful.
When the resistance needs to coordinate without the Suits building a social graph, we don’t use normal DMs.
Regular encrypted DMs still leak who is talking to whom. Gift Wrap fixes this by layering encryption so relays can’t easily see the real sender or receiver.
Every event you publish is intercepted and analyzed here. Toggle the defenses the resistance actually uses and watch your fingerprint disappear.
Both boxes show the exact same resistance message. The left shows what an observer (the Suits) can extract when you use normal habits. The right shows what reaches the relay after you flip the defenses above.
Your personal resistance readiness score. Saved only in your browser. Export it. Study it. Improve it.
Curated tools, NIPs, and references for those who want to go further.
If this briefing has been useful, consider sending a zap to the public resistance npub. Every sat helps keep the shadows alive.