Obelisk Guides
Everything about Obelisk: what it is, how it works, and where it's going. Written plain, no jargon walls.
Run your own relay: admission is a ladder, not a switch
Obelisk Relay is a NIP-29 relay that decides for itself who may connect: a hand-written allowlist, the accounts your references follow, and the follow graph beyond them, each on a smaller share of the rate budget. Two commands to run one.
Chain Reaction, played on a relay
Drop an orb, take a cell, and when a cell holds one orb too many it bursts into its neighbours, and their neighbours. Chain Reaction runs in an Obelisk channel with no game server; every client replays the same event log and reaches the same board.
Stacker: real-time falling blocks over Nostr
Six players, one shared piece order, and every line you clear buries somebody else. Stacker runs its board locally at sixty frames a second and publishes only the consequences: attacks, top-outs, and checkpoints anyone can replay.
Vesta: settlements, trade, and dice nobody rolls
Vesta is a settlement-building game running inside an Obelisk channel. The rules come from an upstream package we track rather than fork, the dice are derived from the event log instead of rolled by a player, and every client checks every move.
Making your DMs quantum-safe
Encrypted messages you send today can be recorded now and read years from now, once a quantum computer breaks the key exchange Nostr uses. This is the one part of the problem you can fix in advance, and there are two ways to do it.
Obelisk Bots: Nostr agents for groups, zaps, and ops
Obelisk-bots is the bot runtime for relay-only Obelisk groups: small Node scripts with their own Nostr keys that listen to NIP-29 group events, announce zaps, run tickers, and automate community operations without a backend.
Swap anything, trust nothing: the Obelisk four-piece stack
Obelisk is four small projects on one open protocol: chat, voice SFU, bot runtime, and relay. Any piece is replaceable, none is central.
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.
Bitcoin zaps in chat
Obelisk lets you send Bitcoin over Lightning directly from a chat message using NIP-57 zaps, paid by a wallet you connect with Nostr Wallet Connect (NIP-47) or by a WebLN browser extension. No custodian, no platform fee, no middleman. Just your wallet, the recipient's wallet, and a signed Nostr event.
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.
How Obelisk works
Obelisk is a web app with no backend of its own. It signs Nostr events with your key and sends them straight to your server, which is a NIP-29 relay, and to the other relays it needs. Here's what happens when you log in, send a message or join a group.
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.
What is Obelisk?
Obelisk is a Discord-style group chat client with no backend. There's no database, no Obelisk server. Your account is a Nostr keypair, your groups live on Nostr relays, and the app is just a frontend that signs and reads events.