Sovereign Engineering on Nostr: nostr:note1j4x2er6jwhnywp68vdfl2sc3e8xy2czmqkahveelyrj28jklqc0q7fcdmu This is ...

quoting note1j4x…cdmu

In the case of a contested 1777 (the real owner and the hacker both publish a kind 1777) then it’ll be up to users to follow the pubkey of who they think is the real successor and not the hacker.

This is inaccurate:

A contested key migration event is decided by which key has the oldest attestation.

If the key created a whitelisting event in 2023, and then an attacker creates a whitelisting event in 2024 and immediately proceeds to generate a migration event to the new key they just whitelisted, the user has 60 days to migrate to key from 2023.

No room for ambiguity.