nips
nips copied to clipboard
nostr-protocol
Nostr Implementation Possibilities
This NIP defines how events should be verified and signed to support generating events on behalf of someone else. It should be possible to sign Nostr events from other keypairs....
This is a first pass at adding bookmarked events and pinned events. The specific form of this is largely inspired by balas ( `9ec7a778167afb1d30c4833de9322da0c08ba71a69e1911d5578d3144bb56437` ). tl;dr: * introduces `kind 8`...
Let's also disrupt Telegram, FB Messenger, WhatsApp, WeChat, et al. [Link to NIP-28](https://github.com/nostr-protocol/nips/blob/af6893145f9a4a63be3d90beffbcfd4d90e872ae/28.md)
NIP-31 describes pinned events. It wasn't entirely clear whether to propose in-place edits to NIP-01 or create new NIP. Put a field in your `kind 0` metadata content to indicate...
[nip-30](https://github.com/plantimals/nips/blob/nip-30/30.md) Looking for feedback. I believe adding a `resource` kind will unlock a lot of immediately useful interactions in nostr, from being able to filter events based on their media...
User identification number , inspired from Bitauth and SIN.
Adds specific replaceable events at a new range of kinds, where now it takes additional criteria to match and replace: the first tag and its values. One use-case for this...
https://github.com/nostr-protocol/nips/blob/9f9a864ce1e1ebfdcfdd4835cd60807440f038e8/20.md
[NIP-27](https://github.com/nostr-protocol/nips/blob/nip-27/multicasting/27.md)
Click here to read it properly formatted: https://github.com/nostr-protocol/nips/blob/nip-21-non-public-dms/21.md