HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nostr-protocol
nips
Communication & Social2022–2026
nostr-protocol / nips

nips

Nostr Implementation Possibilities

Communication & Social
Explore on GitHubRead Hacker News discussions
44Distinct people
61Mentions
0Explicit recommenders
3.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Nostr Implementation Possibilities

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year61 dated mentions

Observed mentions: 2022-11-25 20:22:21 UTC to 2026-10-17 16:09:57 UTC.

01020302022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 33 mentions; 2 submissions, 31 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC615
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC33231
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC817
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC10010
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC413

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
NIPs NIPs stand for Nostr Implementation Possibilities. They exist to document what may be implemented by Nostr-compatible relay and client software. NIPs listed here are not a protocol checklist. Nothing forces any software to implement any NIP. Each app picks the subset relevant to its use case. Don't implement something just because it exists in this repo. Other standards and NIPs may exist outside this repository (e.g. as pull requests) and may already be deployed in the wild -- they should also be considered for implementation. List Event Kinds Message Types Client to Relay Relay to Client Criteria for acceptance of NIPs Is this repository a centralizing factor? How this repository works License List NIP-01: Basic protocol flow description NIP-02: Follow List NIP-03: OpenTimestamps Attestations for Events --- unrecommended: vulnerable to one specific attack, needs update NIP-04: Encrypted Direct Message --- unrecommended: deprecated in favor of NIP-17 NIP-05: Mapping Nostr keys to DNS-based internet identifiers NIP-06: Basic key derivation from mnemonic seed phrase --- unrecommended: prefer a single nsec NIP-07: window.nostr capability for web browsers NIP-08: Handling Mentions --- unrecommended: deprecated in favor of NIP-27 NIP-09: Event Deletion Request NIP-10: Text Notes and Threads NIP-11: Relay Information Document NIP-13: Proof of Work NIP-14: Subject tag in text events NIP-15: Nostr Marketplace (for resilient marketplaces) --- unrecommended: too complicated, try 99 instead NIP-17: Private Direct Messages NIP-18: Reposts NIP-19: bech32-encoded entities NIP-21: nostr: URI scheme NIP-22: Comment NIP-23: Long-form Content NIP-24: Extra metadata fields and tags NIP-25: Reactions NIP-26: Delegated Event Signing --- unrecommended: adds unnecessary burden for little gain NIP-27: Text Note References NIP-28: Public Chat --- unrecommended: try NIP-29 instead NIP-29: Relay-based Groups NIP-30: Custom Emoji NIP-31: Dealing with Unknown Events --- unrecommended: unnecessarily bloated NIP-32: Labeling NIP-34: git stuff NIP-35: Torrents NIP-36: Sensitive Content NIP-37: Draft Events NIP-38: User Statuses NIP-39: Linking Profiles to Other Platforms NIP-40: Expiration Timestamp NIP-42: Authentication of clients to relays NIP-43: Relay Access Metadata and Requests NIP-44: Encrypted Payloads (Versioned) NIP-45: Counting results NIP-46: Nostr Remote Signing NIP-47: Nostr Wallet Connect NIP-48: Bridged Events NIP-49: Private Key Encryption (ncryptsec) NIP-50: Search Capability NIP-51: Lists NIP-52: Calendar Events NIP-53: Live Streaming and Spaces NIP-54: Wiki NIP-55: Android Signer Application NIP-56: Reporting NIP-57: Lightning Zaps NIP-58: Badges NIP-59: Gift Wrap NIP-5A: Static Websites (nsites) NIP-60: Cashu Wallet NIP-61: Nutzaps NIP-62: Request to Vanish NIP-64: Chess (PGN) NIP-65: Relay List Metadata NIP-66: Relay Discovery and Liveness Monitoring NIP-67: EOSE Completeness Hint NIP-68: Picture-first feeds NIP-69: Peer-to-peer Order events NIP-70: Protected Events NIP-71: Video Events NIP-72: Moderated Communities --- unrecommended: try NIP-29 instead NIP-73: External Content IDs NIP-75: Zap Goals NIP-77: Negentropy Syncing NIP-78: Application-specific data NIP-7D: Forum Threads NIP-84: Highlights NIP-85: Trusted Assertions NIP-86: Relay Management API NIP-87: Cashu and Fedimint Discoverability NIP-88: Polls NIP-89: Recommended Application Handlers NIP-90: Data Vending Machines --- unrecommended: this got totally out of control, prefer use-case-specific microstandards NIP-92: Media Attachments Metadata (imeta) NIP-94: File Metadata NIP-96: HTTP File Storage Integration --- unrecommended: replaced by Blossom NIP-98: HTTP Auth NIP-99: Classified Listings NIP-A0: Voice Messages NIP-A3: payto: Payment Targets NIP-A4: Public Messages NIP-B0: Web Bookmarks NIP-B7: Blossom NIP-BE: Nostr BLE Communications Protocol --- unrecommended: only implemented once and unclear whether it works, requires review NIP-C0: Code Snippets NIP-C7: Chats NIP-CC: Geocaching NIP-CD: Slash Commands NIP-EE: E2EE Messaging using MLS Protocol --- unrecommended: superseded by the Marmot Protocol NIP-F4: Podcasts Event Kinds This table is not exhaustive. For a machine-readable registry of all known event kinds prefer https://github.com/nostr-protocol/registry-of-kinds (or alternative registries following the same YAML schema). kind description NIP 0 User Metadata 01 1 Short Text Note 10 3 Follows 02 4 Encrypted Direct Messages 04 5 Event Deletion Request 09 6 Repost 18 7 Reaction 25 8 Badge Award 58 9 Chat Message C7 11 Thread 7D 13 Seal 59 14 Direct Message 17 15 File Message 17 16 Generic Repost 18 17 Reaction to a website 25 20 Picture 68 21 Video Event 71 22 Short-form Portrait Video Event 71 24 Public Message A4 30 internal reference NKBIP-03 31 external web reference NKBIP-03 32 hardcopy reference NKBIP-03 33 prompt reference NKBIP-03 40 Channel Creation 28 41 Channel Metadata 28 42 Channel Message 28 43 Channel Hide Message 28 44 Channel Mute User 28 54 Podcast Episode F4 62 Request to Vanish 62 64 Chess (PGN) 64 78 Application-specific Data 78 443 KeyPackage Marmot 444 Welcome Message Marmot 445 Group Event Marmot 818 Merge Requests 54 1018 Poll Response 88 1021 Bid 15 1022 Bid confirmation 15 1234 Draft Checkpoint 37 1040 OpenTimestamps 03 1059 Gift Wrap 59 1063 File Metadata 94 1068 Poll 88 1111 Comment 22 1222 Voice Message A0 1244 Voice Message Comment A0 1311 Live Chat Message 53 1337 Code Snippet C0 1617 Patches 34 1618 Pull Requests 34 1619 Pull Request Updates 34 1621 Issues 34 1622 Git Replies (deprecated) 34 1630-1633 Status 34 1971 Problem Tracker nostrocket 1984 Reporting 56 1985 Label 32 1987 AI Embeddings / Vector lists NKBIP-02 2003 Torrent 35 2004 Torrent Comment 35 2022 Coinjoin Pool joinstr 4550 Community Post Approval 72 7374 Reserved Cashu Wallet Tokens 60
Read the full README on GitHub

What Hacker News says

61 sources
iamnothere·Oct 17, 2026
Thanks, not sure who would have flagged your comment but I vouched it. Redundancy in download traffic makes sense, although NIP 77 should help with this: https://github.com/nostr-protocol/nips/blob/master/77.md I think I see Nostr as having some of the best points of both decentralization and your “small community” concept. As a user I can be as decentralized as I want to be (or totally centralized!) by publishing to as few or as many relays as I want. I can also hoard my events and republish if relays go offline. And followers can find my content through multiple channels: I don’t necessarily know or care what relay they use. I don’t necessarily think that the small community approach is bad for everyone. Some people may even prefer the ephemerality of it. I just get tired of building on sand.
In We don't want decentralized systems, we want small ones
cykros·Oct 11, 2026
I'd rather see something involving micropayments, likely using the Lightning network, to make viewing a single article for the cost of one viable. And in fairness this does exist on Nostr (I think in multiple forms). It's just not widely used. Not least because most on Nostr don't really believe in the idea that information can be owned in the first place. https://github.com/nostr-protocol/nips/pull/2156 for discussion around the NIP.
In Show HN: WallHop – 12ft.io is gone, so I built a replacement
digitalbase·Dec 16, 2025
I'm building a Q&A/community on top of Nostr and using those same concepts: Original Author posts a kind:1 note with a question A bot sends a kind:1985 note (NIP-32 https://github.com/nostr-protocol/nips/blob/master/32.md) that labels the content. It can be done by the author (self-label), by an app, or by third parties (moderators/curators), depending on the trust model. Other clients can decide to use that classification/label -- For moderation purposes. If the behavior is closer to abuse (spam, scams, harassment...), use NIP-56 (Reporting). Reporting harmful/should-be-moderated content.
In Nature's many attempts to evolve a Nostr
hugs·Oct 12, 2025
from an an average developer perspective, nostr is interesting because it's "just" a digitally signed json data structure sent over a websocket. reading the spec [1] for creating a simple nostr client (aka "nip-1"), my average developer brains thinks: i could do that. i don't get that same feeling when reading atproto or activitypub docs. ultimately, there's a reason why all these protocols get complicated at scale, but in the simple case, nostr is very easy to make a client for and start playing with. nostr feels like a good example case for gall's law: "a complex system that works is invariably found to have evolved from a simple system that worked." [1]: https://github.com/nostr-protocol/nips/blob/master/01.md
In Nostr and ATProto (2024)
synesso·Aug 9, 2025
It's tangentially related through the theme of decentralization - It's trying to be a very decentralized chat application - The linked post is on nostr, which decentralized broadcast messaging protocol - Bitcoin is a decentralized money protocol - Nostr has the capability to send bitcoin between users via the lightning network via https://github.com/nostr-protocol/nips/blob/master/57.md It takes more effort to use nostr than it does anything relatively more centralized like bluesky or mastodon. So people there are the kind who are dedicated to decentralized technologies & support bitcoin.
In Testing Bitchat at the music festival
hugs·Jul 10, 2025
(fwiw, I'm not the creator of this, but am a casual user of Nostr...) tl;dr: the answer you're looking for is probably in the explainer doc [1]. At its core, Nostr is simple: it's "just" JSON over WebSockets. But there are dozens of optional proposals to add additional functionality. And a few of those proposals are related to encrypted DMs, specifically, NIP-04 [2], and NIP-17 [3]. Most of the online criticism of encrypted DMs on Nostr is about NIP-04 (which is why it's deprecated.) White Noise is using a different encryption standard: MLS (Messaging Layer Security) [4]. They explicitly say in their docs: "White Noise is an implementation of the NIP-EE spec." [5]. The NIP-EE proposal itself is on GitHub [6]. The explainer doc [1] I first mentioned is linked to from the proposal [6]. This is all to say: given all the links I posted here,
Read the rest
an AI chatbot could probably give you a better answer using the prompt: "How is NIP-EE (Messaging Layer Security for Nostr) different or better than NIP-04 or NIP-17?" (I'm a little surprised that wasn't already in the FAQ for the project.) [1]: https://github.com/nostr-protocol/nips/blob/001c516f7294308143515a494a35213fc45978… [2]: https://github.com/nostr-protocol/nips/blob/master/04.md [3]: https://github.com/nostr-protocol/nips/blob/master/17.md [4]: https://www.rfc-editor.org/rfc/rfc9420.html [5]: https://github.com/parres-hq/whitenoise?tab=readme-ov-file#the-spec [6]: https://github.com/nostr-protocol/nips/pull/1427
In White Noise – secure and private messenger

Showing the 15 most recent of 61 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.