m4d4m on Nostr: Interesting, if I understand this correctly: 1) the trade-off is basically about how ...

Interesting, if I understand this correctly:

1) the trade-off is basically about how much time to allocate. Balancing the potential leak damage (timespan) versus nsec access frequency (how often to create epoch keys).

2) this basically gives me (or the nostr client) a temporary key to protect instead of using the nsec for each event.

Have other solutions been proposed? If so, why weren't they implemented?

(https://untraceabledigitaldissident.com/nostr-cold-root-epoch-key-rotation/)

quoting
nevent1q…nff7

Cold Root Identity v0.1.0

Cold Root Identity is a simple model for survivable Nostr identities. No protocol changes, no new relay behavior, and no delegation logic.

The idea is straightforward:

- A root key stays offline as the authority

- Epoch keys are derived deterministically for actual daily use

- A signed lineage event proves each new epoch key is legitimate

- Clients treat the newest valid epoch as the user’s active identity

- Old posts stay under old keys; new posts use the fresh one

This gives users safe key rotation without burning their entire account. A compromise only affects a single window instead of the whole identity.

The Python reference implementation, test vectors, and spec are here:

https://github.com/GHOST-UntraceableDigitalDissident/cold-root-identity

If you’re a client dev, this is everything needed to implement rotation cleanly today.