nips
nips copied to clipboard
nostr-protocol
Nostr Implementation Possibilities
_Note: I’m not sure this is the right place to raise/plant my idea, very sorry for that._ Nostr addressed most of the issues with Mastodon but it missed the key...
Proposal for a new nostr kind that stores GeoJSON data as the content. This kind, along with the existing p and e tag model, would make notes spatially aware on...
My name suggestion is NostrNameSystem (NNS) My kind suggestion is 50
NIP-26 allows certain `kind`s of Nostr messages to be delegated. However, given the proliferation of kinds, I think it makes sense to allow kind ranges, (ex: `kind=1-100&kind=102-200`) which would allow...
The current proposal uses SHA256 hashing for POW to incur a cost on a message creator. For a spammer, this is quite agreeable - he can purchase an ASIC and...
This PR aims to standardize an identity field in `kind0` metadata such that users can set their online identities as claims and clients can independently verify it however they see...
This NIP provides a way for clients to report profiles and notes to relays. This is currently implemented by Damus as an apple app store requirement, but may be useful...
add a new kind of event to allow report events or pubkeys ```json { "pubkey": "", "created_at": 1000000000, "kind": 8, // report kind "tags": [ ["p", "", "wss://..."], ["e", "",...
A universal relative web-of-trust reputation protocol on Nostr. UniWoT. https://github.com/brainspacer/nips/blob/master/55.md Authors: @brainspacer, @distbit0 Overview Reputation is multi-dimensional and sharding can be implemented to allow relays to handle specific dimensions of...
This NIP specifies that Nostr relays can implement a filter to check the balance of a bitcoin address derived from a Nostr public key. The filter will be triggered whenever...
