Nostr Relays
How relays store, filter, reject, authenticate, monetize and distribute signed events in Nostr.
Relays are the server side of Nostr, but they are not a single platform server. Clients can connect to multiple relays. Relays can choose rules, business models, storage policies and communities.
What a relay does
A relay receives signed events from clients and responds to client subscriptions. It can store data, filter data, reject events, require authentication, charge for write access, support search or serve a specific community. Relays are deliberately simpler than giant centralized social platforms.
- Public relay. Open reach, usually more spam pressure.
- Paid relay. Payment can reduce spam and fund infrastructure.
- Community relay. A group or venue can define membership and rules.
- Archival relay. Storage and history become the main service.
- Search relay. Indexing and query quality become the product.
Relay choice is product design
A client with poor relay defaults can feel empty or noisy. A client with thoughtful relay strategy can feel fast and coherent. NIP-65 relay list metadata helps users advertise where they write and where they prefer to receive mentions.
Moderation and association
Because relays are privately operated, they can reject content according to their rules. Clients can select relays and apply their own filters. That creates a plural moderation model: no single universal feed, but also no single universal censor.
Crays venue relays
A Crays Super Node can turn a venue into a local relay and service layer. That matters for guests, creators, staff, access, payments and local demand. The venue is no longer only a location. It becomes a node in the social and commercial network.
Infrastructure role
Nostr Relays belongs to the relay infrastructure layer. The page should help you answer one concrete question instead of forcing you through a generic Nostr essay.
The short version is: How relays store, filter, reject, authenticate, monetize and distribute signed events in Nostr. The deeper version is to see which concept, standard, product surface or human decision actually changes because of it.
Read and write behavior
The useful machinery around Nostr Relays 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 relays 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.
- Read. Can clients fetch the expected events?
- Write. Does the relay accept and acknowledge useful events?
- Policy. What is rejected, priced, moderated or authenticated?
Policy and access
Test Nostr Relays 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 relays 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.
Monitoring and failure modes
In the relays 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 relays 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.
Operator questions
For us, Nostr Relays 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 relays 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.
Related relay concepts
The best next step from Nostr Relays is not a generic link pile. Connect it to the closest prerequisite, the closest technical standard and the closest practical example.
In the relays 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 Relays on the map
Read Nostr Relays as part of the Relays route, not as an isolated entry. Its main surface is network infrastructure: storage, delivery, moderation policy, paid access, relay lists, monitoring and local operation. 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 Relays 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. Relays 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, NIP-65, NIP-42, nostr.com. Treat those as anchors, then compare product behavior and NIP support.
What Nostr Relays should help you decide
A good page about Nostr Relays 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 pretending relays are invisible plumbing when they shape speed, discovery, spam resistance and availability. 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 Relays
Use this page with a concrete mental test: a relay page should explain what the relay stores, who operates it, how policies are exposed and what clients can infer. 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 Relays
The source list is part of the content, not decoration. For Nostr Relays, 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 Relays
Before reading Nostr Relays, 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 Relays, 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.