Briefing

Trustless communication

Nostr

Nostr is a communication protocol built around signed events and relays. It is useful as an example of a system that reduces dependence on a single platform, but it brings its own moderation and spam problems. [R1][R2]

Back to handbook Go back

Sections

Use this page as a guide: start with the mechanism, then look at use cases, comparisons, and limits.

Plain termsKeys, relays, and signed events. Why people careWhere portability and relay choice matter. Compare againstCheck the platform model it pushes against. LimitsModeration, spam, and trade-offs.

In plain terms

Nostr separates identity, content, and transport so no single platform owns the whole stack. [R1][R2]

Core mechanism

  • Users generate a key pair. [R1]
  • Messages are signed as events. [R1]
  • Clients publish those events to relays. [R1]
  • Other clients subscribe to relays and read the events back. [R1]

Why people call it trustless

  • Identity is tied to cryptographic keys rather than accounts controlled by one platform. [R1]
  • Events can be verified independently. [R1]
  • Users can choose different relays and clients. [R1]
  • Control is distributed across the network rather than concentrated in one server. [R2]

Why people care about it

Nostr matters only in the places where portability and reduced platform dependence are more important than a polished mainstream product.

Public conversation

Useful when talking about communication without a central platform owner. [R1]

Portable identity

Keys are the anchor, so users can move clients without losing identity. [R1]

Media and storage hooks

Nostr can pair with Blossom for uploads and with content-addressed storage for some workflows. [R1][R2]

Bitcoin-adjacent ecosystem

It fits the handbook's interest in open, signed, and interoperable systems. [R1]

Compare against

The comparison is usually with mainstream social platforms rather than a blank sheet.

Mainstream platforms

  • Centralised platforms usually have better discovery and moderation tools. [R1]
  • They often provide easier onboarding and better default UX. [R1]
  • They also concentrate control and policy decisions in one place. [R1]

Nostr differs when

  • Identity portability matters more than platform convenience. [R1]
  • You want users and clients to be able to move between relays. [R1]
  • You accept that the trade-off is more operational complexity. [R1]

Limits and trade-offs

What critics are right about

  • Relay quality affects the user experience. [R1]
  • Spam and moderation are still real problems. [R1]
  • Discoverability needs active work. [R1]
  • Some applications still rely on third-party infrastructure for convenience. [R1]

Boundaries

  • Moderation still needs active design and governance. [R1]
  • Data persistence still depends on the surrounding infrastructure. [R1]
  • Mainstream platforms still serve many use cases more effectively. [R1]
  • It is strongest when paired with open storage and identity tooling. [R2]

Primary sources

Further reading

  • Compare Nostr with Blossom to see how communication and media storage can be split apart.
Back to handbook Go back Back to topic loop

Sources

References