If your goal is knowing when something was published, OTS certainly gives you that. An attacker will duplicate the update, and also register it with OTS. The next time you update your profile, the attacker is more authoritative than you. OTS gives you "the PoW of the blockchain", but only for knowing a time something happened before.

Collective PoW gives you something else: an expensive notion of how much the network trusts your npub

Reply to this note

Please Login to reply.

Discussion

Yeah i don't think the OTS in this instance is all that helpfull either, especially because older kind0 events are not stored by default.

When it comes to this stuff i am a WoT maxi, i don't really think it is worth doing much else. I have a scheme in mind that could streamline the entire thing, but need to sit down to work the explanation out more at some point.

nostr:nevent1qqsxxwykxh452jw007kv5gpjr9lzp24ajylqhyhy9meyva3t3fkp6vqpzpmhxue69uhkummnw3ezumt0d5hsygz753jgq3dmrlezye2am5mwdh8dm3p4jrpxpyxys6l08rh52rd9h5psgqqqqqqsthmsda

That seems complex. Proof of Work is less complex, but no one's using that either, so 🤷🏻‍♂️ Maybe it's a problem that isn't really a problem. If someone who I'm not following messages me, I just ignore it

Im confused how you come away with that being complex, whilst its the simplest form of WoT possible

Why have expiring WoT attestations when you can use public follow lists?