nostr:note1j4x2er6jwhnywp68vdfl2sc3e8xy2czmqkahveelyrj28jklqc0q7fcdmu
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.
cc @NostReport
Gotcha! My bad I didn’t understand the 60 day part as deeply as I thought. This has better protection than I thought!
This will be corrected in the original post. I imagine that the version of this content that was highlighted above won’t updated after the change (because of how replaceable events work) but anyone reading the original post from here on out will get the corrected version.
Oddbean new post about login | logout