Your Nostr Key Is Not Rotatable. Plan Accordingly.

Key rotation in Nostr is a social convention, not a protocol feature. The correct response is to never need rotation: hardware signing, offline keys, and minimal trust in clients.

The Core Asymmetry

Your Bitcoin private key can be replaced by moving funds. Your Nostr key cannot. The key IS the identity. Rotate it and you start from zero: zero followers, zero trust, zero verification history.

There is no cryptographic migration. NIP-41 (never merged) proposed pre-committing a successor pubkey with a Bitcoin timestamp anchor. The idea is sound. The implementation does not exist in production clients.

What “Key Rotation” Actually Means Today

It means publishing a migration notice from your old key, asking followers to manually follow the new one, and hoping client support exists. This is a social process. Social processes fail when the attacker already holds your key: they publish the migration notice first.

The portal problem: whoever controls your old key controls the migration signal. If you are migrating because of a leak, the attacker migrates before you do.

The Correct Frame: Key Protection, Not Key Rotation

Three layers:

  • Signing isolation: never let your nsec touch a networked device. Amber on Android. Hardware signers. The nsec stays offline. Only signed events leave.
  • Client verification: use clients that never store your nsec server-side. A Nostr client that “logs you in with nsec” holds your key. That is custody.
  • Minimal exposure: use separate keys for different contexts where the stakes differ. Your public identity key signs posts. A separate key handles automated publishing.

The NIP-41 Path Forward

Pre-commit a successor pubkey today. Use OpenTimestamps (NIP-03) to anchor the commitment in a Bitcoin block. If your key leaks, your timestamp predates any attacker migration attempt. The attacker can sign a new commitment but cannot backdate the Bitcoin anchor.

This does not exist in most clients. Building it yourself is 50 lines of code. The spec is there: NIP-41 draft, NIP-03 for timestamping.

Conclusion

The question is not how to rotate your Nostr key. It is how to never need to.

Hardware signing protects against remote key extraction. Cold key management protects against client compromise. And the NIP-41 timestamp anchor is the fallback you build today so you never use it tomorrow.

Write a comment