All guides
#relays#nip-29#sovereignty

Bring your own relay

Obelisk has no central server; instead, you connect to any NIP-29 Nostr relay you trust. Each relay shows up as its own server in the rail. Here's how the multi-relay UX works and why it matters.

2 min read
Web of Trust graphA trust graph with your node at the center, connected nodes in lime green for high trust, and red-outlined spam nodes at the periphery.YOU!!!direct followfriend-of-friendfiltered (spam)

The relay is the server

In Discord, the "server" you join is Discord's server. In Obelisk, the "server" is a Nostr relay. Specifically, a relay that speaks NIP-29 (relay-managed groups).

When you open the app you'll see a left-side rail with one or more icons. Each icon is a relay. Click one and you see the NIP-29 groups that exist on that relay. Click + and you add another. Click and hold to remove one. The app itself is the same code; what changes is whose relay is on the other end of the websocket.

Why this matters

  • No vendor lock-in. Move your community to a different relay if you don't like the policies of the current one. Your key, your group memberships, your follows: all portable.
  • No network-wide deplatforming. Obelisk operates two public relays and can moderate only those. Any relay operator can ban you from their relay, but not from Nostr or an unrelated relay.
  • No platform deciding who can talk. The relay's operator sets the rules for that relay. If you don't like them, run your own (strfry, nostr-rs-relay, and others all support NIP-29).

Picking a relay

New installs currently include wss://public.obelisk.ar and wss://lacrypta-relay.obelisk.ar, both operated by Obelisk. You can remove or replace either one, add any NIP-29 relay, or run your own.

For a real community you probably want one of:

  1. Your own relay. A 5 USD/month VPS runs a NIP-29 relay easily for hundreds of users. You hold the data. You set the policy.
  2. A friendly public relay. Many community-run NIP-29 relays exist; pick one whose operator you trust.
  3. A private relay. If you only want a small invite-only group, run a relay that only accepts events from a fixed set of pubkeys.

How permissions work

Inside a NIP-29 group, the relay enforces three roles:

  • Admins: listed in a 39001 event. Can add members, kick, and ban.
  • Members: listed in a 39002 event. Can post.
  • Everyone else: depending on the group's metadata, may or may not read.

Kicking and banning are also Nostr events (9001, 9005). The relay refuses to publish messages from people who aren't allowed to post.

This means:

  • Moderation is portable. If you fork a community to a new relay, you replay the admin and member events to set up the same permissions there.
  • Moderation is auditable. Every kick is a signed event with a timestamp and a reason.
  • Moderation is the relay's job, not the app's. Obelisk doesn't enforce policies; the relay does.

What about spam?

Right now, anti-spam is whatever your relay enforces. Most NIP-29 relays use proof-of-work, allow-lists, or invite-based join flows. We're tracking community work on Web of Trust scoring at the relay level. Once relays expose a standard, the client can show trust scores in-line. (Earlier versions of Obelisk computed WoT in the backend; with no backend, the client now defers to whatever the relay enforces.)

What is ObeliskAn obelisk monument surrounded by orbiting Nostr keys and floating chat bubbles.Kn

What is Obelisk?

the elevator pitch

How Obelisk worksOn a usual chat platform, your account, your data and the rules live on the company's server, between you and your community. In Obelisk you sign each message with your own key and it goes straight to your community's relay, a NIP-29 relay: Obelisk runs a public one, and anyone can run their own. The Obelisk app only signs and shows.A USUAL CHAT PLATFORMYoumessageThe company's serveryour account · your data · its rulesYour communityOBELISKYou, with your keysigned messageYour community's relayObelisk's relayor your ownYour communityUse Obelisk's relay or run your own: your community depends on no one.

How Obelisk works

architecture detail

Future: Nostr relay-based groupsA mesh of Nostr relays exchanging encrypted group messages, with no central server.relay.arelay.brelay.crelay.drelay.erelay.fNIP-29 group

What shipped, and what's next

voice, bunker, more

Admission is a ladder, not a switchA self-hosted Nostr relay with three widening tiers of admitted keys around it, added by hand, two hops away, three hops away, each publishing on a smaller share of the rate budget, with a block list cutting across all three.relayyoursTIER 1added by hand6,000/minTIER 2two hops3,000/minTIER 3three hops1,500/minBLOCKEDchecked first, overrides every tiernothingDistance from your reference accountsis how much evidence you have.

Run your own relay: admission is a ladder, not a switch

the same graph, deciding who may connect