Nostr Web Client

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.

PABLOF7z 2y ago

cc nostr:npub19mduaf5569jx9xz555jcx3v06mvktvtpu0zgk47n4lcpjsz43zzqhj6vzk

Reply to this note

Please Login to reply.

Discussion

⚡️ᗪㄖ匚⚡️ 2y ago

Attention nostr:npub1r3fwhjpx2njy87f9qxmapjn9neutwh7aeww95e03drkfg45cey4qgl7ex2

Greg 2y ago

Gotcha! My bad I didn’t understand the 60 day part as deeply as I thought. This has better protection than I thought!

The Nostr Report 2y ago

Thanks for the clarification nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft - post has been edited

https://habla.news/nostreport/Nostr-Tech-Weekly-2023-10-22

Greg 2y ago

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.