The only way this catches on is by using kind 1521 by itself, which I will start doing to report inactive profiles that have migrated
I was writing and them I stumbled on this even simpler version that is even more left-side of the bell-curve
https://github.com/nostr-protocol/nips/blob/key-invalidation-and-migration/37.md
Discussion
what if we just start with kind:1521 with opentimestampped events; this seems like such a trivial get and doesn't open the door of crypto/HD bikeshedding.
Regardless, if we do HD keys we'd still need to do kind:1521 stuff as described in https://github.com/nostr-protocol/nips/blob/key-invalidation-and-migration/37.md
what do you think nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s ?