#nip
4 items · 4 articles
Articles
Algorithms as Identities: Why NIP-85 Matters
NIP-85 makes each algorithm a Nostr identity. Users follow algorithm-keys, see their outputs, and switch freely.
Curated Feeds: A Simpler Alternative to DVM Feeds
Replace DVM request/response overhead with simple replaceable events. Publishers maintain feed lists, clients just subscribe. No round trips, no privacy leakage
Owned by No One: Solving Nostr's Key Rotation Problem
Nostr's greatest strength - that you own your identity through cryptographic keys - becomes its greatest weakness when keys are lost or stolen. This post introduces two simple, social solutions that let users mark compromised keys and rotate to new ones through community verification, without complex cryptography or pre-planning.
The Gossip Vulnerability: Why NIP-17's "Deniable" Messages Aren't
NIP-17 promises deniable messaging with its three-layer design: an unsigned "rumor," a signed "seal," and an ephemeral "gift wrap." However, this setup has a hidden vulnerability. The signed seal allows recipients to prove that a message was sent by the claimed author, even without revealing the content. This creates a perfect scenario for gossip attacks, where the mere proof of communication can damage reputations. As we explore NIP-17, we find that the rumor, despite being unsigned, is not as deniable as it seems, making it a potential risk for exposure.