All guides
#roadmap#nostr#nip-46#nip-44#voice

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.

3 min read
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

Where we are

The big migration is done. Obelisk used to be a hybrid app (Postgres database, Socket.io server, custom auth) with Nostr only for login. Today the database is gone, the auth service is gone, and the app is a frontend talking directly to NIP-29 relays. NIP-29 groups, encrypted DMs (NIP-04 + NIP-17), and Lightning zaps (NIP-57 + NIP-47) all work without any Obelisk-run infrastructure.

Most of what this page used to list as "next" has shipped since. Here's what's in the app today, and what's still ahead.

Shipped: NIP-46 signer-app login

Besides a NIP-07 browser extension or a pasted nsec, you can now log in with NIP-46 ("Nostr Connect" / bunker): your private key stays in a separate signer app (Amber, nsec.app, a hardware device or a remote service), and Obelisk asks it for signatures over a relay. Scan a QR code or paste a bunker link. On a phone, it's the way to log in without handing the browser your key. The login screen can also generate a brand-new key for you.

Shipped: NIP-44 v2 encryption

NIP-17 DMs are gift-wrapped and sealed with NIP-44 v2, the modern Nostr encryption standard: versioned, authenticated, with proper key derivation. NIP-17 is the default for every new conversation; NIP-04 stays available per conversation for people whose client still needs it. On top of that, a post-quantum seal is added whenever your signer and the other person both have post-quantum keys.

Shipped: voice channels

Voice is back, without the Socket.io server it used to need. Small rooms are WebRTC with signaling over Nostr events: browsers connect directly in a peer-to-peer mesh of up to four people. For bigger rooms, a channel admin makes the channel a big-room voice channel and picks a mediasoup SFU to route it, which can be one you host yourself. Both kinds do audio, camera and screen sharing, and DMs have one-to-one calls too.

Shipped: installable app (PWA)

Obelisk has a web app manifest and a service worker, so you can install it to your home screen from the browser menu, no app store needed. The service worker caches the app shell, and the last messages of each channel are kept on the device so a reload paints instantly. While the app is open, new DMs and mentions show up as system notifications.

Still ahead: static-export build

Today the app is built with next build and served by Node. The server part is small (security headers, the first-visit language redirect, link previews and the public note and profile pages), but it is still there, so Obelisk can't be dropped on a purely static host yet. Moving those pieces out of the way would give a build you can put on GitHub Pages, Cloudflare Pages, S3, IPFS, or any static host.

Status: planned. Some routes need adjustment first.

Still ahead: push notifications

Notifications work only while Obelisk is open in a tab. Web Push (notifications that arrive with the app closed) needs a relay-side dispatcher and is not built yet.

Status: planned.

What's not on the roadmap anymore

  • PostgreSQL. Gone.
  • Socket.io server. Gone. Voice signaling runs over Nostr instead.
  • A separate admin backend. The admin tools live in the app and publish NIP-29 events; the relay enforces them.
  • Web of Trust scoring service. Gone as a server: trust comes from the Nostr WoT extension and SDK in your browser, and each relay enforces its own admission.