Introduction

The NOSTR protocol (Notes and Other Stuff Transmitted by Relays) represents an innovative paradigm for publishing and distributing content on the decentralized web. Unlike traditional social platforms, NOSTR does not rely on proprietary central servers, but on an open and distributed network of simple entities called relays. These relays constitute the transport and connection infrastructure of the entire ecosystem. Understanding their operation is fundamental to appreciating the protocol’s characteristics of resilience, openness, and neutrality.

What are Relays? A Conceptual Definition

In NOSTR, a relay is essentially a minimal server that performs two fundamental tasks: receiving and forwarding messages. Users (identified by public cryptographic keys) do not “connect” to a single platform, but interact with one, or more commonly, many relays simultaneously. The relay is a simple transit point: it does not hold identities, does not apply proprietary recommendation algorithms (unless optionally and transparently), and, in its purest form, does not filter content except for basic technical reasons. It can be imagined as a decentralized bulletin board, or rather, a multitude of bulletin boards from which a user chooses where to post their messages (notes) and from which to read.

Technical Operation: Subscriptions and Publications

The protocol uses WebSocket as the primary means of communication. Interaction occurs through structured JSON messages of three main types: EVENT, REQ, and CLOSE.

• Publication (EVENT): A client (e.g., an application like Damus or Amethyst) sends an EVENT message to one or more relays it is connected to. The message contains the note, digitally signed by the user’s private key to verify its authenticity and integrity. The relay, after validating the signature and some basic parameters (like the timestamp), stores the event and retransmits it to all clients that have subscribed to relevant filters.

• Subscription (REQ): A client sends a REQ message to a relay, specifying a subscription_id and a set of filters. Filters are criteria such as “author X,” “keywords Y,” “event types Z.” The relay responds by sending the client all past events that satisfy the filters and, subsequently, forwards in real-time all new events that satisfy them.

• Subscription Closure (CLOSE): The client sends this message to terminate a specific subscription, stopping the data flow.

The architecture is publish-subscribe (pub/sub) and asynchronous. A user publishes to N relays and subscribes to M relays (often N and M are different), thereby aggregating a personalized view of the network.

Decentralized Architecture and Censorship Resistance

The choice to delegate the relay function to a multitude of independent operators is at the heart of NOSTR’s censorship resistance. The implications are profound:

• No Single Point of Failure: A relay can be shut down without affecting the ecosystem. The user only loses access to messages stored on that specific relay but can continue to publish and read through others.
• Individual Sovereignty: Users choose whom to trust with the propagation and archiving of their data. They can use public relays, private relays, or even run a personal one.
• Difficult Censorship Model: To effectively censor a user, a malicious actor would need to coordinate censorship across the majority of relays the user is connected to and that their community reads. This is inherently more difficult than acting on a central server.
• Identity Portability: Identity (the public key) is completely independent of relays. The user can change the set of relays they use at any time without losing their reputation or social connections (follows).

Types of Relays and Business Models

Not all relays are identical. The base specification is simple but leaves room for different implementations and policies:

• Public and Free Relays: These are the entry point for many users. They may be funded by donations, communities, or run by enthusiasts. They often impose usage limits to prevent abuse.
• Relays with Filters and Moderation: Some relays apply blacklists (NIP-51) for keywords, authors, or content types (e.g., images). This is an operator’s choice, and clients can openly view these policies.
• Paid Relays (NIP-XX for authentication, monetization concepts): To sustain costs and mitigate spam, some relays require payment, often via the Lightning Network, for publication or full access. This creates a sustainable economic model and a marginal cost for spammers.
• Private/Corporate Relays: Companies or communities can run exclusive relays for their employees or members, creating more controlled environments while remaining within the open protocol.

Advantages and Challenges

Advantages:

• Simplicity: The protocol is so simple that a basic relay can be written in a few hundred lines of code.
• Interoperability: Any client can talk to any relay, without the need for special APIs.
• Robustness: The network survives the disappearance of individual nodes.

Challenges and Considerations:

• Deduplication: The client receives the same event from multiple relays and must handle duplicates.
• Reliability and Performance: Service quality depends on the relay operator. Slow or unreliable relays impact the user experience.
• Metadata Privacy: Relays, and those observing them, know which relays you are connected to, when you are active, and which filters you subscribe to, which can reveal information about your social network and interests.
• Archiving and Costs: There is no guarantee of permanent archiving. If no relay archives your notes, they can disappear. The burden of preserving the network’s history is distributed and voluntary.

Conclusion

Relays are the vital, albeit deliberately “dumb,” element of NOSTR. They dematerialize the notion of a platform, turning it into a neutral and composable network service. They shift power from the service provider to the user, who is free to choose their own trade-off between cost, privacy, reliability, and moderation. The study of relays is therefore not only technical but touches on fundamental issues of network governance, data economics, and freedom of communication in the digital age. The NOSTR ecosystem, in its growth, will have to face the challenges of scalability and sustainability of this model, which remains one of the purest incarnations of the decentralized web dream.