Nostrfi
/Docs
Browse documentation
Owner: NostrfiLast reviewed: 2026-11-17

Changelog

How releases work

Nostrfi Relay releases follow semantic versioning. Each release is tagged v<version> and published on GitHub releases, with relay and dashboard images on the GitHub Container Registry and a Linux binary attached.

This page summarises each release for the people who run the relay. The full list of commits is in the release notes on GitHub. Before 1.0, a release may change configuration between versions, so read the notes before you upgrade.

0.3.0 (16 November 2026)

Release notes on GitHub

This release deletes stored ephemeral events on its first start, and refuses operator requests until the relay knows its own public address. Read Upgrading before you deploy it.

Administrators

  • Grant administrator rights to other pubkeys, so a team can run a relay without sharing the owner's key. The owner (moderation.admin_pubkey) uses the NIP-86 assignrole and unassignrole methods. The relay adds two methods of its own: listroleassignments and whoami.
  • Administrators can moderate and browse events. Role management and the configuration API stay owner only, and answer administrators with 403. See administrators.
  • Administrators can sign in to the dashboard. The dashboard asks the relay which role a key holds, so your signer now prompts twice at sign-in. Configuration is hidden from administrators. See admin dashboard.

Protocol

  • Ephemeral events are no longer stored. Kinds 20000–29999, such as presence heartbeats, are delivered to open subscriptions and never written to the database, as NIP-01 expects. A new metric, relay_events_ephemeral_total, counts them.
  • Kind 22242 sent as EVENT is refused. NIP-42 authentication events belong in AUTH messages. Before, they were stored and broadcast.

Security fixes

  • Operator signatures are bound to this relay. A NIP-98 signature must name this relay's origin, and each one is accepted once. Before, a signature a browser extension made for another website could be replayed at the relay (nostrfi/relay#60).
  • Administrator grants are kept consistent. A grant or revocation is completed even if the client disconnects mid-request. At start, the relay deletes any stored grant for the owner's own key, and warns about grants made by a former owner key.
  • Dashboard sessions end when they should. Signing out really ends the session, signing in again revokes the previous one, and restarting the dashboard ends every session. Revoking an administrator ends their dashboard access too.

Packaging

  • The prebuilt relay-linux-amd64 binary needs glibc 2.36 or newer, down from 2.43, so it runs on Debian 12 and Ubuntu 24.04.

Upgrading

  • Back up first. Migration 6 deletes every stored ephemeral event when 0.3.0 first starts. To keep them, take the backup with your current 0.2.0 binary, or copy db/relay.db while the relay is stopped. A backup taken with 0.3.0 runs the migration first. See backup and retention.
  • Set the relay's public address. The relay refuses every operator request, including dashboard sign-in, unless auth.relay_url or moderation.api_origin gives its origin. With the TLS overlay, set RELAY_URL=wss://your-domain in .env; it defaults to wss://localhost:8443. See moderation.
  • Remove NUXT_ADMIN_PUBKEY from the dashboard's environment. It is no longer read. The owner is moderation.admin_pubkey in the relay's config.yaml, as before.
  • Operators sign in again after the upgrade, because older sessions carry no role.

0.2.0 (12 November 2026)

Release notes on GitHub

Dashboard

  • Filter events by several tags at once, including multi-letter tags. The event browser explains how tag rows combine.
  • Relay status and uptime on the Overview, with a spinner while the page refreshes. See the admin dashboard.
  • The Metrics page has the same status card and refresh spinner as the Overview, so either page tells you at a glance whether the relay is up.

Fixes

  • NIP-42 authentication: the relay now answers every AUTH message with an OK, as the specification requires: true when authentication succeeds, and false with an invalid: or restricted: reason when it does not (this was a NOTICE before). Clients that wait for the reply, such as nak and go-nostr, no longer time out, so they can publish NIP-70 protected events. See protocol support.

Upgrading

  • No configuration changes.
  • The prebuilt relay-linux-amd64 binary attached to this release needs glibc 2.43 or newer. The container images are not affected. The fix is merged and ships in the next release.

0.1.0 (11 November 2026)

Release notes on GitHub

The first tagged release of Nostrfi Relay and its operator dashboard. Releases are now cut from a release PR, and the relay is built with Go 1.26.11 to clear standard-library security advisories.

Start with the quickstart, and read the current limitations before you deploy.