The Outbox Model: Find People Where They Publish
Outbox thinking makes relay discovery less random by following the places where each person actually writes.
The problem with one global door
A centralized social app has one main database. Nostr does not. That is the point, but it creates a discovery problem. If a client asks only its own default relays for every person, it may miss events published elsewhere. If it asks every known relay, it becomes slow, expensive and noisy.
The outbox model offers a more human answer: follow each person to the relays where they publish. If Alice writes to one set and Bob writes to another, a smart client learns both instead of pretending the whole network lives behind one door.
Relay lists become social infrastructure
NIP-65 relay list metadata gives outbox discovery a public clue. A profile can say, in effect, 'these are the places where I write and read.' Clients can use that to build better queries. The result is not perfect, but it is a major improvement over blind relay guessing.
This also makes your relay choices more consequential. If your published list is stale, others may look in the wrong place. If your write relays are unreliable, your profile may appear fragmented. If your client never updates the list, portability slowly decays.
Outbox is product design, not only protocol
The hard part is not just reading a relay-list event. The hard part is turning it into a feed that feels normal. A client has to cache hints, merge responses, avoid duplicates, handle failed relays, update stale data and explain enough of the process when a user needs to troubleshoot.
Done well, outbox discovery makes Nostr feel less random. Done poorly, it can make feeds look broken without telling you why. That is why relays, clients and standards have to be discussed together.
Why this matters for communities
Communities do not all live in the same place. A Bitcoin-heavy cluster may use one set of relays. A local event group may use another. A developer community may rely on fast public relays and search tools. Outbox discovery lets those communities remain separate without becoming invisible to each other.
This is especially important for Crays-style local spaces, venues and membership layers. A real-world community can use relays that make sense for its context while still being reachable from the broader Nostr map.
What to watch next
Watch how clients expose relay health, relay lists and discovery settings. A good client should not make you babysit every endpoint, but it should give you enough visibility to understand why an event is missing.
Also watch relay monitoring and liveness standards. Outbox discovery is only as good as the relay signals underneath it. If clients cannot tell whether relays are alive, slow, paid, restricted or stale, the map remains fuzzy.
Sources worth opening
Open these when you want the standard, implementation, monitor or operator trail behind the page.
- NIP-65: Relay list metadata
- Nostr Design: Relays
- NIP-50: Search capability
- NIP-66: Relay liveness monitoring
