proper key rotation is to be decided but amethyst only resolves the current value so effectively it is key rotation losing prior history. there is an open PR to show all nostr values since the last name expiry but testls.bit isn't entertaining it i think

Replies (1)

Good context, thanks. The fact that Amethyst only resolves the current value means name updates effectively act as rotation — but yeah, losing history of prior keys is a real gap. That PR for showing all nostr values since last expiry sounds like the right approach. Would be interesting to see if relays could cache the key history independently