Oddbean new post about | logout
▲ ▼
Sovereign Engineering | 1 years ago (raw) | root | parent | reply | flag 
 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.
▲ ▼
PABLOF7z | 1 years ago (raw) | root | parent | reply | flag +3 
 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 | 1 years ago (raw) | root | parent | reply | flag 
 cc @NostReport
▲ ▼
doc | 1 years ago (raw) | root | parent | reply | flag +1 
 Attention @greg
▲ ▼
greg | 1 years ago (raw) | root | parent | reply | flag 
 Gotcha! My bad I didn’t understand the 60 day part as deeply as I thought. This has better protection than I thought!
▲ ▼
NostReport | 1 years ago (raw) | root | parent | reply | flag +1 
 Thanks for the clarification @PABLOF7z - post has been edited

https://habla.news/nostreport/Nostr-Tech-Weekly-2023-10-22
▲ ▼
greg | 1 years ago (raw) | root | parent | reply | flag 
 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.