Nostr Events and Event Kinds
The event model behind Nostr: ids, pubkeys, timestamps, kinds, tags, content and signatures.
Nostr has one basic object: the event. The event is signed, identified, timestamped and tagged. Different event kinds let clients understand profiles, notes, reactions, long-form content, badges, wallet requests and many other formats.
The event object
NIP-01 defines the basic flow. An event includes an id, a public key, creation time, kind, tags, content and signature. The signature proves that the holder of the private key authorized the event content.
- id. A hash of the serialized event data.
- pubkey. The author identity.
- created_at. Unix timestamp.
- kind. The category of event.
- tags. References, metadata, relay hints and structured context.
- content. The payload, often text but not always.
- sig. The Schnorr signature.
Why kinds matter
Kinds let clients interpret the same event structure differently. A short note, profile metadata, reaction, badge, long-form article, zap receipt or relay list can all use the event model while carrying different meaning.
Tags are the connective tissue
Tags connect events to people, events, relays, addresses, hashtags, geographies, communities, payments and external references. A strong product often depends more on tag design and indexing than on raw posting.
Crays event thinking
For us, event kinds and tags can represent profile context, follows, content access, status, award votes, venue signals, membership proof and governance participation. The design challenge is to make that useful without exposing users to protocol clutter.
What this standard changes
Nostr Events and Event Kinds belongs to the protocol standards layer. The page should help you answer one concrete question instead of forcing you through a generic Nostr essay.
The short version is: The event model behind Nostr: ids, pubkeys, timestamps, kinds, tags, content and signatures. The deeper version is to see which concept, standard, product surface or human decision actually changes because of it.
Who has to implement it
The useful machinery around Nostr Events and Event Kinds is keys, clients, relays, signed events, NIPs, wallets, media and search layers. Name those moving parts directly, because vague protocol language is where confusion starts.
In the events-and-kinds chapter, A strong page gives you enough context to recognize the term in another client, NIP, relay policy, wallet prompt or source document without pretending every reader is already a protocol engineer.
- Status. Is the NIP mandatory, optional, draft, final or unrecommended?
- Layer. Client, relay, signer, wallet, media server or indexer?
- Adoption. Where can you verify support?
Event, tag or service surface
Test Nostr Events and Event Kinds by asking what is signed, where it is stored, who renders it, which relays or services are involved and what survives when the first app or server is unavailable.
In the events-and-kinds chapter, That test keeps the explanation tied to reality. It also tells us which internal links belong in the body: foundations first, then standards, then practical examples.
Compatibility and adoption
In the events-and-kinds chapter, The main risk is that the page can become a definition instead of an explanation. The page should say that plainly and then show the safer reading: what works today, what is experimental and what needs source verification.
In the events-and-kinds chapter, This is where dense content beats long content. Give the reader facts, constraints, examples and next steps instead of repeating broad claims about openness or decentralization.
Product risk
For us, Nostr Events and Event Kinds matters only when it improves understanding or helps a real flow: identity, publishing, relay choice, signing, payment, media, moderation, commerce, venue context or governance.
In the events-and-kinds chapter, That does not mean every page has to become our product pitch. It means the page should make the connection visible when the topic affects our ecosystem, and stay purely educational when it does not.
Neighboring standards
The best next step from Nostr Events and Event Kinds is not a generic link pile. Connect it to the closest prerequisite, the closest technical standard and the closest practical example.
In the events-and-kinds chapter, A large archive becomes useful when every page behaves like a node in a knowledge graph: this explains one thing, points to what it depends on and shows where the idea is used.
How to place Nostr Events and Event Kinds on the map
Read Nostr Events and Event Kinds as part of the NIPs route, not as an isolated entry. Its main surface is technical standards: event kinds, tags, messages, identity formats, encryption, wallet flows and client-relay agreements. That framing matters because a Nostr page is useful only when you can see which layer it belongs to and which layer it does not solve by itself.
The first question is practical: what changes for you if Nostr Events and Event Kinds works well? Sometimes the answer is safer signing, sometimes better relay discovery, sometimes clearer media storage, sometimes a stronger source trail. Keep that question in front of you and the page becomes easier to judge.
- Layer. NIPs is the parent route, so the page should send you back to that shelf and sideways into adjacent concepts.
- Evidence. The current source trail starts with NIP-01, Nostr NIPs, nostr.how, Nostr protocol repository. Treat those as anchors, then compare product behavior and NIP support.
What Nostr Events and Event Kinds should help you decide
A good page about Nostr Events and Event Kinds should leave you with a decision, not just recognition. You should know whether it is a protocol primitive, a client behavior, a relay operation, a product example, a research source or our implementation question. That distinction keeps the archive from becoming a flat glossary.
The common mistake is presenting a NIP as if support were automatic across every app and relay. We avoid that by making the claim, the evidence and the next step visible. If a statement depends on a NIP, the page should point to that NIP. If it depends on a project, the page should show the project source. If it affects user safety, the page should say what can fail.
The working example behind Nostr Events and Event Kinds
Use this page with a concrete mental test: a NIP page should translate the spec into product consequences, failure cases and the reader-visible behavior it enables. That example is more useful than a generic definition because Nostr is not one product. The same signed event can be read by different clients, stored by different relays and interpreted through different product choices.
This is also why internal links matter. When the page mentions keys, clients, relays, events, zaps, Blossom, Cashu, FoundUPS or NIPs, those words should lead to the page that explains the concept more deeply. The goal is not to trap you in tabs; the goal is to let you move with context.
Source discipline for Nostr Events and Event Kinds
The source list is part of the content, not decoration. For Nostr Events and Event Kinds, use primary protocol documents first when the claim is technical, project repositories or product pages when the claim is about an app, and research or directory sources when the claim is about ecosystem position. If the sources disagree, the page should show the uncertainty instead of smoothing it away.
That source discipline is how a large archive stays trustworthy. It also helps learning: you get a short explanation first, then a route to the source that proves or complicates it. The page should feel like a guided chapter, but the evidence should still be close enough to inspect.
Before and after reading Nostr Events and Event Kinds
Before reading Nostr Events and Event Kinds, make sure you know the nearby base concepts: a public key identifies, a private key signs, relays carry signed events, clients render those events, and NIPs describe shared behavior. You do not need to memorize the whole protocol, but those pieces prevent most confusion.
After reading Nostr Events and Event Kinds, the next useful move is to compare it with one neighboring page. If this is an app, compare it with a signer, relay or wallet page. If this is a NIP, compare it with the product behavior it enables. If this is a research source, compare it with the hub that uses it. That is how the archive becomes a learning path instead of a pile.
The navigation job of Nostr Events and Event Kinds
Nostr Events and Event Kinds also has a navigation job. It should help you decide whether to move upward to the NIPs hub, sideways to a related concept, or downward into a more technical source. That sounds simple, but it is the difference between browsing and learning.
When a page does that job well, you do not need to keep the whole archive in your head. The page carries enough context to orient you, enough links to continue, and enough source discipline to show where the claims come from.