All guides
#moderation#nip-29#admins#roles

NIP-29 admins, members, and moderation

How admins run a relay community in Obelisk today. Channel admins edit their channel and its members from channel settings; the relay operator manages roles, members, emoji and layout from server settings. Every action is a standard NIP-29 event that any Nostr client can read.

4 min read
Admin tools in the appThe relay operator's server settings and a channel admin's channel settings, side by side. Both publish signed events to a NIP-29 relay, which checks and enforces them.NIP-78NIP-29Server settingsrelay operator onlyServer profileEmoji & stickersChannels & categoriesRoles & ranksMembers & moderationChannel settings#general ACCESSpublicread-onlyprivateTYPEtextvoice & videopublicationsMEMBERSaliceadmindemotebobmemberremove+ add by npubNIP-29 relaychecks and enforcesrelay operator: the whole relaychannel admins: their channelevery click is a signed event

Where moderation lives

In the old hybrid Obelisk, admins lived in a Postgres table and an admin web panel called an HTTP API to remove people. In the new Obelisk, the permissions live on the relay. The admin tools are in the app, but every click publishes a signed NIP-29 event, and the relay is the one that enforces it.

That means:

  • Any NIP-29 client can show the same admin list and member list.
  • Switching clients doesn't change permissions.
  • Switching relays does: moderation is per-relay-per-group, because the relay is the enforcer.

Two kinds of admin

Obelisk has two levels of authority, and they never mix:

  • Channel admins. A channel is a NIP-29 group. Its admins are the people listed in the relay's latest 39001 event for that group. They manage that one channel.
  • The relay operator. The pubkey the relay names as its operator (the contact npub in its NIP-11 document, else its pubkey). Only the operator sees the server settings, and only the operator's events change relay-wide things like roles, categories and branding.

Channel settings (channel admins)

Open a channel and click its settings in the channel header (on a phone, the channel's settings sheet). From there an admin can:

  • Edit the channel: name, description, icon and banner.
  • Set who gets in: public (everyone reads and posts), read-only (everyone reads, members post) or private (hidden, members only).
  • Pick the channel type: text, voice and video (a peer-to-peer mesh for small rooms), big-room voice (routed through an SFU you choose and verify), or publications (a feed of posts, each with its own chat, with curated tags).
  • Manage members: add someone by npub or hex key (optionally as an admin), demote an admin to member, or remove someone from the channel.

In the chat itself, an admin can delete any message in the channel ("Delete for everyone") and clear its reactions.

Server settings (relay operator)

The relay operator gets a server settings button at the top of the channel list. It opens five tools:

  • Server profile & banner: the name, icon, banner and description everyone sees for the relay.
  • Emoji, GIFs & stickers: the server's own favorites and packs, shown to every member.
  • Channels & categories: category names and the order of the channels in them.
  • Roles & ranks: tiered badges (name, color, emoji) shown next to member names. Members can hold several; the most senior one is the badge they wear. Roles are labels, not permissions: the relay still only knows admins and members.
  • Members & moderation: one table of every admin and member across every channel on the relay, filterable by name, role and channel, to demote or remove people in bulk.

The events behind the buttons

Every action above is one of these events, signed by the admin and timestamped by the relay. There's no hidden moderation log; the events are the log.

KindWhat it is
9007Create group: a new channel
9002Edit metadata: name, images, access, channel type
9000Put user: add a member, or make them an admin
9001Remove user: take someone out of the channel
9003Remove permission: demote an admin to member
9005Delete event: remove a message or reaction
39000Group metadata, published by the relay
39001Admin list, published by the relay
39002Member list, published by the relay

The relay checks each request against its own admin list before it accepts it, and then publishes the updated 39000/39001/39002 state. Roles, categories and branding are the operator's own replaceable events (NIP-78, kind 30078), and Obelisk only reads them from the operator's key.

What about removals across relays?

NIP-29 removals are per-relay. If someone is removed from your group on relay A, nothing stops them from creating a group with the same ID on relay B and posting there. This is by design: relays are sovereign. If you care about portable moderation, run your own relay (or a relay set you control) and replicate group state across them.

Where the admin CLI went

Earlier versions of Obelisk shipped a Node CLI (scripts/admin-cli) that drove an HTTP admin API with an nsec. The API is gone, so the CLI is gone too, and everything it did is now in the app's channel and server settings. A script can still do the same work without Obelisk: load a key with nostr-tools or any Nostr SDK, build the NIP-29 events above and publish them to the relay. The relay judges them exactly as it judges a click in the app.

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

the no-backend architecture

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)

Bring your own relay

relays as sovereign communities

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

Obelisk is a pure Nostr client with no backend. Voice channels, NIP-46 signer-app login, NIP-44 v2 encryption and the installable app have shipped. Still ahead: a static-export build and push notifications while the app is closed.

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 relay that enforces all of this