This edition covers developments through Wednesday 18 November 2026 at 16:00 UTC and is published retrospectively. Several projects put tighter limits on encrypted media and keys this week. Applesauce bounds attachment downloads, MDK changes recovery, device and media handling in source, and Keep Android changes how it trusts relay certificates. Clients and wallets, including Wisp and ZEUS, fix reliability problems. Hashtree releases browser read and indexing changes, while its paid blob retrieval exists only in source. Protocol experiments such as Scheduled Tasks and NAP-WEBRTC are still open proposals or branch-only work. The deep dive covers public zap goals and peer-to-peer orders.

Top stories

Sidecar

Sidecar is a browser side-panel Nostr client with a built-in signer. v1.17.1 adds one relay-backed library for bookmarks, highlights, web comments and reactions. It includes bookmark sets created in other clients: Sidecar reads kinds 10003, 30003 and 30001, uses the owner’s key to decrypt private entries over NIP-44 or NIP-04, and shows private entries as read-only. Web comments appear as kind 1111 reply trees. Users can add a custom client by pasting a sample note or profile URL. Sidecar parses the link, rebuilds it and saves the client only when the rebuilt link matches the original, and it removes relay hints from nprofile links. Much of this work was merged in #612 and #621. Because the library holds only what the queried relays return, it may not include a user’s complete history.

In v1.17.2, livestream chat can be read before an account is added. Writing actions are hidden, controls that need an account are disabled and the sign-up link opens Accounts. Locked panels still hide chat. Reply and mention names can now resolve from the target’s own relays. #627 separates approval of a single signature from a per-kind grant, which Sidecar offers after three requests of the same kind. Users can also choose a time-limited approval window, and sites that share an account get no standing grants. Choosing an account applies to that one signature and leaves the active account and the site pin unchanged. Wallet, deletion, authentication and list events remain excluded from grants.

Later merges to main, not yet tied to a release, add NIP-37 drafts and configurable profile search. With #635, a user can explicitly save a draft to private relays as a kind 31234 event encrypted to themself with NIP-44. Local autosave stays on the device. Sidecar lists relay drafts of kind 1 notes and replies alongside kind 1111 web-comment replies, ten at a time. Opening a relay draft preserves the current local draft. After a draft is posted or deleted, Sidecar makes a best-effort attempt to blank its relay copy, which is not guaranteed. NIP-42 authentication uses the account key. The change aims at cross-client compatibility, and the cited tests used a controlled relay and Chrome (commit).

#633 makes signed-profile search configurable through search relays, including relays from a kind 10007 list and an optional ranked Brainstorm relay. Sidecar verifies the signature on each returned profile and checks that its key is consistent. Queries send the typed text and do not include the user’s follow list or key. Brainstorm results leave out accounts that the service has not scored (commit).

Formstr nostr-docs

Formstr’s nostr-docs, an encrypted collaborative document editor built on Nostr, merged a sharing rework that separates the right to decrypt a document from permission to edit it (#82, #79). Restricted shares accept writes from the owner and invited editors. Older documents keep working through a legacy edit-key attestation, and open links let any link holder write. Signed presence updates with a mismatched identity or an invalid signature are rejected. Proofreading now parses content with an inert DOMParser before passing it to ProseMirror, where it previously used live innerHTML. This closes one injection path but does not show that the app is free of XSS. A smaller merged change, #80, adds a delete option to document cards.

Pull request #88, which builds on earlier work, replaces the Mammoth converter with a native OOXML adapter for DOCX files. Users can edit basic text, tables, images and page settings. Unsupported structures and the original package parts pass through unchanged. Complex and vertically merged tables, fields, footnotes and tracked changes cannot be edited. Header and footer edits are not written back, and edited runs keep only some of their formatting. Open proposal #86 links encrypted comments to their parents so replies can nest at any depth, and it adds tests for persisted replies. Because the parent relation sits inside the ciphertext, older clients show replies as separate comments. Resolution and counts apply at the root comment, and comment metadata is not fully private.

Vector

Vector, a private messaging app that hosts Concord communities, published v0.5.2-1 on 18 November as a prerelease, described as the first preview of v0.5.2. The preview carries hardened locked channels, which rely on scoped writer certificates, quieted read addresses and sealed history from before the lock. Commits ff610ae and 6027095 preserve the hash, ID and read epoch of sealed content and reseal history over an initial 10-minute window. They also reject backdated reactor or call authority and mark missing history pages as incomplete. The lock applies only to new readers. Other work adds an Add Reactions permission, guided community creation and raid detection. Raid detection examines the densest 15-minute burst of activity and distinguishes established participants from newcomers. Main-branch commits also speed up role key grants while keeping the messages surrounding a grant, and keep attachments from failed messages through retry and deletion.

Merged #101 adds a 60 ms playback buffer. Open, experimental #102 builds a GPUI client meant to match the existing Tauri app. It has no release, and neither parity nor performance has been demonstrated.

Wisp

Wisp, a Nostr client, merged media and payment-verification changes this week without a new release. #688 adds BUD-10 blossom: URIs: Wisp reads the file hash and server hints, tries the hinted servers and then the user’s configured servers, and checks the downloaded bytes against the hash before it uses the media URL. That check covers only Wisp’s own fetch, not a later independent fetch of the same URL. #697 also verifies any supplied sha256 against the fetched file. BUD-05 transformed media can omit that value.

For zaps, #687 confirms that a BOLT11 invoice commits to the expected amount and description. It also ties receipts more closely to the identity and context of the original zap request. Reading changes add article previews in feeds and profiles (#696), article sharing (#692), full note text in opened threads (#695), a wake lock during inline video (#669) and stable image heights (#691). Wisp now deletes superseded Drive backups and shows their status (#689), and it decodes entities in a single pass (#698).

White Noise

White Noise is an encrypted group messenger built on the Marmot protocol. Its developer merged work across its native apps and published Android release 2026.11.17 on 18 November. According to the developer’s release notes, that Android build adds in-app PDF and HTML readers, a two-pane chat layout on wide screens, sticker packs, configurable chat shortcuts, notification privacy options, audit log export and an update to MarmotKit 0.17.0. The notes also list improvements to custom emoji, dictation, media previews, attachment delivery and recovery, and they have not been checked against the package itself. On Android, #3835 places the chat list and conversation side by side on screens 840dp and wider. Drafts and scroll position survive window resizes, although the selected chat is not yet highlighted. With #3839, PDF and HTML attachments open inside the app. PDFs render in an isolated media process, and HTML is rebuilt from an allowlist with JavaScript and network access disabled. PDF search and text selection are not available.

On iOS, #1338 accepts video, audio and documents up to 512 MiB and images up to 50 MB. Attachments over 50 MB are not saved as drafts, and backgrounding the app or leaving the chat may stop an upload. A large-file check on a physical device is still pending. #1337 adds hold-to-dictate on iOS 26 and later and sends the transcribed text on release. It uses Apple’s on-device speech recognition and neither stores nor sends the audio.

On macOS, #1031 adds Save As and Show in Finder for each download. The author notes that testing in the sandboxed running app is incomplete. #990 adds multi-select with bulk archive, mute and leave. Before connecting to a NIP-46 remote signer, the Linux client now shows the exact permissions for review. It offers the pairing link only once its listener is ready and restores the vault session. Android #3825, iOS #1348 and macOS #1045 adopt MarmotKit 0.17.0. If some invitees cannot be added, the group is still created, everyone else is invited, and the app lists the skipped users. On macOS the update migrates the account schema from version 201 to 207, and this migration cannot be reversed. A known Android problem with receiving messages after a deletion predates these changes and is still unresolved.

ZEUS

ZEUS, a Lightning wallet that can serve Nostr Wallet Connect (NWC) requests, released stable v13.2.5 on 16 November after v13.2.5-rc1. The release stores a claim for each NWC request event ID per connection and rejects repeated deliveries before they reach a handler (#4410). It also adds payment_sent and payment_received notifications from NIP-47, the wallet RPC protocol behind NWC (#4347). The v13.2.4 to v13.2.5 comparison also includes pending-invoice reconciliation and fixes to the NWC relay and initialization lifecycle.

Related NWC work merged on master in the same period. This issue has not confirmed which of it is in v13.2.5. list_transactions reconciles pending make_invoice activities and lists unpaid or expired invoices according to its flags (#5610), and pending-payment refresh uses targeted lookupPayment calls on backends that support them (#4495). Overlapping service initializations join one in-flight operation (#5638). A superseded subscription can no longer become active, and concurrent subscribes on one connection join (#5646). A reset closes relay services after a bounded grace period for handlers still running (#5639). Wallet error replies keep their failure text and stay distinct from SDK transport errors (#5758). New custom NWC relays must use wss, except onion endpoints, which may use ws (#5323).

More fixes merged after the release and exist only in source. NIP-05 lookups, which map human-readable names to keys, now reject redirects (#5371) and go through Tor when Use Tor is enabled (#5321). An incomplete payment with an all-zero preimage no longer counts as proof of NWC settlement (#5166). Budget accounting now rounds NWC invoice amounts and fees up to whole sats, so a 1999 msat payment with a 500 msat fee consumes 3 sats of budget (#5336). The NIP-47 fees_paid field still reports the raw fee, but an amount built from an activity record now reports the rounded-up value. A rejected send may still have reached the node. In that case ZEUS checks the node’s payment list and keeps the budget reserved for a payment listed as in flight. A duplicate refusal from the node is handled separately and is not charged to the connection (#5159). NWC connection objects keep their identity across storage reloads, so current activity rows no longer stay pending after settlement (#5182).

The wallet also backs up its Cashu mint list to Nostr as a kind 30078 event. Failure of every relay is now distinct from a relay answering that no backup exists (#5370). ZEUS retries at the next initialization and suppresses empty-list writes and backups while that check is pending. The pending flag lives only in memory, so a mint added manually in the same session can prevent a later restore. A single relay that answers with nothing still counts as no backup.

Two draft proposals remain open. One would let users release an old pending pay_invoice budget hold while settlement reconciliation continues (#5768). The other would store the timestamp of the newest accepted request and reject older events outside a replay window (#5726).

Amber

Amber, an Android signer that keeps Nostr keys for other apps, published the 7.0.0-pre4 and 7.0.0-pre5 prereleases. Stable 7.0.0 has not been released, and these prereleases have not had a security audit. Pre4 adds an Amber CLI for NIP-46 signing from scripts and agents, packaged for Linux, macOS and Windows. Pre5 changes CLI pairing, status reporting and secret-store handling (#557). The CLI subscribes before it shows a pairing URI, and login - reads a bunker URI from standard input. While offline or pending, status returns a real failure code along with ok:false. The CLI also keeps using whichever secret-store backend was selected.

On Android, #565 adds nip44v3_encrypt, nip44v3_decrypt and sign_psbt to rate limiting. NIP-55 is the interface Android apps use to reach a signer, and the change limits floods of approval screens requested through it while leaving cryptography unchanged. #561 publishes the error reply for an unverified NIP-46 request once, while verified replies keep their retry behavior. Upgrade fixes restore accounts from legacy storage (#549), including installs from 3.3.0 or older, and keep the upgrade and account-discovery paths intact for offline-flavor application IDs (#550). Smaller commits send an Amber User-Agent from every HTTP client and pass context to the sensitive clipboard. Another commit makes the key-store marker private and deduplicates forwarded ephemeral events.

Fixes merged after pre5 change how Amber loads saved permissions. They are not in either prerelease, and no release or security audit covering them is established. #582 reloads saved application permissions for every NIP-55 request, so reusing a request ID cannot carry over a grant that has since been revoked. Loaded permissions are matched to the exact request object, and web callers still never load a shared null-package application. #579, including 316b4c8, applies the same per-request load to NIP-46 bunker requests.

Rejecting a browser request now sends rejected=true with its request ID and closes the request without recording a shared browser grant (#575). With #570, a request screen closes its own activity. #578 refuses a queued batch request whose saved application was revoked and does not recreate that application. Batch choices and removal now apply only to that batch, leaving unrelated open requests alone. e96ae9a keeps remembered durations for ordinary batch signing grants and limits relay-auth scope handling to kind 22242.

Applesauce

Applesauce is a set of TypeScript libraries for building Nostr clients. applesauce-extra@7.2.0 bounds attachment downloads. A file can be no larger than its declared size, plus the 16-byte AES-GCM authentication tag for encrypted files, and never larger than the configured maximum, which defaults to 100 MiB. A file without a valid declared size is held to that maximum. The library rejects oversized attachments before fetching them and can fall back to a mirror (#111). If a response declares a content length above the limit, its body is cancelled. Script-capable MIME types are returned as application/octet-stream unless an app explicitly allows them.

Other packages tighten event and connection handling. applesauce-core@7.1.2 runs an event store’s configured verification on deletion events before processing them. applesauce-wallet@7.1.1 filters deletion reads by the wallet owner. applesauce-relay@7.1.1 treats socket connection errors as retryable when reconnect is enabled. Separately, merged #119 makes Kehto DM decryption and napplet relay hints opt-in, and merged #109 lets inbox processing continue past malformed cache rows. The available release notes do not show that either change has shipped. Merged #121 updates the ratchet dependency.

Hashtree

Hashtree is a content-addressed storage system that publishes data over Nostr. Released CLI 0.4.5 and git helper 0.4.2 add name search through the social graph, with explicit publisher selection. They also add a login link shown only in the terminal and an option to publish release trees with 32-byte keys that older gateways can read. Suite-prefixed 33-byte keys remain the default.

TypeScript runtimes 0.5.42 through 0.5.48 change how browser apps read and index data. File reads keep byte order while running at most 16 concurrent store reads with up to 8 MiB of read-ahead. Concurrent callers asking for the same hash share one read. For followed-by-friends queries, the worker returns the viewer’s follows who follow the profile, and it recomputes follow distances after follow lists have been quiet for one second. Dexie 0.1.15 keeps a transactional byte count with size and access indexes, so quota and eviction checks do not load payloads. Runtime 0.5.47 adds opt-in browser indexes for signed relay events, which keep older history queryable and apply deletions and replacements across stores. The publication outbox stays durable. In 0.5.48 the worker reads signed graph snapshots and verifies their content hash before keeping preferences for each account.

Worker source committed after the runtime 0.5.49 release adds an opt-in graph bootstrap that did not ship in that release (df8b28f). With this option, an app can bundle a social graph receipt together with a verified snapshot. The bundled snapshot has limits on both its size in bytes and its number of users. Because the app already holds this verified snapshot, it can start from that graph. The worker then fetches a signed public update in the background and merges it with the current local state. Local edits made while that merge runs are not overwritten. A graph that came only from the package stays ephemeral, so the next visit still looks for a signed snapshot. Real local changes and accepted signed snapshots persist. In a separate change, the durable Nostr outbox now keeps full metadata for each pending delivery scope. It updates pending entries atomically inside serialized state updates. As a result, independent relay and source deliveries survive persistence and reload (9d4af0e, 2d49ef4). This issue does not attribute either change to a release.

Source written after CLI 0.4.5 lets htree get and cat open link-visible encrypted trees, and it removes the link secret before any discovery or HTTP request. LMDB stores refuse lock files created under a different C library, and relay connections race IPv6 and IPv4 through the WebSocket handshake. Private local HTTP routes now reject proxied requests that carry forwarding markers. This only works if the proxy adds such a marker.

Paid Cashu blob retrieval also exists only in source and is off unless configured. A configured client can move to the paid cost tier once all free sources have finished without the blob, and since the defaults change that includes sources that failed or timed out. The buyer saves the payment intent and token so a payment can be recovered by its stable wallet payment ID, and it records provider shortfalls. This does not make payment and delivery atomic, and users must still trust the mint and the provider. Providers serve hashtree.paid-blob/1 on FIPS port 39020. They can also enable a custom POST /paid-blob HTTP endpoint, which accepts requests of up to 64 KiB with sixteen concurrent slots and is not generic HTTP 402 payment. Adding an explicit paid section to the configuration turns on those defaults, including a 1000-sat lifetime spending limit for the buying client. Provider ledgers write credits to disk before replying, but charges can take up to one second to be written.

Marmot Development Kit (MDK)

MDK is the toolkit for building Marmot apps, which run end-to-end encrypted MLS group chats over Nostr. Stable MDK 0.16, released on 12 November, brings shared persistent NIP-46 signing to Swift, Kotlin and C. Users must approve the exact permissions requested, and sessions resume after a restart without host callbacks. Its OpenMLS update includes fixes that the release’s security notes describe for two bugs: nested extensions that could abort the process, and rejected private messages that could advance a sender ratchet. Existing groups still interoperate, and Hermes attachment staging and gateway files are now private.

Stable MDK 0.17 followed on 15 November. It creates groups with and invites the recipients who are available and returns an ordered result for each member. If no recipient is available, MDK creates neither a group nor a commit. Agent-control operations still succeed or fail as a whole. Published read snapshots let account and group reads skip the queue behind sends and catch-up, although hydrating a group for the first time can still wait. The release notes also list four concurrent attachment downloads, which are prioritized by visibility and pause when disk space is low. Missing-history notices appear only with evidence, and failed sends can be discarded locally. Media gains reply context, and so do polls and stickers; sticker packs also get offline share links. Valid bare event references now parse, and security dependencies are updated.

Hosts upgrading to 0.17 must ship one matching set of bindings, native libraries and headers. Its account database migration from version 201 to 207 cannot be reversed. Upload of whole-file v4 audits is removed, so hosts use v5 and must initialize its source on every launch. The MDK, MarmotKit and C tags are stable, while the WN Agent v0.16 and v0.17 tags are still marked as prereleases (0.17 release).

Several changes merged after the stable releases. Commit recovery reads the exact pending event back after ten minutes, and own echoes can also confirm it. Pending and stuck status shows which changes are blocked, and durable not-delivered outcomes remain available after the originating call returns. MDK abandons a commit only when it knows the commit reached no relay; a commit that may have been exposed stays pending. With #3531, a locally authored commit, including one stranded in the database, enters convergence only after its publication is confirmed. A rename that relays refused can therefore no longer advance the device’s own epoch and lose a confirmed retry. Queued sends keep their prepared event across retries and restarts, although sends stored by older versions can still duplicate once. When host-safety checks refuse every relay, MDK returns a typed NoUsableRelay error (#3515). After startup or reconnect, published-state reads now hydrate groups before responding, and restored status is published before watchers are notified. This fixes false delivery status and groups stuck in Discovering.

Merged device build changes remove compile-time flags so every build can support device linking, rosters and backups. #3519 has since merged and turns device groups on by default in Rust, the binding constructors and the CLI. Rust hosts can still disable them, while the bindings have no off switch. Every process that opens the same data root, extensions included, must run this version or newer. These device groups are separate from the already released group membership across a user’s devices. Related merged fixes restore KeyPackage rotation and avoid both idle writer transactions and empty-database creation. Another merged fix, with migration 0211, will remember slots that were linked and then removed after the roster removal record expires.

#3543 implements the post-link chat inventory from Marmot PR #511. It adds encrypted chat inventories and per-device snapshots of the chats a new device still has to join, and it resumes after a restart or a late Welcome. An incomplete inventory counts as unknown. The change merged on November 18 after the nightly pin described below, and no client UI for it is shown.

For messages, editable NIP-22 replies recognize kind 1111 with a numeric lowercase k tag and keep images and author edits. Large draft attachments are staged as encrypted files. Native hosts can identify tombstones from a losing branch through raw-message invalidation and remove a single reaction through exact-emoji removal. The 0.17 known-issues list still includes the loss of photos from old epochs. Sticker and emoji reads combine configured and account relays, verify copies before deduplicating them and link to the relays that served them, while publication still goes only to account relays. Failed refreshes keep installed images, and revisions are deduplicated before the 60-set limit applies. The attachment-removal journal has also merged. It retains 4,096 records and gives native hosts durable cache eviction through a restartable cursor, with explicit reset and full reconciliation. Historical records do not let hosts read attachment bodies.

When an imported relay list gives no clear answer, onboarding repair offers edits and default additions with explicit risk and freshness checks. Removal advice names relays shown to be unusable for their role. Most idle jobs now wake per account and run on deadlines, and with due-time scheduling merged, session maintenance does as well. Device-group passes, now on by default, still retry every 15 seconds, while an idle account with device groups off rechecks about every ten minutes. Epoch-gap recovery gives its visits durable end times and bounds passive polling, so relays that respond with nothing no longer cause continuous sweeps. Fresh evidence reopens the work, and polling for ordinary message loss is left to a follow-up. Battery impact has not been measured. For invitations to whichever recipients are available, recipient discovery reserves a deadline for each lookup stage, so early reads can no longer use up the whole 50 seconds. Atomic invitations are unchanged.

Welcome delivery changed in two places. Publication eligibility pauses queued attempts when their native branch loses. Welcome deduplication marks content as processed only after the user completes a join or explicitly declines. A refused wrapper therefore no longer blocks a later honest delivery of the same bytes. Markers already set the old way remain until the ring evicts them or a fresh invite arrives. Destructive sign-out now reports a queued Leave in group_leave_failures and no longer treats the departure as complete. Cleanup still proceeds and may discard that Leave, so a remote departure is not guaranteed. A fix for OpenClaw tool registration and Doctor repairs registration and upgrade failures in the Marmot plugin and is intended for 0.18. Terminal reply context remains an open proposal. Under that proposal, the replied-to snapshot would pass as untrusted prompt data across retries. Command and working-directory routing would stay unchanged.

The 0.18 nightlies from 17 November are pinned to a2d3486acc7d. They include #3476, #3467 and #3435 and exclude #3508, #3518 and #3520. The WN Agent nightly of 18 November is a testing-only prerelease pinned to 0ad3c61088e1. It includes #3519, #3495 and #3361 and excludes everything merged later on 18 November, including #3543, #3531 and #3533. It provides no installers, expires after 30 days and does not support downgrading. These are test builds, not a stable 0.18 release.

Zap Cooking

Zap Cooking, a Nostr recipe-sharing client, merged live streaming in source. The work adds NIP-53 live-activity discovery, playback, chat and zaps, Go live hosting and staged host approval and moderation. After the final chat switch, chat messages are kind 1311 events with an a tag naming 30311:<host>:<session id> and a p tag for the host, so chat works without a public announcement note. Readers still accept kind 1 replies to an existing note. Verified zap totals combine receipts for the note and the session address and deduplicate them by invoice payment hash. Each receipt and its embedded zap request must name the same target and host. The author’s browser tests of chat and zaps used a local stand-in provider, so no run of those features against real wallets and public relays has been established.

Other merged changes add NIP-49 encrypted-key login, which decrypts an ncryptsec with its password before the existing login flow. They also add address-scoped reactions for hosts and viewers with serialized signer requests, and a layout that puts saved streams and a zap goal in the player.

Later source changes make sessions easier to find and end. Recognition and deduplication now use the 30311:<host>:<session id> address and no longer rely on the streaming URL. An naddr lookup checks the session host on the server before redirecting. Announcements on kind 30311 events carry a chat and zap relay list that leaves out purplepag.es (#1010). Watch links go into the summary, r and alt tags. The host also signs a pinned kind 1311 chat message with the link. That message is repeated periodically, but only for signers fast enough to keep up (#1011). A stream can still be marked as ended if the host’s page is closed. For that case, the host pre-signs an ended kind 30311 copy. The server holds and validates the copy, then publishes it when the stream ends, so the event becomes public only after the end (#1012). Publication is retried through a periodic server sweep. The pre-signed end time can be up to 30 minutes early. For a slow signer, the copy covers only the first 30 minutes. A normal End now publishes a fresh ended event with an accurate time right away, alongside the server request. If no relay accepts it or the attempt times out, it retries after two seconds and then after five seconds. It asks the signer only once (#1013).

For #1012 and #1013, the author reports reading the events back from public relays in a preview and seeing the stream shown as ended in Primal and zap.stream. These are the author’s own checks, not independent verification. No release or deployment has been established for any of this work.

Tagged releases

Monostr

Monostr, an Android Nostr client, added polls in v0.38.0. Polls offer two to four choices and run from five minutes to seven days. Following the NIP-88 format, they are published as kind 1068 events with option, polltype, endsAt and relay tags, and votes are kind 1018 events with response tags. Screen readers announce progress, votes and errors. v0.39.0 adds a switch for using relay hints and warnings for misleading links. It also hashes the sender pubkey and a nonce into tip payment IDs. v0.39.1 applies the relay-hint setting to both fetching from and publishing to a poll’s named relays. Link prompts can still ask when “Always open” is selected, and search results now show likes, reposts and replies. Users can mark a tip as arrived without a receipt on their relays, and the wallet opens separately. Interoperability with other poll clients has not been tested independently.

Snort

Snort, a web Nostr client, released v0.5.6 after a v0.5.5 tag without release notes. For NIP-46 remote signers, Snort now sends NIP-44 encryption and decryption as RPC requests to the signer, replacing methods that had not been implemented. It also stores the remote signer’s pubkey in the session and accepts bunker connection responses that echo the secret, which fixes a pairing failure with some signers. NIP-45 COUNT merges HyperLogLog registers into approximate estimates. When relays return no HyperLogLog data, Snort reports the largest single relay count, which is not a deduplicated total. Messages gains chat search, previews of the last message and empty states. Account switching remembers the active account across reloads and saves state when switching. It refuses duplicate pubkeys and falls back to another account when one is removed. Add Account is now always available.

NosTube

NosTube, a Nostr video site with shorts and live streams, shipped releases through v0.2.82. Live streams display a kind 9041 zap goal: the stream’s explicit goal if one is set, otherwise the host’s newest open goal. On phones, v0.2.82 moves that goal into the scrolling stream header. Profile goals arrived in v0.2.75 and were removed in v0.2.81, server-instance builds omit goals entirely, and no interface exists for creating them. The goal hook fetches receipts through the goal’s relay hints. Receipts are then checked by the shared goal code against the author’s LNURL, with duplicate invoices removed and receipts after the closing time dropped. A displayed total may therefore miss receipts held only on other relays.

According to the changelog, chat mentions now become nostr:npub references with p tags, and custom emotes carry emoji tags. Version 0.2.77 lets viewers turn off the one-video-per-creator-per-day grouping, remembered per browser across home, the followed-creators shelf and subscriptions. Linked shorts resolve from the author’s relays since v0.2.74, and v0.2.82 gives mobile chat more space and device-specific appearance defaults.

Commits on main after v0.2.82, listed under Unreleased in the changelog, rework creator uploads. With 47de7a9, NosTube uploads each file to one primary Blossom server and then sends BUD-04 mirror requests asking the other servers to copy it. Servers without a mirror endpoint get a direct upload. If the primary fails, the next server takes over. NosTube caches each server’s capabilities for 30 days, including its speed and size limit. A mirror timeout or server error counts as a retryable failure because the copy may still complete.

b47435f lets the transcode worker stream its output to the browser’s origin private file system (OPFS) when that is supported and enough quota is available, and it falls back to the previous in-memory output otherwise. This reduces output buffering, though it does not show that every device can transcode arbitrarily large files. Output from abandoned jobs is cleaned up after one hour. 0beff0f puts upload details and a live preview with a checklist on the same page as publishing, and a remembered Show all options setting reveals relay and event preview controls.

eHagaki

eHagaki, a web client for writing and posting Nostr notes, released v1.33.0 on 17 November with in-app notifications for replies, reactions, reposts and mentions, including unread indicators and per-notification actions. It does not use operating-system push. Rendering keeps unchanged record and group identities, caches per-card work and batches repository writes (#551). In builds without native WebP support, the WASM WebP encoder runs in a module Worker so the editor stays responsive, with abort and main-thread fallback paths retained (#531).

A saved NIP-46 session is restored without waiting for the remote signer (#550), but eHagaki still checks the live identity before signing. An offline signer no longer switches accounts silently, and an identity mismatch drops the app to guest mode while keeping saved data. Saved logins also restore during history migration (#553). Merged authentication work orders the steps that save an nsec and commit the account, clears replaced credentials and in-memory keys, validates extension identities and rejects stale NIP-07 login responses (#529). Cached history listings are cleared on logout and when a failed account switch falls back to guest (#501).

History fixes keep a second opened reply target from leaving the first stuck while loading (#544), autoload older history after the listing window shifts (#535) and let JSONL export finish without a PrematureCommitError (#534). Realtime waiting queues for reactions and replies are capped at 32 events beyond the active item. That cap limits resource use, but a new event arriving at capacity can be dropped until it is received again (#502). Pasting an image no longer also inserts its HTML URL (#412). Pasted videos go through normal uploads, and unsupported files are rejected (#503). Ctrl or Cmd+Enter cannot publish text while an IME composition is unfinished (#498).

Nostr WoT extension

Nostr WoT, a browser extension for Nostr web-of-trust data that also handles signing and a Lightning wallet, released v0.8.24 with #59. After a credential rotation, the extension reconnects the hosted wallet using an account signature and a fingerprint of the saved wallet key. If an outgoing payment is in flight, recovery waits and does not replay that payment. A payment with no definitive reply stays in an unknown state. A later commit adds an experimental local NIP-46 transport, described in the design notes. It carries NIP-44 encrypted kind 24133 event frames over paired Wi-Fi or Bluetooth after a profile-bound handshake. That commit came after v0.8.25 and is not in any release. The phone must advertise and implement nip46-event, and an ordinary relay bunker needs an adapter. Legacy offers keep their old encoding. The transport does not fall back to relays and does not replay after a disconnect.

The server side of pairing is in the companion nostr-wot SDK. #30 keeps the same client URI after a brief subscription closure. Its changelog records that repeat delivery of the ephemeral pairing approval now requires an acknowledgement and is capped. #34 shares normalized relay connections and backoff across identities, enforces a global relay limit and closes failed handshakes. Monotonic generation numbers keep it in sync without disconnecting unrelated clients. Source prepares version 1.2.0 of the identity package, but no release has been supplied.

Mail by Form*

Mail by Form*, Formstr’s email client that delivers mail over Nostr, released v0.5.0 (changes). Large incoming mail from the bridge now arrives as ordered NIP-59 gift wraps, and the chunk metadata stays inside the encrypted rumor. At least one relay must accept each chunk, and the reader shows whichever parts have arrived. The client cannot yet split outgoing mail into chunks for reassembly. Incoming attachments are encrypted and uploaded to the recipient’s Blossom servers, with fallback servers and Formstr Drive links. The release also adds folder and label rules. Replies default to the address the mail was delivered to as the From address. If that mailbox is unavailable, the client asks the user to choose.

Codr

Codr, published as HERDR White Noise Remote, lets users answer OpenCode sessions through encrypted White Noise chats. Version 0.11.2 (#23) handles OpenCode V2 multipart questions one part at a time. Replying 1 or 2 to a permission request applies only to that exact session and request, and the user must confirm again if a pending request changes. Persistent and multiselect approvals are available only in the terminal. Messages wait in a durable queue with a bound on its size. The /recent command lists them oldest first.

Merged on the main branch, #25 delivers replies natively to OpenCode V2. Codr saves the message ID before submitting over an authenticated loopback connection. When an acknowledgement is uncertain, it reconciles state without repeating the uncertain POST or falling back to terminal input. The change also sets an MDK 0.17 storage-cohort boundary that refuses routine automatic migration. After an immutable tag build failed, the still-open #27 fixes an x64 musl startup crash, so no working stable 0.12.0 binary has been confirmed.

ngit

ngit, a command-line tool for Git collaboration over Nostr, released v3.1.0. Its installer retries Blossom mirrors and a versioned GitHub mirror, and it checks the signed archive hash before extraction. Pull requests whose changes have already landed are marked as applied without touching Git. Merges are refused when the branch is behind or has diverged from the default branch, and a closing reference must directly follow its verb. Version-matched agent skills for command help can be installed for one user or for the whole system (9cc4420, ca95d85, da0e012, e539194). The related ngit-flow tool is a separate early Rust CLI that depends on ngit. Alongside backup recovery and passive mirror review, it packages Nostr-first Git verification, which runs only on Linux for now.

NoorNote

NoorNote, a Nostr client, released versions 1.9.11 through 1.9.15. Some release notes repeat across versions. Replies in NIP-17 direct messages can now quote the original message and jump back to it. Cached content appears on first paint, and notes and threads resolve more reliably when opened cold or from a deep link (v1.9.12, v1.9.13). In 1.9.15, feed pagination uses a cursor in place of an initial time window. It requests more events than it needs, rechecks in the background after ten seconds and refills short pages.

Later source changes, which are not part of 1.9.15 (ea2892e, 3273b41, 02259e5), keep cross-device bookmark read markers active in both the classic and Focus interfaces. Profile sections now load only when they are opened. In the Focus interface, tabs and addon objects become deep-linked and user and hashtag searches get their own links, while the media composer can now publish images. The Electron app drops a bare custom user agent, which the author says caused sign-in walls on embedded YouTube videos.

nsite-clay

nsite-clay, a tool for agent-published encrypted pages on Nostr and Blossom, released 0.3.32. Signed-in readers can now comment on those pages and view source and page diffs. When a concurrent save is refused, the edit stays in the tab and can be retried after a reload. 0.3.34 fixes a hang during Amber approval by dropping an unanswered switch_relays request and suggests signer relays that the app can reach.

Source that prepares 0.4.0 is still in development, and no 0.4.0 release has been confirmed. Replaced encrypted page blobs are kept for at least two days. They are deleted only after every publication relay and the gateway confirm the replacement, which stops stale gateways from resolving deleted blobs into 502 errors. Uploads are read back and verified before a new page is announced. Multiple pages can share one site through an optional workspace, and each page gets its own private link. Existing standalone pages are unchanged. In a separate commit, the newer-version Reload checks for the expected content hash. For ordinary pages, it waits until the gateway serves a matching hash. Encrypted sealed pages fetch and verify the newer shell directly from Blossom or session storage and skip the gateway wait, so a stale gateway copy is not reloaded, unless a runtime they require is unavailable at the gateway.

Haven

Haven, an app for sharing location privately within encrypted circles, released v0.1.14 and v0.1.15 with fixes to relays, profiles and onboarding. PR #19 seeds relays and waits for them to acknowledge the KeyPackage and relay lists before showing the onboarding QR code. It also distinguishes an incomplete lookup from “not found” and sends public relay lists only to lookup relays. PR #15 republishes an existing kind 0 profile to relays that lack it and limits member profile fetches to two relays. It also shows the name and photo when a user types an npub. PR #18 fixes and bounds iOS background hangs inside the app process, though what triggers them in real use is not yet established. Circles now survive when the Android app resumes (PR #11). With PR #17, repair warnings follow observed foreground time and Android fetches peers after a successful publish. The battery cost of this has not been measured. PR #12 fixes relay-settings loading, and PR #10 changes how map recentering interacts with touch gestures. v0.1.15 also repairs Android startup. Underlying release work sits in the v0.1.13 comparison. It includes an internal location event kind 25442, usernames and cached recommendations, MDK 0.10.4 and per-circle location relay pools. Background publishing, stream restarts, onboarding changes and map markers are also part of it.

Open draft PR #13 proposes a mesh transport, switched off behind a HAVEN_MESH flag. The draft pairs a Rust engine that has no I/O of its own with a Flutter bridge and controls. Pure-Kotlin radio decision logic handles carrying opaque encrypted location data alongside Nostr. The draft has no Android radio adapter or manifest entries. A native binding and iOS support are also missing, and the code has not been tested on real radios.

Bray

Bray, a Nostr identity and relay toolkit with a command-line interface, an SDK and an MCP server, published releases 3.12.0 through 3.15.0 (full comparison). With PR #173, an owner can wrap an existing raw account key from the CLI or SDK and recover it later. Recovery needs both the master root and the encrypted file. It keeps the original npub and its provenance and requires explicit account selection. The imported key gets no derivation proof and no extra MCP authority. No external security review or physical recovery test of the wrapping feature has been published.

Relay handling changed too. Each persona now gets its own relay and AUTH pool (PR #165), and COUNT requests go through the proxy and that pool (PR #164). Fixes cover the handling of relay refusals, AUTH and false success reports (PR #161, PR #163), resubscription (PR #166) and error reporting (PR #168). PR #171 and PR #172 keep AUTH state alive across the daemon and in-flight requests.

GRAIN

GRAIN is a Nostr relay. In version 0.8.2, the relay sends OK only after an event is committed to storage, and a write that is not confirmed within ten seconds fails (#114). It also reassembles fragmented WebSocket messages (#111). The owner set in GRAIN_OWNER_PUBKEY now survives metadata reloads and writes (#112). Previously, an admin save could clear that owner from memory, after which later admin calls were rejected and the setup claim reopened. The release also updates the project’s branding (#113).

Goblin

Goblin, a wallet that exchanges payment messages as Nostr gift wraps, fixed a recovery gap. Before the fix, a gift wrap that arrived while the wallet was closed could fail to parse and still be recorded as processed. The entry guard is now checked apart from the parsing and lookup step, and dispatch has its own check. Such gift wraps stay unprocessed, so the wallet can recover the payment message the next time it opens. Build 172, published on 16 November, is a prerelease until the owner qualifies on-chain sending and receiving.

legends-buzz

legends-buzz, an operator toolkit for Buzz that includes Nostr relay diagnostics, released v0.1.1 on 11 November. Before connecting, its relay probes over HTTP and WebSocket validate their input and resolve the target to a pinned IP. The probes also ignore ambient proxy settings. Attachment inspection gets bounds for XML and ZIP content. Tests for the pinned transports and validation are in the implementing commit. This release hardens one operator tool and does not certify the safety of Buzz or of any relay.

Buzzr

Buzzr, a terminal client for Buzz, now checks each incoming event’s ID and signature before parsing it and drops forged events. New tests feed it forged input. Local agents that run through the client accept mentions only from their owner.

Nostream

Nostream, a TypeScript Nostr relay, released 3.16.0 with paid peering. Under #1088, configured peers request signed kind 402 BOLT11 invoices over an authenticated connection. Until a peer pays, the relay refuses its feed REQ, COUNT and NIP-77 negentropy sync requests, and the existing payment processor handles settlement. Peering charges go into a billing ledger. #1089 renews invoices, rechecks pending settlement before access lapses, closes sockets for lapsed peers and rechecks NEG-MSG access. Events and sync state are kept so a peer can resume later, and the admin interface shows billing status. The release does not include automatic payment by buying peers.

The same release also hardens administration. Admin logout revokes a random session ID in Redis until the session expires. Every admin request checks for that revocation, and if Redis cannot be read, the token is refused. A failed revocation returns 500 and still clears the cookie. Existing admins must sign in again after upgrading. Debug logs for rate limiting, WebSocket and payment callbacks now redact credential-bearing headers, but older logs are not changed. Settings-file writers are serialized with refreshed owner locks, hostname checks, process-start checks and async writer lifetimes. A worker started from the legacy settings.json also watches settings.yaml, so YAML writes take effect, including removal of an admin allowlist entry. The earlier 3.15.3 release shipped #1092. With that change, paying for a cheaper plan keeps a more expensive plan that is already running and credits proportional time.

The separate Rust rewrite gained a NIP-50 search term index with fixture parity and shared read and count predicates. It also gained a PostgreSQL-to-LMDB migration tool with resume, verification and throughput reporting. The tool leaves the source database read-only and keeps tombstones and expired rows. Its target checks now pin handles, verify identity after LMDB opens and reject unsafe ancestor ownership (#1161).

Deletion handling in the rewrite was tightened as well. #1164 deduplicates deletion e IDs and refuses a request with more than 100 distinct IDs before deleting or storing anything. Imported kind 5 requests now follow the live relay’s author-owned a-address deletion rules and whole-request caps (#1165). #1166 ends search-term index keys with a null separator and rebuilds the index as version 2, so an exact-term lookup no longer scans longer terms that share its prefix. All of this is development on rewrite/main, not yet integrated into main. None of it is part of 3.16.0 or any published package, and migration acceptance has not been verified.

Two source commits add buyer-side groundwork. be2aba4 adds buyer invoice ledger and budget primitives, and f84d891 bounds BOLT11 input and hardens budget rows. Neither has a verified merge or integration, and together they do not establish full invoice processing or automatic payment by buying peers.

PsstPsst

PsstPsst is an encrypted messenger that works over Nostr and Bluetooth. Version 26.11.2 encodes its Blossom authorization token as UTF-8 unpadded Base64URL for both primary uploads and mirrors. If a server responds with 400 or 401, the client retries with the old encoding a limited number of times. The release also fixes where the keyboard and menus appear on Android.

Cordn

Cordn, a Nostr messaging web app, released v0.7.0 on 13 November. It imports published Nostr emoji lists and packs, so custom emoji defined in other clients work in Cordn. It also adds local petnames that each account keeps for its own contacts. The v0.6.1 to v0.7.0 comparison also includes notification previews, join-state handling and source embeds, which landed at various points after the 30 October release.

In the separate cordn repository, merged PR #13 adds a draft calendar application specification with no code. It places NIP-52-shaped kinds 31922, 31923 and 31925 inside sealed MLS group payloads as unsigned inner envelopes authenticated by the MLS sender. Each group has one calendar, with addressable revisions, cancellation by the author and the latest RSVP kept per account. The coordinator cannot see the content, and the draft defines no kind 31924 calendar-list object. These events are not public NIP-52 events, and no calendar interface has been released.

Opal

Opal, a Nostr signing daemon and library that applies per-app approval rules, released v0.3.15. Approvals for sensitive signing can last longer than one hour only after the user verifies their passphrase. Saved rules are now scoped to the requesting app and event kind, and both the daemon and the library enforce that scope.

Feather

Feather, a Nostr client, added attestations across versions 1.15 and 1.16. Kind 31871 attestations render as native cards showing the stated status, validity dates, referenced note and explanation. Version 1.16.0 also adds automatically discovered attestation feeds to home and profile views, querying kind 31871 events from the account and followed authors and deduplicating them by issuer and d tag. The displayed status is the issuer’s own assertion, and Feather does not verify it. Kind 31871 has no standardized NIP number. In version 1.16.1, an explicit refresh sends a new request even when filters are unchanged.

Feather 1.17.0, published on 18 November, renders tagged custom emoji such as :PepeHands: inline in notes, replies and quoted notes, according to its release notes. Shortcodes are kept when text is copied or when an image cannot load. This release also avoids a dialog layout crash when choosing a custom zap amount or message on a note with zap splits, and when opening repost and matching-hashtag lists.

Nexpense

Nexpense, a shared-expense ledger on Nostr, released v1.0.0. This week’s source work improves settings and member management for encrypted shared groups and makes the app’s relay storage more durable. Nexpense records who owes whom but does not move funds.

Nowstr

Nowstr, a browser extension that publishes the music you are playing as a Nostr status, released extension v0.7.1. Its fix corrects Spotify artist detection and stops looping artwork videos from being treated as the playing media, so music-status publishing works again.

KithMoot

KithMoot is a private group chat and calling app with browser, desktop and Android clients. A new People inbox from merged PR #845, first released in desktop 0.1.168, receives encrypted Nostr messages and requests from new senders through the account’s signed inbox relay list. Users can edit that relay list or opt out on each device, and can answer over Nostr or invite the contact to private node chat. PR #847, released in desktop 0.1.169, lets a remote NIP-46 signer authenticate to inbox relays and send approved messages and replies. Desktop 0.1.170 adds PR #848, which lists unread conversations first and caches known profile pictures within the user’s privacy controls. PR #849 publishes feed and download metadata for Android 0.6.166.

Ordinary rooms can also use Wok, the members-only Nostr relay behind KithMoot rooms, as a standalone relay. Merged PR #837 lets the browser and PWA client use a standalone WSS Wok relay alongside Bothy. Saving the relay only makes it available. Each room has to be switched on separately with keeper-signed scoped grants. These rooms carry text and presence only, without calls, media, invitations, rekeys or protected MLS. A Wok source change binds each grant to a relay URL, guest, room, allowed kinds and expiry. With the ordinary profile, a guest can read kinds 1460, 1462 and 20461 and write kinds 1460 and 20461. A separate Wok change gives REQ its own read-permit budget, so incoming EVENT messages no longer use up those permits. Wok has no published release with these changes. Android 0.6.161 connects account-owned private chat to standalone Wok with stored room-scoped consent. It requests the expected event kind, event id and room d tag and keeps discovering the live roster.

For operators, a new forgesworn-node bundle runs operator-owned Spry pairing and TURN, a private Wok relay and Wildbloom encrypted blob storage without Archipelago. It has not been tested on a public host, with TURN across networks or on physical devices.

On desktop, Desktop 0.1.160 includes PR #827. This change strips attachment metadata on the device before encryption and upload. Malformed or unsupported files are not sent, and originals stay on the device. The cleaner can leave visible content in place, along with filenames and auxiliary codec data. The optional public IP and location lookup uses ipwho.is. Android has no cleaner, and neither Safari nor physical devices have been tested. Desktop 0.1.163 adds a drawing overlay from PR #835. The overlay follows the shared window or screen and disappears when sharing or the call ends. On Wayland it relies on optional compositor companions that have to be attached explicitly. Physical Windows machines, mixed-DPI setups, modern compositors and mixed clients are still untested. Call changes in PR #840 and PR #842 keep a camera visible when readings briefly go missing and avoid resets while frames are still advancing. They also show observed connection routes and a waveform for each person. Acceptance with mixed clients on physical devices remains unproven.

Merged PR #832 adds “Save to my Wildbloom”. It copies the exact verified encrypted envelope to a non-public Blossom server the user chooses, under the current identity. The copy contains no plaintext, uses no new key and creates no new kind 1063 event. Because the room key still opens it and copies saved by recipients sit outside the room’s cleanup, revoking a file does not reach them.

My Signet

My Signet, a Nostr identity and Nostr Connect signing app, published v0.26.0 through v0.29.0 (comparison). v0.26.0 adds personas held by Heartwood and a direct Nostr Connect handoff, after which the phone can be closed. v0.28 and v0.29 add a preview of encrypted recovery for imported accounts. A collection holds up to 100 imported identities, and users choose which ones to restore. Recovery needs both the recovery words and the encrypted file, because the words cannot regenerate imported nsecs that were never derived from them. The Wildbloom receipt has to be stored separately, and the feature is awaiting external security review.

In the related Heartwood repository, PR #26 merged a Rust reference codec with a shared test vector. Its wrap_nsec and unwrap_nsec functions authenticate a raw-key record to the tree root and check the public key and an optional npub. No Heartwood binary uses the codec yet, and the firmware is unchanged.

Citrine

Citrine, an Android app that runs a Nostr relay on the phone, shipped five releases that limit memory and connection use. For memory, v3.2.3 bounds tag loading with cancellation and recovers a stuck Download events action. v3.2.4 keeps contact lists only from followed authors and deletes copies it had already stored. It also exports large backups without loading every event ID, and an out-of-memory request now fails without stopping the relay. v3.2.5 caps connections at 50, adds frame and queue limits and pages the stranger-list cleanup so it can resume. It also adds editable crash reports that can be signed or anonymous. v3.2.6 suspends outbound queues under backpressure, allows one historical subscription stream per connection and retries an interrupted aggregator refresh within 30 seconds. The full comparison also shows the incoming queue reduced to 16.

v3.2.7, published November 18, pages history queries as event IDs and loads event content in bounded chunks (#189). Four app-wide permits cap how many history chunks load at once, and an outgoing queue must have room before another chunk loads. Each chunk has a content budget of 1,048,576 characters, though a single oversized event can exceed it. Outbound relay requests now send Citrine’s own User-Agent in place of Amethyst’s. Benchmarks in #189 come from the maintainer on one device and database and have not been independently reproduced. None of the five releases promises a fixed memory ceiling in every case or freedom from crashes.

Ambulando

Ambulando’s Android app tightened Shared FIPS access in shared workspaces in 0.9.26 (v0.9.18 to v0.9.26 comparison). Access now requires an explicitly enrolled Nostr Browser provider and native approval from the user. The code treats Shared FIPS separately from NIP-98 HTTP authentication and binds each request to the user’s current consent. Without native approval, the app does not fall back to HTTPS automatically. This behavior has been checked only in source; it has not been tested on physical devices or audited.

Canopy

Canopy, an Android app from Humans Institute, now edits public Blossom server lists (v0.2.0 to v0.2.3 comparison). Version 0.2.1 lets users read, edit, reorder and publish their BUD-03 kind 10063 list through the Amber signer, kept separate from local per-app overrides. Version 0.2.2 shows persistent warnings when relays return incomplete results. When some relays fail, the editor keeps the newest verified cached list and does not replace an unknown state with an empty list. It asks for confirmation after an incomplete read and checks again around signing.

Nostr Navigator

Nostr Navigator, an alpha web browser with built-in Nostr features, published Android v0.32.1 and Android 0.32.4. The v0.32.1 work gives ordinary web pages NIP-07, the browser signer interface, on Android, with throwaway signing keys in private and Tor tabs. It also adds NCC relay locators and sync of the user’s NIP-65 write relays, along with browser sync across devices. In 0.32.4, a requested named-service locator takes priority over a newer default address. ncc:// relay locators resolve to ws or wss addresses before saving, and the NIP-07 shim no longer narrows a page’s meta Content Security Policy.

Android 0.33.14, published on 18 November and still labelled alpha, adds management of multiple Nostr identities under Settings → Identity, according to its release notes. Users can add local keys or NIP-46 connections, switch the active signer for new NIP-07 requests and pick a default identity that stays first in the list. The app remembers the active choice across launches.

On desktop, a November 17 source commit adds Share to Nostr for ordinary tabs. Sharing requires the user to be signed in with relays configured, and it signs a kind 1 note carrying the page title and URL, with an optional comment. That commit also raises the version number to 0.33.7; it is source evidence only and does not by itself show a downloadable 0.33.7 release.

PeerTube2Nostr

PeerTube2Nostr, a desktop tool that publishes PeerTube videos to Nostr, released v0.2.3. Its Flatpak build now embeds frontend assets, which earlier builds loaded from a localhost development server. Tauri setup and state handling are fixed, and the app falls back gracefully when no system keyring is available. With these fixes, the packaged app runs as installed.

Iris Chat

Iris Chat, an end-to-end encrypted messenger built on the nostr-double-ratchet library, released v2026.11.13.4. This version sends each group message as one signed sender-key ciphertext and lets clients read groups anonymously. v2026.11.13.6 sends repair requests for missing keys to the known sender device (comparison). Every device in a group has to update. New group messages do not trigger background notifications, and relays can still tell that the same sender’s messages are being read. Later app source asks linked devices for history when a chat opens and replaces a local history inventory pull without cancelling the peer’s pull on the same stream. Earlier patches remove recipient-device names from message events and split author subscriptions to fit relay limits. These source changes came after the 13 November downloads and are not in those builds.

In the library, Rust and TypeScript code no longer names the recipient device on new kind 1060 messages. Established group senders publish one anonymous sender-key payload. Sender authors learned through private key distribution are exposed without account or device identifiers, so host apps can subscribe to them anonymously. Chain repair goes only to the authenticated writer device. In Rust, key-only repair targets that device only while the owner and device remain authorized, and unknown writers or missing roster revisions fall back to general recovery. Other commits stop losing backlog and splitting rosters under churn and send sender keys once per roster change. They also keep header keys with skipped message keys. Author subscriptions are split into chunks of 1,000 and capped at 12,000 authors, and old missed-message keys are dropped before active ones. Attempts to lay out those chunks are bounded, with a fallback to fixed-size sorted chunks, so adversarial key prefixes cannot stall the layout or produce oversized filters. Group controls and repair still create traffic for each device. Both peers must update for new shared group traffic, and older wrapped history stays readable. According to the README, keeping historical chain seeds for recovery costs some forward secrecy. It also warns that removals must reach senders and that anonymous reads can still be linked by IP address and timing.

A later Rust commit keeps the preferred sender key when an old distribution is replayed after key rotation. The library now updates its preferred key only when no preference exists or a distribution introduces an unknown chain. Replaying a known historical distribution therefore no longer selects the old key or prompts redundant forwarding to linked devices, and a regression test confirms that a delayed message from before the rotation still decrypts. In a controlled benchmark, replaying two already-learned distributions produced two extra signed envelopes (4,168 bytes) before the fix and none after. That result comes from one test setup and is not a general traffic or reliability guarantee. The fix is in the Rust code only, and no TypeScript patch accompanies it. A version bump to Rust 0.0.181 adds a changelog covering the replay handling, redundant forwards and existing wire and storage formats. No new tagged library release or published package has been verified, and no external audit could be independently verified in the sources checked for this edition, which does not mean that no audit exists.

Postilla

Postilla, an Android app for publishing marketplace listings on Nostr, released v1.0.27. When a user edits an old kind 30018 product, the app republishes it as a kind 30402 listing and asks relays to withdraw the old event only after a relay confirms the new one. Hidden and sold listings no longer show up in discovery, and deleted addressable events no longer return to the local cache (v1.0.17 to v1.0.27 diff, v1.0.25).

Zino

Zino is a Nostr messaging client that was called Struthio until a rename this week. In v0.15.0, it uses negentropy on connect to catch up on recent gift-wrapped messages and fetches only the IDs it is missing. Relays without negentropy support fall back to the existing backdated REQ. A follow-up responds quickly when a relay replies with an unknown-command notice. Interoperability with other clients has not been independently tested.

Emanator

Emanator, a web and Android app for posting from several Nostr accounts, added Boost as and Quote as in version 1.5.2. From an account page, a user can repost or quote any recent note from another account, including notes published outside Emanator. These signed actions go through the app’s existing Nostr action queue (commit, Android 1.5.1 to 1.5.2 diff, Android 1.5.2). Android 1.5.3 adds search to the account picker.

LaWallet

LaWallet, a Lightning wallet whose Android app connects to wallets over Nostr Wallet Connect (NWC), shipped v1.4.0 through v1.7.1 (v1.5.0 to v1.7.1 changes). v1.4.0 adds NIP-46 remote-signer login through bunker or nostrconnect URIs with editable relays. It also adds kind 0 profile fetching and editing, with profiles published through the remote signer. If one relay accepts a profile, that does not mean every relay keeps it. Merged source also refreshes profiles from relays at startup and login and whenever a profile is opened. Recipient profiles are cached. v1.5.0 pools one socket per relay URL, with reference-counted, capped subscriptions and backoff that respects rate limits. Since v1.6.0, transfers between remote wallets request an invoice from the destination wallet over NWC and pay it from the primary wallet. The on-chain and USDT pages are still marked as coming soon. v1.7.0 cuts the timeout for non-payment NWC requests from 60 to 20 seconds. pay_invoice keeps its 60-second timeout.

In the separate LaWallet NWC web service, merged source adds email magic-link login. For a new user, the server creates and holds a Nostr key and then returns it to the client. The client uses the key to sign a NIP-98 HTTP-auth request, which it exchanges for the existing JWT. Links are single-use, expire after 15 minutes, are stored only as hashes and are rate-limited. Opening a link preview does not use up the link. A vault fallback can derive a separate nsec-vault key from JWT_SECRET. During migration, decryption tries both the old and the new vault key. Operators who use the fallback must therefore back up the JWT secret to keep custodied keys recoverable. The claim dialog offers every login method and resumes a username claim after email login. No backend release or deployment has been established.

Mialuna

Mialuna, a Nostr client with a photo-posting composer, released v0.24.0. It adds photo adjustments, curves and non-destructive edit recipes, which are applied to the kept originals when a post is composed. The comparison with v0.23.1 shows the editor, rendering and export paths. No on-device rendering test is claimed.

NIP44 Notes

NIP44 Notes, a notes app that stores its notes on Nostr relays, added cross-device sync through relays in version 0.03. v0.04 fixes the WebSocket content security policy and app loading for installed Android and web builds.

Nostrfi Relay

Nostrfi Relay, a Nostr relay implementation, now broadcasts ephemeral events to live subscriptions without storing them. Its migration 6 deletes ephemeral rows already stored, so operators who need that data must back it up with the old binary before migrating. Operator HTTP signatures are now bound to the configured relay origin, and replays are rejected. Both changes appear in the 0.3.0 release notes alongside role and admin dashboard features. No security certification is claimed.

Myco

Myco, an Android host for napplets with its own relay, Blossom storage and phone pairing, released v0.13.0 (diff). Paired Circle phones now pass the newest signed Myco release APK to each other. Share Myco sends the app to a phone that lacks it, either over a hotspot or through the Android share menu. Android asks before installing. The received bytes must match the pinned publisher’s signed file event and the release signing key. Phones on 0.12 can receive the update notice, but only 0.13 can transfer the update itself. Myco now routes its own relay, Blossom and pairing traffic through an in-app TCP/IP stack, which leaves Android’s VPN slot free for another VPN. An optional VPN remains available for other apps and exit proxying. Napplets need permission to use a gamepad, and only the foreground app receives live input. Apps keep running through rotation and resizing. USB reconnection and discovery of phones from desktop FIPS also work better.

#176 was merged after the release and is not part of v0.13.0. It adds handler hints for NAP-INTENT, the napplet interface for app-to-host invocation and handler selection, and lets apps launch by catalog ID. When a recommended app is installed, any waiting payload is tied to that app’s review screen and delivered only after the user taps Open. #177 sends every intent launch through the review sheet, including launches of installed apps. The caller is not told which apps are installed. With #178, the phone counts itself as a blob holder when its own store has the file. As a result, the app store’s Around you view can include app files already on the device. The peer count and return shape are unchanged.

Separate from the release and the merged intent work, open PR #180 was opened on November 17 and received further commits on November 18. It proposes neighborhoods to replace Circle, pairing and NAP-MESH. One-time QR, link or NFC invitations set up per-link keys. After that setup, later requests carry NIP-98 signatures, and offers use kind 37516. Applets address a neighborhood through neighborhood://, and the runtime fans events and blob access out to linked peers without revealing membership to the applet. Neighborhood posts stay out of the device relay. Each neighborhood has quotas of 10,000 posts and 256 MiB, and eviction favors keeping the device’s own posts. App, nsite and Myco release updates can be shared per neighborhood.

A radio-nearby extension in #180 uses ephemeral links. Their state is forgotten when no radio peer is in reach, and also at launch or node restart. BLE advertises a one-use four-byte secret. The peer proves that secret with an HMAC tied to its link key. Later commits restrict proofs to radio-reachable peers and bound replay and time windows. They also limit link-service requests and stop treating unknown blob availability as definite absence. The PR lists several items as unfinished: the newest BLE secret and retry handling, fallback advertisements, invitation revocation and device checks for the new UI. These details describe open development, not release behavior. No completed two-device verification is claimed here.

NUTCADE

NUTCADE, a Cashu ecash wallet with an arcade, published v1.12.1. The release documents NWC spending budgets and anonymous zaps, both introduced in v1.12.0, and adds one-time delivery over Nostr for payment requests, treasure hunts and bounties that survives recovery (commit).

Roadstr

Roadstr, an app for reporting road events over Nostr and MeshCore radio, now uses event kinds 1315 and 1316 and radio frames compatible with Roadbeacon. Roadbeacon is a separate project, and Roadstr is developed independently. Version 1.3.0 made this change, dropped an optional, deprecated duplicate event layout and adopted MeshCore datatype 0x0150. Its current release is v1.4.0 (comparison), and its motorway rerouting is not Nostr-related.

Keycloak Nostr Auth

Keycloak Nostr Auth adds Nostr login to the Keycloak identity server. Version 0.2.1 accepts sign-in from a browser extension or a NIP-46 bunker. With a bunker, the signing key stays on the remote signer. Each login is a kind 27235 NIP-98 signature bound to the URL, the method and a hash of the challenge. The server checks that the timestamp falls within a time window, and each challenge works only once.

Tawny

Tawny, an Android pet-monitor app, now prefers Nostr for pairing and signaling between devices (v1.0.4 to v1.0.5, FOSS v1.0.10 to v1.0.11). Users can configure relays or choose a relay-only mode; the default mode falls back to Tawny’s own rendezvous service. Signaling uses encrypted gift wraps, while video and audio travel over a separate transport. Follow-up code gives the Monitor its own Nostr key; earlier code derived it from the pairing key. The public key now appears in the pairing link. Tawny’s privacy has not been independently audited, and peer-to-peer delivery is not guaranteed.

T-Bone

T-Bone, an Android Nostr client fork published as social.tbone.fork, adds editable custom home feeds and stores the feed layout in encrypted account backups. This week’s releases also fix crashes on relay reconnect, bound quote lookups and add cache controls. Version 0.6.0 changes relay WebSocket compression and uses the Blossom upload server the user explicitly selected. Version 0.6.1 adds cache presets and local profile and mention search backed by the Room searchText index.

The Wired

The Wired, an app for community spaces with channels, ships a preview of encrypted spaces in 0.8.0, off by default. Spaces use shared epoch keys and grants, not Marmot MLS. Chat messages, edits, replies and mentions are encrypted. Space metadata, the member list and posting times stay visible. A new encrypted space has a single chat channel. Attachments, reactions, polls, other channel types, previews, search and notifications are turned off in encrypted spaces.

Cosign

Cosign, a beta protocol, library and server for Nostr signing with threshold keys, published server releases 0.12.11 and 0.12.12. Its surrounding protocol has not been independently reviewed. In 0.12.11, a client or relay that disconnects during a subscribe or close no longer crashes the process, and the server logs unhandled promise rejections, which had been linked to a restart loop. In 0.12.12, the server queries its own relays for the archive: group relays and the archived kind 10002 write relays. Damus only seeds an empty archive. Archive fetches move from fifteen-minute intervals to hourly runs spread over the first minute.

better-auth-nostr

better-auth-nostr, a plugin that adds Nostr sign-in to the Better Auth framework, released v0.7.0. Before issuing a token, the server now verifies the login event that the signer returns. On adapters that support transactions, first-login creation of the user and public-key records runs in one transaction, and errors carry stable codes (#46, #52, #53, #62). Client error codes and statuses changed in breaking ways, so integrators need to migrate. Adapters without real transactions keep a limited fallback against race conditions.

After that release, #63 merged to the main branch on 18 November. It is not yet part of a tagged release. In production the plugin no longer accepts an unconfigured baseURL, which it uses to bind the URL signed in NIP-98 login requests. Operators who need a dynamic base URL must opt in with allowDynamicBaseURL. The change also gives the plugin’s endpoints their own per-IP rate limits: 10 nonce requests per 60 seconds, 3 login attempts per 10 seconds and 5 public-key additions per 60 seconds. These limits apply only where the Better Auth rate limiter is enabled.

nostr-social-graph

nostr-social-graph, a library that builds a user’s follow graph and computes social distances, released v4.2.0 with a signed Hashtree bootstrap for graph snapshots and immutable access to selected files. v4.2.1 pins the exact bounded graph bytes used on mobile and verifies them offline. An existing local graph can reconcile revisions of public lists with relays using NIP-77.

v4.2.3 (#11) validates mobile v4 graph data strictly and rejects malformed identity and list bounds. The standard signed public discovery graph must now reach at least 10,000 users. Custom graphs and saved personal graphs are still supported. If a graph is rejected, falling back to embedded discovery data is left to the application. A separate source change (db950a0) publishes graph updates independently of the slower profile crawls and tracks profile coverage by completed sweeps. A newer graph therefore does not mean that profile metadata has been refreshed.

nostr-pubsub

nostr-pubsub, a TypeScript and Rust library for delivering and syncing Nostr events across relays and peers, shipped TypeScript releases focused on delivery to each relay. 0.5.30 stores a delivery row for each event and relay pair. It clears only the destinations that acknowledged and defers relays that rate-limited the publish. Structured rate-limit errors with retry hints and reporting of partial success support this queue. In 0.5.31, paused rows stay pending while eligible rows continue. 0.5.32 keeps an independent retry scope for each set of destinations when one event is sent to several, so each set is retried separately. Reads can fall back to replicas when a relay’s history is incomplete, and the SimplePool adapter returns as soon as one relay acknowledges a publish. For this retry tracking to hold, persistent queue adapters must store and return the additionalScopes field, and implementations with multiple writers need an atomic updatePending.

0.5.29 accepts recipientless kind 1060 v2 envelopes with headers and removes the anonymous discovery API. It also replaces per-author relay discovery with relay-list ranking. 0.5.28 and reconcile 0.1.2 speed up set reconciliation. The reconcile package now owns its wire types and uses constant-time range fingerprints. The speed figures are maintainer synthetic benchmarks. They are not independently verified performance or security guarantees. Source on the default branch (#1, d087f67, e28afb3) brings recipientless envelopes to FIPS provider 0.6.4. It also adds Negentropy sync for public peer feeds in Rust, which has not been released yet.

fips-ts

fips-ts, a TypeScript runtime for the FIPS peer network that finds peers through signed Nostr kind 37195 adverts, released runtime v0.0.62. The release limits lookups and repeated WebRTC redials to peers that have gone offline. After five failures, a peer enters a 30-minute WebRTC cooldown. Preferred peers back off on a shorter schedule, and applications can now replace their preferred peers at runtime. The traffic measurements come from in-memory tests. Live browser acceptance is left to the applications that use the runtime.

Alby Hub

Alby Hub, a self-hosted Lightning wallet that serves apps over Nostr Wallet Connect (NIP-47), released v1.24.7 on 14 November, shipping stricter request handling merged on 10 November. It validates malformed keysend requests and malformed NIP-04 ciphertext, answers invalid JSON with an explicit BAD_REQUEST and answers unknown methods with NOT_IMPLEMENTED. Open proposal #2727, still unmerged, would reset connection editing on switch or cancel so that a name and NWC permissions cannot carry over to a different connection.

fips2go

fips2go, an Android app that runs a FIPS mesh node on a phone, fixed the token-protected local bridge its nostr-sdk client uses to read signed public-name claims from relays over FIPS. In v0.10.1, the four relay slots go only to connections that present the bridge token, and unauthenticated handshakes get their own bound and deadline. That release also sends the destination npub.fips relay as the WebSocket Host, though the author notes that host-routed testing against a real relay was not performed. Both PRs move DNS to TCP and accept answers only from the queried upstream, while another fix set bounds native DNS queries and handles tunnel errors.

v0.10.2 moves the app’s TCP streams off the runtime so that stopping the forwarder ends its thread. It also applies rebinds that arrive during a rebind and cleans up after a failed start. v0.10.4 redacts the relay access token before it reaches the log buffer or logcat at any log level; that short-lived token was unusable off the phone. Release notes report device checks within stated ABI limits.

Bitcredit Core

Bitcredit Core, the library that manages Bitcredit identities, companies and bills and propagates their changes as Nostr events, released v0.6.0 with fully reworked Nostr propagation. Outgoing chain, invite and notification events are now prepared and signed before the state transaction, and their propagation queue is persisted atomically with the identity, company or bill state they describe. A worker attempts delivery immediately, then retries on a default ten-second interval with per-message exponential backoff that starts at five seconds and caps at fifteen minutes. Dependent actions wait for their prerequisites, and status reporting plus a manual retry expose anything still pending. Each required message has its own acknowledgment threshold, bounded by the number of target relays. A relay acknowledgment confirms neither peer receipt nor credit settlement. Prebuilt Flutter FFI binaries sit under a separate precompiled tag.

A later source follow-up, which is not part of v0.6.0, handles invites that arrive before the chain they refer to (3d76247). Incoming bill and company chain invites now retry resolution up to five times, 500 ms apart. Writes to the delivery database are serialized behind a shared mutex while network delivery stays concurrent, and the SQLite connection limit rises from five to ten.

Mesh-LLM

Mesh-LLM, a distributed inference system that advertises meshes as Nostr kind 31990 listings, released v0.80.0 with changes to discovery (#2983, #3063, #3087, diff). An optional publisher_serves field tells thin clients whether a listing’s own invite endpoint serves a model. Clients try serving publishers first, then older publishers that do not declare the field, then non-serving publishers, and keep the original order within each group. Fallback listings stay available, and a client-only publisher does not become an inference relay. The default relay list keeps damus and nos.lol, drops nostr.band, nostr.land and nostr.wine, and adds ditto, primal, nostr.net and oxtr. Once upgraded, public nodes without membership restrictions converge on the lowest mesh ID their peers announce. Private, policy-based and SDK meshes keep their IDs. Mixed public meshes settle fully only after all their nodes upgrade.

Open #3125, created on November 17 with implementation commits through early November 18, is not part of v0.80.0 or any other release. It would separate two discovery outcomes: no Nostr relay answered, or a completed query found no meshes. Discovery would track relay completion and received events and would stop treating swallowed fetch failures as an empty result. The CLI would exit with an error and a nonzero code when no relay answers, and would report partial relay health. The publishing watchdog would record a listing as present, missing or unknown, so a relay outage stays unknown and does not trigger a takeover on the assumption that the listing disappeared.

Iris Kit

Iris Kit, the shared package set behind Iris applications, published several runtime tags. runtime-v0.2.10 ships @iris/hashtree-app 0.1.8, which drops the unavailable nostr.band endpoint from the default public, tree, history and test relay lists while keeping the remaining order. It also exports RETIRED_PUBLIC_RELAYS so apps can recognize saved copies of the old defaults, though each app still has to migrate those saved lists itself.

With runtime-v0.2.11, @iris/svelte-ui 0.1.3 is published. Its release notes list private contact memory (ContactMemoryPanel, FavoriteStar, createContactMemoryStore), Node and browser helpers, and gold trusted social badges. Against the previous tag, the diff changes only versions, the changelog and clipped-name alignment, so the contact-memory code predates this tag. The badges are interface elements with no protocol-wide trust guarantee.

On November 18, runtime-v0.2.13 released @iris/profile-events 0.1.0, a new package added in bd8773d. It edits profile fields while keeping untouched metadata, custom JSON and event tags. It also compares profile and follow-list versions, detects conflicting edits and flags large removals. These are helpers, and a client’s follow list gains this protection only if the client uses them.

runtime-v0.2.14 followed with @iris/svelte-ui 0.1.4 and @iris/hashtree-app 0.1.9. 757ed91 adds a shared public profile editor with standard and custom fields, tag inspection and preview, plus verified profile reads and writes guarded by signer approval. A follow-up included before publication, 92a5bd6, scopes queries to the account’s configured sources. A verified known head may display offline, but writes require completed history. Only a complete empty result permits creating a profile, and unanswered history is not treated as evidence of absence. After signing, a query cancels the replacement if it finds a newer remote head. Publication counts as successful only once a durable queue or a remote relay accepts it. Apps must adopt these exported helpers, and the releases do not show which Iris apps have done so.

Napplet web packages

Napplets are embedded Nostr web apps. The Napplet web packages implement and test the draft contracts between napplets and the apps that host them. To match revised intent and navigation drafts, the project released core 0.41.0 and nap 0.40.0, along with conformance 0.28.0. Intent deliveries now require a nonempty string sender and no longer carry a delivery ID. Navigation reports lose deliveryId, and revisits settle by revision and value. This is a breaking update to a draft contract, not an accepted NIP.

Separately, merged preview hardening uses Kehto’s source-document preparation to strip RTC constructors and turns on its experimental nested-context lock for every quick preview. It rejects frame markup, requires Trusted Types and removes any preview that acquires child contexts. Browsers without Trusted Types, and apps that register their own default policy, may fail to run in quick preview. After a failed site deployment, a build-order repair followed. Neither PR establishes that the hardened public site is deployed.

Napplet Soy

Napplet Soy, a shell for running napplets (small Nostr web apps), released soyLI 0.34.0 with negotiated realtime WebRTC delivery. Reliable JSON stays the default. Peers that support it can send transient updates and separate binary events, and a send with an uncertain outcome is not retried as JSON. The release also includes FIPS session and resource controls. The author’s rollout documentation records how deployment, workers and the installer were turned on. Multiplayer over real networks and interoperability with independent shells remain unverified. Measurements on a local simulated network do not show performance on public networks.

Merged source after the 0.34.0 tag adds an opt-in NIP-60 wallet, which stores Cashu wallet state on relays. The wallet starts disabled for each account and browser and keeps funds and recovery records when stopped. Cache and loading changes reduce repeated decryption requests to the signer, though overall CPU use has not been measured. Experimental document tools need two separate grants, both off by default: one for internal calls and one for browser WebMCP exposure. Both grants are limited to the live document and account. A follow-up adds a browser-wide switch and fullscreen download actions. The switch is on by default but does not authorize document tools. Turning it off revokes their grants, and turning it back on requires fresh consent for each document. soy.webmcp/1 is a local experiment and has not been accepted as a NAP.

More source merged on November 18, also with no release verified. #22, #71 and #72 add an opt-in Playing now directory whose game-room joins recheck the provider. They tag the signed kind 11317 inventory with CEP-15 schema hashes and tool names. Controller input reaches only the focused napplet, through a private NIP-5D port. NAP-GAMEPAD is still a draft, and native isolation depends on browser policy. Physical controllers, Safari and Firefox are unverified.

HolyFit

HolyFit, an Android step and fitness tracker in the Vanderwarker wellbeing suite, released v3.0.0. Step-history queries now fetch legacy kind 30078 records alongside the kind 1359 events the app already published, so older history loads next to newer records. The release notes announce end of life for the legacy format on 1 January 2027 and describe deduplication that prefers the canonical event. Neither that deduplication nor any date-based deletion appears in the changed code. “SNIP-10” is the suite’s own name for the format, not an upstream NIP.

nunlock

nunlock is an Android app that tracks daily phone unlocks. In v3.0.0 it moves its records from addressable kind 30342 to regular kind 1342. History requests cover kind 1342 alongside kinds 30342 and 30078. The app asks Amber for all of its signing permissions at once. The project has announced that legacy support ends on January 1, 2027. “SNIP-10” is the wellbeing suite’s own name for this format and is not an upstream NIP.

SaintStream

SaintStream, a listening app from the same Android suite, released v3.0.0, which splits listening data into three event types. Latest-track status uses addressable kind 36787 with an expiry. Live playhead and playback state use ephemeral kind 20344, while listening history uses regular kind 1073. The history filter adds kind 1073 to the existing kind 30344 and 36787 queries (commit). As with Cellibacy, the announced legacy end of life on 1 January 2027 has no verified enforcement. SNIP-10 is the suite’s own term, and the changed code does not show the claimed canonical-preference deduplication.

SisterCharge

SisterCharge is a battery-state tracker from the same Android wellbeing suite. In v3.0.0 it stores live battery state in replaceable kind 10343 and keeps history as regular kind 1343 events. History queries still include legacy kind 30343, and the app requests updated signing permissions. The suite has announced the same January 1, 2027 end date for legacy support.

Cellibacy

Cellibacy, a digital-wellbeing Android app that publishes daily network usage to Nostr, released v3.0.0. Daily usage records move from addressable kind 34557 to regular kind 1357. History queries cover both kinds, and signing permissions now include kind 1357 (commit). According to the release notes, the legacy format reaches end of life on 1 January 2027, but deletion on that date has not been verified. The notes use the suite’s own SNIP-10 term, which is not an adopted NIP. They also claim canonical-preference deduplication, which the changed code does not show.

Magnetar

Magnetar, an index that ingests signature-verified NIP-35 kind 2003 torrent events, published v0.3.2-redeploy1 as a pre-release on November 18 after merging #18. Oversize reports now stay provisional after a server restart until the worker re-sends its hello message. This stops a small worker from permanently excluding a torrent that a larger worker could retrieve. Seed checking keeps its pacing and router health probing when DHT crawling is turned off. MP4 trun parsing now counts runs that lack per-sample fields in a single step, which bounds a loop the upstream notes describe as reachable with crafted input.

Database enrichment moves to an enrich_due queue, and the migration has no supported rollback. The release notes ask operators to take a verified database dump before first start, then upgrade the server followed by every worker. Older binaries refuse a migrated database. These steps come from upstream and have not been tested independently. On the Nostr side, Magnetar keeps its existing NIP-35 index with NIP-65 relay discovery and its /relay endpoint, and this release introduces no new event format.

Marble

Marble, an Android Nostr app, published five releases on November 17 and 18. v0.15.0 moves notes into encrypted vaults stored through relays and Blossom servers. Earlier notes are imported once, and the old relay events are not erased. Concurrent edits appear as versions side by side, and deleted notes go to a Trash with Restore. Marble Web shares the same vault notes. Removing a device and cycling the key creates a new generation that the removed device cannot open, which does not undo copies or keys it already obtained. At the design snapshot, sharing with invites and readers, audit and repair, and garbage collection were not yet built. The vault format follows a draft specification that is not an adopted NIP.

v0.13.0 replaced public Cosign signing servers with Keykin. Under Keykin, pieces of the key are stored on the phone and on a box. Any two of those pieces together can sign. Accounts set up with Cosign servers do not carry over automatically, so the release asks users to export their key before updating and import it afterward. v0.13.1 restored phone-only custody, in which the phone holds the key and signs without a box. Joining a Keykin box is optional. A phone that joins keeps its whole key as a backup unless the user chooses to forget it. Local apps can still sign through NIP-55, and remote sign-in still works through nostrconnect or bunker links.

v0.14.0 signs new website logins into deterministic per-site child accounts by default, with an explicit option to use the main account. Existing sign-ins keep the main account. v0.14.1 opens web apps found through search as temporary Visiting chips and asks the user for permission before any sign-in request. Source code now carries version 0.15.1 with follow-up work on scope-based sign-in permissions and login pointers, and no 0.15.1 release had been published by the cutoff.

The standalone Keykin repository also changed in the window. A November 17 commit adds derived child npubs backed by the same threshold key pieces, together with account and login work and per-site grants. No independent review of Keykin’s cryptographic security has been reported.

Zapstore

Zapstore, a permissionless Android app store, released 2.0.5. Turning off the new social switch signs the user out, stops loading contact relays and removes locally stored comments, zaps, reports and community stacks. Saved apps and catalogs remain. On first install, a catalog gate shows connection, download and import status, offers a choice between Tor and a direct connection, and provides retry and diagnostics. Tor runs inside the app. The APK from the website bundles the catalog, but the GitHub and Zapstore builds do not.

According to the release notes, moving to ONNX Runtime 1.24.3 fixes an upstream search crash on some Snapdragon 8-series phones running Android 16. That fix was not tested on a device for this report. A commit keeps decrypted backup plaintext out of failure messages and logs.

In development

Streets

Streets, a Nostr client, merged PR #1248 and PR #1252 as development on feat/unknown-kind-fallback, not yet integrated into main. Kind 16 generic reposts now appear in the home, user, follow-set and notification feeds, and addressable targets resolve through a tags. Comments, photos, videos and channels can be reposted from their existing controls. Reposts of kinds Streets cannot display show an author and alt summary. Articles, polls and lists have no repost controls and are not supported yet. Reposts that reference only an a tag are not counted. The author reports passing checks and Storybook but no testing in the real app.

Hibiki

Hibiki, a reader for a user’s circle of Nostr authors, merged two changes into main. PR #17 applies NIP-09 deletion requests from circle authors to matching events in the local cache, including addressable events. Requests are kept for 90 days and applied again after a restart. This only removes events from Hibiki’s cache and deletes nothing from the network. PR #18 groups shared links into article stories ranked by how widely the circle shares them, with a limit per site.

Nostur

Nostur, an iOS Nostr client, extends its built-in browser’s signer interface from getPublicKey and signEvent to NIP-04 and NIP-44 encryption and decryption, and it adds a one-day allowance for encryption and decryption approvals. Web apps that rely on encryption can therefore run inside the browser. These are source changes; their inclusion in the shipping 1.35.0 build has not been verified, and the permission system has not been audited.

Coracle

Coracle, a web Nostr client, merged PR #689 and PR #690 as development on dev, not yet integrated into master. Users can add public NIP-51 bookmarks from the note menu and see them in profile collections. New bookmarks are public. Existing lists keep their encrypted entries, and only the user’s own are decrypted. A Conversations tab on profiles filters to public notes in which the two accounts mention each other. It shows neither private messages nor a complete history. The changes also list members of people lists and sort follows and followers by trust. Zaps are routed using split relay hints.

Lumilumi

Lumilumi, a web Nostr client, now checks each redirect in its link-preview endpoint before following it, so a public URL cannot redirect the server to a private address. The fix landed in #1141 on the development branch and reached main through #1142. A regression test confirms that a redirect to 169.254.169.254 is never fetched while ordinary redirects still work. This blocks one redirect path to private addresses and is not a full defense against server-side request forgery or DNS rebinding. Previews in Shift_JIS and EUC-JP now decode correctly.

gittr

gittr, a Git forge built on Nostr, now publishes repository to-do lists and kanban boards as kinds 30301 and 30302. Importing from another forge is one-way and writes nothing back to GitHub. Later imports append new items while keeping cards created locally. Working examples land in the project’s helper cookbook. Both kinds are project-defined, with no adopted NIP or cross-client testing.

App publishing to Zapstore now sends the APK ownership proof with each app publish and in the same publish as the release. gittr renews its official proof and no longer trusts an older copy held on another relay. When a publish gets no echo confirmation, gittr reads back the exact file, release and proof event IDs from Zapstore and counts the publish as accepted only when every wanted ID returns within an eight-second timeout.

If Zapstore refuses a listing that another relay kept, the listing stays on gittr Apps, and the app labels that state separately from Zapstore acceptance. Apps shows one card per repository with the newest package ID and hides removed apps. Releases carry the APK’s Android version code and arm64 platform metadata. The official listing identifier is gittr, and space.gittr.app remains the APK package name.

For NIP-46 remote signing with Amber, gittr can now pass encrypted signer traffic through its server when browser relay handshakes fail. The server carries the encrypted messages as a transport fallback, and no deployment of this path has been verified. A separate fix stops stale background dials from closing sockets opened for a Push. These two changes are direct commits, and the 1.0.2 release notes below do not mention them.

On 17 November the developer published gittr 1.0.2 with an Android package, space.gittr.app. According to its release notes, the APK is a standalone wrapper around the hosted forge at gittr.space, the same hosted forge as the PWA, and it is not an offline self-hosted copy. Self-hosters still clone the git repository, since the package always opens gittr.space. Sign-in uses Amber over NIP-46, and browser extensions are not available in the APK. Users can install the APK directly or announce the tag to Zapstore through NIP-82 from the repository’s Releases tab.

Grimoire

Grimoire, a Nostr client organized into windows, merged #369 and #370. NIP-29 group chats and NIP-53 live chats now tell an incomplete read apart from an empty one. They keep messages already loaded and show when a relay requires AUTH, times out, closes the subscription or returns an error. An auth-required refusal no longer opens a new AUTH prompt automatically. Grimoire authenticates only when it has both a challenge and a signer, and otherwise explains why it cannot continue. When a read is incomplete, pagination raises an error and no longer reports the end of the history.

Grimoire also merged #371 on Wednesday. Windows opened from /run or from NIP-19 preview routes previously landed in a workspace hidden behind the single-window route. Grimoire now reveals the persisted active workspace with the original and requested windows, preserves the layout and keeps preview profiles and events. Pop-out URLs carry the source window’s identity, so revealing an already placed source no longer duplicates it. Older pop-out URLs without window= cannot identify their source and can still duplicate it. Pop-outs do not carry over AI conversations. The fix is merged development work with no release established.

Feedstr

Feedstr, a feed reader that syncs its state over Nostr, published prerelease v0.0.2. Commit ea8b50e adds nsite feeds. Feedstr reads root and named site manifests (kinds 15128 and 35128) plus legacy root-site kind 34128 file records, fetches hash-addressed files from Blossom and verifies their hashes. It uses a site’s RSS feed when one exists and otherwise turns new or changed pages into articles. This supports following nsites, and Feedstr does not host them. The prerelease also adds Tor, I2P and Gemini feeds, YouTube feed filtering and sync tuning.

The same commit adds per-feed route preferences to encrypted subscription sync. On native builds, Tor routes use a local SOCKS proxy and I2P routes use a local HTTP proxy. A chosen proxy route never falls back to a direct connection. An everything-through-Tor setting also covers Nostr sync, reading and remote-signing relays, with I2P feeds excepted. The browser build cannot use these native proxies and receives those articles from other devices.

Feedstr also changed experimental relay sync in commit 665e3dc. Encrypted relay sync reads back its own publications to detect concurrent writes. After a failed request, it sends no more chunks to that relay. Refusal handling and backoff limit repeated sends. Read state syncs before feed caches. Because sync stops after three publish rounds, full convergence is not guaranteed. Incoming long-form events, along with profile and follow-list events, must now match the requested filter as well as carry valid signatures. Public relay targets reject literal local addresses but do not resolve DNS names, so protection against server-side request forgery is only partial.

CarryChat

CarryChat, a store-and-forward messenger backed by Nostr that can also pass messages over local links, added an Android transport that flashes messages from one phone’s flashlight to another phone’s camera. The same change adds LE Coded PHY for Bluetooth (9db5fa1). 04db130 uses a 50 ms light pulse per bit, and it uses two audio bands to send messages by sound over longer distances. A later fix corrects padding in short rounds. The light link moves messages between phones but does not run over Nostr itself. The author’s range and timing observations come from tests with two phones.

Matrix Nostr Appservice

The Matrix Nostr Appservice, a prototype bridge that gives Matrix users Nostr identities, can now manage Concord communities. After 7005917, Matrix users can create communities, attach public Matrix rooms as channels and rename them. They can also issue and revoke share links and send gift-wrapped invitations. Creating a community derives its secrets and publishes the initial roles, Join and Community List events. Other source changes invite users to the Space without separate invites to each channel and turn mentions into npub references with p tags. The bridge also waits up to 20 seconds for public relays to accept encrypted media before marking it sent, and it publishes a NIP-89 application-handler declaration. Roles, admin tools, bans, private channels and rekeying are not implemented. Revoking a link neither recreates the community nor removes keys held by earlier members.

Bosstro

Bosstro is an app that dispute solvers use to resolve disputes on Mostro, the peer-to-peer Bitcoin exchange. Stable v0.1.2, published 17 November, ships two pull requests merged earlier that day. PR #52 adds a read-only lookup of an order by its UUID on the active Mostro node and merges disputes into one Disputes tab. It pins the released mostro-core 0.17.4, though runtime compatibility has not been verified. PR #55 keeps the solver logged in after Android Back and reopening by loading the same solver key into the Rust process that is still running. Repeating this has no side effects. It keeps request generations and subscriptions and refuses a different key. The release does not show that either change has been checked on a physical device with a dispute already taken.

0xchat

0xchat, a Nostr messaging app, merged a source change that replaces retired defaults for relays, connections, uploads, the wallet and calls. Relay defaults move to relay.primal.net and nos.lol where relevant. The chosen upload server is now saved by URL, and older saved positions are migrated. Users of retired servers with no origin move to blossom.band. Calls now use public STUN servers in place of the old TURN server, so two users behind strict NAT may need a custom TURN server. There is no longer a default mint action, so users choose their own mint. NIP-05 editing, which sets the human-readable name@domain identity, accepts any verified address and no longer requires 0xchat.com registration. No release includes this change yet.

bitchat

bitchat, a messenger that works over Bluetooth mesh and Nostr location channels, has an open proposal in PR #1851 for when location permission is revoked. The app would stop publishing its own presence and location-derived rendezvous points. It would also clear old location channels and place names and reject late location results and lookups. Bridge cells advertised by peers, bookmarks and teleports would remain, so the proposal does not turn off bridging entirely.

NYM

NYM is a chat client. Commit a1453c26f064 adds pending private-group invitations to both the Flutter and JavaScript apps. Each account stores up to 20 invitations in encrypted, sealed form. The user accepts or declines each one. While an invitation is pending, a limited number of messages are held. Invitations expire, and a decision made on one device applies to the user’s other devices. A new parser reads Bitchat verification links for kinds 20000 and 23333. It checks only the link format and does not verify identity cryptographically.

Hasheus

Hasheus is a tool for verifying files against hashes signed by verifiers the user trusts. Merged #102 changes follow-list handling, and with it which verifiers a user trusts: a follow list that relays do not have is removed, and a newer locally stored list is kept when relays return an older copy. #100 changes the verify-and-publish flow and clears the current user’s verification on disconnect. A threat model in #104 states that a hash with a trusted signature does not prove a file is safe and that relays can withhold events. It also describes planned withdrawals, verification methods, thresholds and bounded lookups, which are only documented so far.

algia

algia, a command-line Nostr client, released v0.0.139. The release includes #45, which accepts NIP-49 ncryptsec keys. These keys are decrypted only when needed, from a terminal prompt or ALGIA_PASSWORD. The change also adds a key-encryption command. A pubkey cache keyed by the ciphertext hash lets later read-only commands run without a prompt. The new command prints the encrypted value, and replacing a plaintext key in the configuration is still a manual step.

The release also carries #43, which signs through a bunker URL or NIP-05 identifier supplied in the private-key setting. It caches the authorized session and skips the signer for read-only commands, while NIP-26 delegation still requires a local key. #44 deduplicates self-addressed DMs by rumor and authenticates with NIP-42 on the publishing connection, followed by one publish retry.

nostr-idb

nostr-idb, a library that stores Nostr events in the browser’s IndexedDB, reached version 6.0.0 in source with worker RPC. A client and server pair streams results in backpressured chunks and supports cancellation (e803275, d2ed672). Cursor pagination over committed data uses short transactions and a deterministic timestamp-plus-UID cursor. An empty page can still be followed by more results (937d9c9). Sidecar data attaches to an exact event ID and is kept across versions of replaceable events (5273be2). Publication of 6.0.0 to a package registry has not been verified.

NostrDVM

NostrDVM is a framework for building NIP-90 data vending machines, which are services that take paid or requested processing jobs. Its URL and relay handling has been tightened. The framework now rejects URL inputs that are literal private, loopback or link-local IP addresses or localhost. It also skips invalid and non-WebSocket relay tags. When replying, the framework adds the requester’s NIP-65 inbox relays to the request relays. Loopback relays serve subscriptions only, not outbound publishing. The URL check does not resolve DNS names, so it offers no protection against server-side request forgery through hostnames or DNS rebinding.

zap.stream

zap.stream, a Nostr live-streaming platform, merged security changes on 16 November in PR #80, PR #82 and PR #91. Signature checks on events and text-to-speech now recompute event IDs. Media segments are limited to 16 MiB and checked against the advertised SHA-256 hash when an x tag is present. Media URLs taken from events must use HTTPS. Signatures are verified in batches by a WebAssembly module that uses recomputed IDs and caches verified events. Separately, the feed is limited to the last seven days. Gaps remain. The HTTPS media host still sees the viewer’s IP address. Media is tied to an author only when an author link exists and is accepted when none does. Segments without an x tag skip the hash check.

Open draft PR #101 adds NIP-46 bunker and QR login with recovery, covering identity checks, approval, cancellation and logging out across tabs. The draft depends on an explicit Bun patch and on Snort PR #637, as well as on a published dependency. NIP-55 is not part of the change, and the login flow has not been tested with a physical signer.

Route96

Route96 is a Blossom media server. Last week’s issue covered its signature and playlist checks. New default-branch source, which has not been released, runs libav in a separate worker for each job before an upload is parsed. The worker gets an inherited read-only file descriptor and a limited number of frames. It runs under resource limits that default to 120 s and 2048 MiB, plus seccomp (67923e38, aeae951a). Linux namespaces are used where possible, and seccomp still applies when unshare is unavailable. A decoder failure rejects the job.

Label-based deletion matches terms without regard to case at confidence 0.8. It runs as a dry run with an audit log by default (a072a8df). Live deletion bans the file’s hash so the same file cannot be uploaded again (7f60ed08). A later correction includes files that were already reviewed, so turning off dry run processes pending matches. An optional non-media cleanup removes files from uploaders whose activity falls below a threshold, which defaults to 24h. Admin, paid and qualifying shared uploads are exempt. Listing an uploader’s files now returns 403 unless the signer matches the pubkey in the path.

Further unreleased commits extend operator moderation. Operators can now delete (8298f7f7) and search (a0812e55) using combinations of labels, which narrows matches beyond a single label. Reports now show uploader identities, and admins get per-user usage views (d208743f) with traffic ratios (007f2304). The usage table refreshes every five minutes. These additions do not establish how accurate the moderation is.

Shopstr

Shopstr, a Nostr marketplace, has several open proposals on reviews and its MCP server; none has been merged. #685 would count only each reviewer’s newest review per seller and product, plus a seller-level review, so reviewing variants cannot multiply one reviewer’s weight. Sybil accounts and reviews across multiple products could still inflate ratings. #681 would validate and clamp ratings and fix the five-star scale. That proposal would also exclude reviews of one’s own listings and of unrequested targets while keeping the newest consistent text and score.

For the standalone MCP server, #684 would bound review data to 1,000 characters of content, ten rating keys of up to 32 characters and 300-character d tags, marking any truncation. This limits review floods but is no general defense against prompt injection. Under #683, get_product_details would return NOT_FOUND when a listing’s newest version is hidden, without falling back to an older public version; the events remain public on relays. #679 would link unassigned kind 1059 messages to their order_id when saving order status, preserve conflicts and have the dashboard send the messageId.

Mostro

Mostro, a peer-to-peer Lightning exchange daemon that coordinates trades over Nostr, merged #1110, a read-only, encrypted admin-order-info action that needs no new event kind. Admins and solvers at every level can inspect any order, including orders not in dispute, and the reply exposes trade pubkeys and amounts. Bad payloads are rejected and permission is checked before any lookup. Database and Lightning snapshots are taken separately; the Lightning query runs off the main loop and reports unavailable after two seconds, and Cashu orders show mint and locktime without tokens or secrets. #1105 and #1115 add tests. Via #190, mostro-core v0.17.4 supplies the action and a typed order-snapshot payload and rejects missing reply IDs and wrong wrappers. Authorization and Lightning queries remain in the daemon.

Merged #1109 (merge commit) protects price quotes. When exactly two valid price sources exist and the absolute difference between their quotes exceeds a configured percentage of their mean, Mostro refuses to aggregate them. That percentage, pair_divergence_pct, is configured separately and falls back to the outlier threshold outlier_threshold_pct, 5% by default. It keeps the last good quote until a maximum age, after which market pricing fails with PriceTooStale. The contributor tag of the Nostr price source lists only the sources kept, and cross quotes cannot be derived from a refused divergent pair. Separately, merged #863 adds only a design document for a future payment circuit breaker. It proposes per-order principal and rolling-window budgets that would gate Lightning outflow, with a persistent latch that an admin resets. No halt is implemented, and the document describes no Cashu equivalent.

Three open proposals extend the admin work. #1111 would answer Cashu NewOrder and AddCashuEscrow, along with TakeBuy and TakeSell, with CantDo InvalidAction until the Cashu lifecycle is implemented. An unsafe override would default to false. The change would neither fix orders already stranded nor remove the advertisement, and a refused first contact can still consume a trade index. Under #1106, a maker taking their own order under an alternate trade key would be rejected: master identities are matched before any bond or order write, with a CantDo invalid_pubkey reply. Full-privacy users with unlinkable identities fall outside that check. In the command-line client, mostro-cli #270 would send encrypted AdminOrderInfo requests under an admin or solver signer and correlate the replies with their orders. Timeouts and denials would be handled in both human-readable and machine-readable output.

Nostr Market

Nostr Market, the LNbits extension that runs a merchant’s Nostr marketplace stall, merged #173. Paid-status and order-update results are now bound to both merchant_id and order_id, and the merchant is looked up before anything changes. Restored incoming DMs return before outgoing payment or status handling runs, and the bundled market client is updated. Automated checks reportedly stop at preexisting formatting issues, and the change neither repairs historical records nor amounts to a security audit. In the separate storefront, Nostr Market App now matches checkout event updates to the active order, so events for other orders cannot change the current checkout.

Conduit

Conduit, a Nostr marketplace, merged PR #823 to disable the nsec import and restore login paths in source for its managed environments, then reverted that source change on 17 November. Merged PR #831 (merge commit) restores the earlier authentication code across its preview, production and staging configurations. Local secret-key sign-in and automatic restore return, and the controls for removing saved keys are gone. Only a minor clipboard variable cleanup from #823 remains. Whether a live deployment carries the rollback is not established. PR #819 limits commerce discovery to configured peers and stops fanning out to author or link relays. A new device may therefore miss follows published only elsewhere. Routing for shop owners is unchanged.

On the payment side, PR #797, PR #820 and PR #822 check invoices against historical prices. They use the last completed Coinbase BTC-USD minute and the previous day’s ECB rate via Frankfurter. Rates carry forward for at most seven days, and the effective rate gets one 1% bound. Verification pauses when history is missing, and terms that are already funded do not change.

evil-napps

evil-napps, a collection of adversarial test cases for launchers that install napps from signed Nostr manifests, merged #11. It adds a signed kind 35130 rollback fixture and a 31-check browser stage in which a mock relay withholds newer events and leads a miniature launcher to install older, correctly signed bytes; a manifest bound to a different author is rejected. The author reports 195 of 195 checks passing, including the 31 new author-binding tests. These results were not rerun here and do not prove an exploit against a production launcher. Earlier documents from #1 through #10 describe the gaps under test. They establish neither that every launcher is vulnerable nor that the gaps cannot be closed, and nothing in the NIPs changes.

elisym and Askr

The elisym repository holds Nostr job and payment tooling for agents, along with Askr, a shopping assistant built on signed product catalogs. On main, #208 binds a fetched job result to the locally recorded provider when provider_npub is omitted and rate-limits the message and policy tools that read relays. Open proposal #201 would bring Askr to main with relay chat, a runtime, a server and a widget. Askr is absent from the pay-core 0.5.0 release. Its event kinds are defined by the implementation, with no new NIP assignment.

Most Askr work this week is development on comcore, which has not been merged into main. That branch adds the widget, gateway and worker (#202), then admin pages, a landing page, askr-key, an MCP catalog and merchant product links (#205). #206 brings evaluation and model sweeps, pending-state readback, conversation counts, a pinned widget and CJK price handling. Merchant catalogs now carry every field, variants and CSV, with repaired connectors (#210). Tier listing, deletion and suspend --tier come with product caps on every source (#211). Only changed items are published, and store creation is rate-limited (#212). The semantic policy budget is capped at 50 and Shopify imports become read-only (#213). PayCore is dropped as a product source (#217). Price validation in #219 checks CJK country-dollar amounts, currency signs, variants, qualified-only prices and look-alike prices. Deletions dated further in the future than the allowed clock skew are ignored (#221).

For key recovery, a merchant site can replace a leaked or lost key without signing in through the extension (#214). #218 adds secret download. A later admin commit, also on comcore, replaces the password-backed storage of the remembered key from #218. The key is now sealed with AES-GCM under a non-extractable WebCrypto device key kept in IndexedDB. Sealing is on by default and needs no password. Also on comcore, #222 lets the widget speak ten languages: English, Russian, Spanish, German, French, Portuguese, Italian, Chinese, Japanese and Korean. It picks the language from the data-lang attribute first, falling back to the page language, then the store setting, then English. Product cards sit in a horizontal row that can be reached by keyboard and offer buttons or selects for variants. The widget also handles reduced-motion settings.

#203 adds Postgres storage, an operator CLI, an admin API and connectors as development on comcore-phase2, which has not been merged into main. Neither the author’s tests nor any deployment has been verified independently.

Grocery

Grocery is a shared shopping-list app that stores lists as encrypted kind 30078 events. In version 1.0.7, released November 15, sharing republishes the household and its key grant. Each filter also gets its own relay subscription, and the app rebuilds its list d-tag filters after a reconnect. New writes carry a created_at later than the newest event seen, so clock skew no longer causes edits to be lost. Relays can still see sharing metadata, and replacing the Android signing key requires reinstalling the app.

SplitNut

SplitNut, an experimental threshold ecash mint whose guardians coordinate through an MLS group, replaced its trusted dealer with distributed key generation in 9d1f6c1 and a7bb714. Before signing, guardians restore the saved MLS group and replay its history from oldest to newest. Approval digests update the spent and issuance state, and a signed public ledger with an audit example shows totals. The project is unaudited and not meant for real funds. The author’s demos do not count as independent testing.

mdk-squared

mdk-squared monitors fleets of Bitaxe miners. Commit ae3ea65e, from November 11, sends health alerts to a Marmot group when a device goes offline or comes back. A device counts as offline after three failed checks. The alert transport is always on, and the app falls back to marmot-ts when the Rust library is unavailable. Its README still says White Noise rejects its KeyPackages.

Pacto

Pacto, an app for organizing groups into squads, merged #555. The change adds public squad channels built on NIP-28 public chat, using kind 40 for channels and kind 42 for messages. Clients read the channels from trusted relays and filter them locally against the squad roster. A later patch corrects roster handling (c1c91a4, e3c00ce, e4a0a1b). Channel messages are plaintext, without Marmot encryption. The roster is not published, and removing a member does not hide posts already stored on relays. A 0.8.2 version bump in the source does not match any verified release.

Nostrautica

Nostrautica, a chat app built on MarmotKit, described a production sync update in commit d1c00ea. According to that description, the Android app moves to MarmotKit 0.17 and keeps the chat runtime alive for five minutes, so reopening a chat does not wait for relays to reconnect. It also drops a sync-health check that delayed room readiness and opens chats at the newest message. e6fb12c changes the default relays after relay failures. These changes are as the author describes them and have not been verified in the code or at runtime.

Sovran

Sovran, a Bitcoin wallet app with Marmot group messaging, changed how it fetches and publishes Marmot events. Its kind 1059 gift-wrap subscription now looks back three days before the cursor, up from one minute. Regression tests cover wraps backdated by two days and duplicate ingestion. This reduces missed messages but does not guarantee full recovery. If an invitation fails before the peer joins, the app keeps and reuses the group within the same session. This does not cover a failed welcome to a peer who was already added, or an app restart. Sovran now reads, signs and publishes its own replaceable relay list, with tests for timestamps, the signer and an empty default.

Quartz

Quartz, a Nostr protocol library, added library support for a proposed NIP-FB in 3da5f6a. The proposal defines kind 34817 scheduled tasks that use POSIX cron expressions with time zones. Private task tags are encrypted, and the format includes claim and finished decisions. The commit includes tests for an Observer printing case. Another commit, e085ddf, models Routstr kind 38421 announcements, including models and endpoint validation. In 19cd46e, new client methods show which kinds and filter limits relays have refused, but nothing is filtered automatically. This is library code, not a complete scheduler or an adopted standard.

nostrc

nostrc, a C Nostr toolkit that hosts several applications, received two unrelated source changes, both unreleased. In fipsd, its daemon for the FIPS network, peer discovery builds kind 37195 adverts from the transport registry, so TCP and Tor endpoints appear alongside UDP. Each instance gets an advertise_on_nostr setting and an advertisable TCP address. An onion address is published only when Tor is exposed. Adverts refresh after changes but are republished only when their content differs. The manifest still lists unreleased version 0.1.0, and neither interoperability with the Rust implementation nor anonymity properties have been qualified. In the Groundhog app, a readiness fix shows the single-use NIP-46 QR code or URI only after its subscription reaches EOSE. A connected transport does not mean the subscription is ready yet, and a regression test covers this by delaying EOSE beyond 2.5 seconds.

Primal

Primal, a Nostr client for Android, iOS and the web, has six open pull requests that would each add inline translation of notes; none has been accepted. Three send note text to Google’s undocumented gtx endpoint: Android #1118, which also handles the locale target, a bounded cache and retries, iOS #228 and web #241. Two web proposals rely on LibreTranslate. #240 takes a configurable endpoint and optional API key, while #239 defaults to a public Argos demo endpoint through which its author could not confirm a live translation. iOS #227 uses Apple’s built-in Translation framework.

All six proposals keep Nostr identifiers, URLs and invoices out of translation. All but the Apple framework proposal send note text to an outside translation provider. The Google proposals work without an API key, and that gives no privacy protection. The authors of #1118 and #228 did not run Gradle or Xcode builds.

Jumble

Jumble, a web Nostr client, merged PR #892 to main on November 17 to keep one working login method per pubkey. No release including it has been identified. Before replacing saved credentials, Jumble authenticates with the new signer and confirms that it controls the same identity. A canceled or failed authentication leaves the current session in place, as does a signer that returns a different identity. Native secure storage loads before saved duplicates are migrated, and migration is skipped if that storage is blocked. A remote bunker URL’s key may differ from the user’s identity, so new connections ask for the user pubkey and restored sessions use the saved user key. Only the author has reported test results (commit).

Nostria

Nostria, a Nostr client, has two open pull requests, one for mute-list editing and one for browser-extension signing. With #649, edits to kind 10000 mute lists keep both public tags and encrypted private NIP-51 entries. The client queries all of the user’s write and outbox relays and uses the newest event, with the lowest event ID breaking ties. Edits are serialized, and signing ties each edit to the account. An edit fails closed if fewer than two relays respond (or fewer than all, when only one is configured), or if decryption or re-encryption fails. Two stale relays can still answer while a third relay with newer data stays silent, so a newer list can be missed. New entries are added as public tags. Old NIP-04 ciphertext can still be read, and new output uses NIP-44. #650 adds an app-wide 180-second timeout to the NIP-07 browser-extension signing queue. Completions that arrive late are discarded and the queue moves on, although an old extension prompt may stay on screen.

Dark Wisp

Dark Wisp, an Android fork of the Wisp client, can now undo reposts and correctly deduplicates events that relays replay. Related changes render Blossom URIs and fix upload authorization.

Haven

Haven, a personal Nostr relay, merged an opt-in low-memory profile. Setting BADGER_PROFILE=low-memory tunes each of Haven’s five Badger databases; individual options can still be overridden, invalid combinations are rejected and defaults are unchanged. The author reports lower resident memory over a twelve-minute comparison that has not been reproduced independently, and no release containing the change has been established.

Open proposal #145 would move Haven to a successor storage module, changing hook and event APIs and iterator reads. Under DB_ENGINE=badger, Haven would then refuse to start and print migration guidance, so it never opens an empty replacement database. LMDB and BoltDB paths remain, and the proposal performs no automatic data migration.

WoT Relay

WoT Relay accepts writes from its operator’s web of trust, and its repository has moved from bitvora to barrydeen. Merged #104 adds an optional monthly zap goal. When the option is enabled, the relay publishes the goal as a signed kind 9041 event and validates the provider’s zap receipts. It blocks writes while the goal is unmet and updates its payment-required metadata. Meeting the goal reopens writes only for users who are otherwise eligible under the web of trust, not for everyone on Nostr. Merged #118 moves pprof to localhost, so the public relay no longer serves goroutine dumps. Both changes are on master and have not been released.

BitMacro Signer

BitMacro Signer, a remote signer that serves bunker connections, adds configurable fallback relays to daemon subscriptions and bunker links. Further work serializes requests per client to fix races at first login and expires web sessions after a daemon restart.

Buzz

Buzz, Block’s Nostr-based workspace for channels, direct messages and AI agents, merged a series of permission and relay changes into its main branch. Only channel owners can now grant ownership or change and remove other owners, enforced through relay authorization and serialized writes. DMs can grow in place with an explicit choice about including history; human membership identifies the DM, and agents do not count toward the nine-person limit. Opening a private channel is refused when any current or removed member falls outside the sender and the sender’s own agents, and a refused edit stores nothing. A workflow send_dm action looks up or creates the private channel and signs messages, and it requires a channel owner or admin. Operator media cleanup covers a user and the agents they own directly, protects shared or outside-uploaded files, previews by default and deletes only with --delete. Separate operator commands for content, account and profile cleanup followed (#9363, #9364, #9580). They require stopping writers and an explicit deletion step, and profile cleanup always reports account_erasure_complete as false. Removing a user also removes the agents that user owns, and superseded relay-signed lists are removed.

On the relay side, NIP-42 and NIP-98 authentication now allow 120 seconds of clock skew with a 250-second replay window, with a revised assertion-cache lifetime. Empty author, ID or tag filter sets match nothing, and #a filtering runs before LIMIT, restoring selective results and COUNT. The relay now rejects kind 7 reactions and kind 5 deletions of e targets whose h tags name only another channel, so these invisible events no longer occupy catch-up limits. Events without an h tag are still accepted, and bad rows already stored are unchanged. SDK and CLI kind 9 messages, replies included, carry a canonical 0 to 999 ms tag taken from the same clock read as created_at. Query planning for wide e filters improved in local measurements. Optional single-community mode limits ordinary HTTP and WebSocket traffic to the canonical RELAY_URL; admin cleanup and extra rows remain, and every serving revision must restart. Git object-storage pushes compare refs before and after the push: a rejected or no-op push publishes no manifest or event, and refs that landed survive a partial rejection. Taking the identity-archive replacement lock before reading the prior head keeps timestamps increasing under concurrent writes, which supports incremental mobile reads.

Mobile source changes add a Settings sign-out on every build that first saves community keys locally and revokes push leases before closing the hosted session. On iOS 16 and later, a Siri and Shortcuts action, “Message my Bestie”, sends a DM to a chosen agent without opening the app. Android uses shared Cronet HTTP/2 engines with QUIC off and a fallback when Cronet is unavailable, while iOS uses shared ephemeral NSURLSessions for HTTP/2 without cookies. Remote Huddle cleanup keeps transcripts accessible on mobile, and finalization separates an explicit leave from mesh or control-stream teardown so that rejoining remains possible. The gateway gained Android installation enrollment with fixed-payload FCM wakes and verification of Google-rooted hardware Key Attestation with limits on signed calls. Android push stays disabled until an operator configures it, and enrollment fails closed when revocation evidence is missing or stale. This gateway work does not show that push works in the Android app. None of these mobile changes is established as available in a shipped app.

Boost Me Buddy

Boost Me Buddy, a podcast boosting app that signs boost notes through a remote signer, now checks that the signer is reachable before asking for signatures (a48e452). It also lets users retry notes that failed (1d239f2), so they no longer face repeated long waits on an unreachable signer.

DELTUM

DELTUM, a fork of Armada, adds signed classification of messages under multiple topics. Users can subscribe to topics, and users with the right role can move threads while the original messages stay unchanged. The code can be reviewed, but no live service has been independently checked.

Ditto

Ditto, Soapbox’s Nostr social client, published v2.46.4 on GitLab on November 18. Its notes include greentext, list membership from a pasted key or address, a My Packs tab and text sizing that reaches posts. Quotes are kept separate from replies, and comment replies appear on the comment’s own page. Which version currently runs on the hosted site or in distributed binaries has not been checked.

Some of those items first appeared as GitLab source changes that are not in the 2.46.2 or 2.46.3 builds. Edit Members accepts a pasted npub, nprofile, hex key or NIP-05 address. People Lists gains a My Packs tab for finding one’s own follow packs to edit. A comment’s detail page shows NIP-10 kind 1 replies. Hiding media from strangers now applies across event renderers and quote cards and to magazines, their issues and quoted publications. The content-warning policy also covers magazine issue stacks, the issues grid and quoted publications. Multiple-choice polls publish one response tag per choice and count voters, so someone who picks several choices counts once.

In the 2.46.4 source, 5f5ed78 makes the Text size setting scale theme text and arbitrary pixel or rem sizes, including posts. With 82b4461, lines that start with > render as greentext. Common emoticons, a bare > and >> references are left unchanged. On detail pages, bb83f97 counts replies, reposts and reactions from fetched events and counts quotes separately. A fetch can stop at its cap, and when that happens the events it returned may not be complete, so the count shown is only a lower bound. In that case, if a provider reports a higher count, the higher provider count is kept. Removing the mirrored scrollbar gutter in be37ea8 stops the layout from shifting sideways. According to the release notes, Chrome scrollbars are now rounded. Mention and emoji suggestion lists also scroll on touch without picking an entry by accident.

Advanced settings gains a raw event JSON publisher. The publisher ignores any supplied id, pubkey and sig and signs with the current account before sending to the user’s write relays, so it cannot forward an already signed event. Drafts are previewed in the regular note card before signing. Starter templates and kind-specific warnings come with it, though relays may still reject an event and other clients may display it differently. Import and Export now links to the existing version recovery dialogs for profiles, follows, themes, mutes and badges. Separately, the Ditto Blossom media server adds an upload.exempt setting. Listed hex pubkeys that send valid signed authorization skip the blob-size and per-address rate limits for uploads and mirrors. The list is empty by default. Bans and blob-token checks still apply, as does the 64-at-once limit.

Tasa K

Tasa K, a dashboard for peer-to-peer trading activity, now shows live views and history from other P2P platforms that publish kind 35353 orders and trades (5da3333). A platform selector picks the source, and breakdowns cover assets, currencies and payment methods. Kind 35353 comes from a NIP pull request that remains a proposal and has not been adopted.

Nostr Relay Server

Nostr Relay Server, a self-hosted relay by Gabriel Moura, added handling for temporary rejections and imports and an admin GraphQL interface over WebSocket, along with connection tests.

GuideSats

GuideSats, a tour-booking app that pays guides over Lightning, added a demo:nwc mode on 16 November that connects the booking API and PWA to two NWC test wallets using the real clock and block height. The simulator remains a separate path. A hold-limit change checks each wallet’s settlement deadline and cancels holds that would expire before the tour ends. Later fixes shorten the window to fifty minutes and cap demo tour length. The author reports tests with faucet-funded test balances; the app has not handled real money or real tours.

Word5

Word5, a daily word game, gained a native Android client (c858409). Amber is its only provider for identity, signing and encryption. The client keeps self-encrypted account backups and posts results to Nostr only after the player confirms. A follow-up keeps View result and Post to Nostr reachable and reuses the confirmed event when the score link is retried. Encrypted saves go to the Word5 server in signed envelopes. The newer daily chat uses shared keys that the server generates and can read, so it is not server-blind and is neither a Nostr nor a Marmot chat.

Nutjar

Nutjar is a creator tip jar in early beta. It stores the creator’s balance as encrypted Cashu tokens on Nostr under NIP-60, which keeps Cashu wallet state on relays. Creators can sign in from a phone with Nostr Connect. A fix stops overlapping saves from doubling the collected balance shown in the app. Boosts are capped at 100k sats.

accordion.chat

accordion.chat, a Nostr chat client by hzrd149, moved gift-wrapped direct messages to SDK-managed handling. The SDK now handles receiving, decryption, relay discovery and retries. Prepared envelopes survive route changes and partial failures, which reduces duplicate sends.

Shirasu

Shirasu, a bot that posts disaster alerts to Nostr, now adds evacuation destinations from DCX data and default guidance to its posts (20fa9ac). Commit 21209e5 serves lossless WebP alert images through signed URLs and adds image MIME metadata to the signed events. PNG stays the default when the WebP change first lands. Later records point to a production switch, but that deployment has not been independently verified.

noq

noq, a Nostr event queue, now delivers every version of replaceable and addressable events in arrival order, leaving each consumer to choose the latest version. The same change adds durable compaction and rejects malformed content. This is intentional queue behavior and does not follow relay replacement rules.

Cosmos Depths

Cosmos Depths, a game, now has a browser build. Public Nostr relays carry encrypted adverts for game runs along with signed, expiring notes, graves and ghost records, while gameplay runs between players over WebRTC. Gameplay has not been independently tested, and the source does not show whether players can connect on restrictive networks.

Kami

Kami turns Nostr-signed comments on a self-hosted site into agent work. Comments from keys on the owner’s allowlist become tasks, and the agent publishes status updates to relays. The published source adds the worker and the relay code. No deployment or security review has been established.

Labradorite

Labradorite lets a phone chat with agents over Marmot encrypted session groups. Its author tagged v0.9.0 on 16 November in the nostr-agents repository (git clone URL), and that tag includes the work from versions 0.7 through 0.9. Version 0.7 adds file and camera attachments with encrypted chunked upload. Version 0.8 lets an agent deliver files to the chat and adds a relay log. In version 0.9, an agent can request a masked sudo password through the group, with cancellation and a five-minute expiry. The source keeps those answers out of the phone’s chat history, but no independent security audit has been done.

Labradorite 0.10.0, published on 17 November, lets Claude sessions keep working across the usage limit, according to its release notes. Claude’s own limit auto-continue does not arm in print mode, which is how agentd runs Claude, so agentd arms it itself. When a rate-limit event is rejected with a reset due within 24 hours, agentd waits for the reset and then continues the task with Claude’s continuation prompt. It does this at most three times per session. If claude exits at the limit, agentd respawns it with --resume and keeps waiting. A prompt, an interrupt or a successful turn cancels that wait. Relay connections from agentd and the Android app also send a User-Agent. The release notes describe this resume behavior for Claude sessions only.

Tendrl

Tendrl is a local-first reader, writer and reference manager. v0.21.0, released November 12, adds a local network mode that blocks ordinary relay connections and stores publishing locally. A broadcast picker lets the user deliberately re-send already-signed local events to chosen relays under a scoped permit. It never signs new events. Later source exempts remote-signer transport from local mode and lets the picker handle any event. Because NIP-46 traffic still passes through, local mode is not fully offline.

ocaml-nostr-relay

ocaml-nostr-relay, a Nostr relay written in OCaml by mattn, now enforces a configurable NIP-13 proof-of-work difficulty. It advertises the requirement and rejects events with too little work. Focused tests accompany the change.

Social Backup

Social Backup, a browser tool that carries an X account’s social graph to Nostr, links an X account through a public verification post. It can then publish a Nostr follow list that matches the account’s verified X follows. A later privacy change builds profile cards and links from local data that is refreshed separately, so ordinary X browsing does not query relays for each profile visited. Only verified public originals are published, and private or unverified captures stay local. The unlocked signing key is stored unencrypted in the browser profile.

Rayl

Rayl, a Lightning wallet app, can now hold several external wallet cards alongside its built-in wallet (def2106). Each card is stored separately and can include multiple Nostr Wallet Connect (NWC) connections. Payment routing, storage and deletion use each card’s NWC settings separately. This change was committed on 12 November.

Block

Block, an Android Nostr client, routes events to recipients’ inbox relays by looking up their read relays and publishing to a bounded set. It also adds local and offline event search. No release or production use is established.

pi-nip17-bridge

pi-nip17-bridge connects encrypted Nostr DMs to coding agents. A fork adds encrypted image sending. Each image is encrypted with AES-GCM using a fresh key and nonce, and only the ciphertext is uploaded to Blossom under a throwaway author key. Incoming images are decrypted and passed to an AI provider, which can see them in plaintext. The fork has not been security-audited.

qntx Marmot (mk-core)

qntx/marmot, a pure-Rust Marmot toolkit, merged mk-core changes on 17 November that add encrypted media, an outbox and agent streams for host apps. mk-core builds on a pinned version of the Marmot development kit (MDK) and does not replace it. The README calls the project pre-alpha, with only a Rust session and key-value core and no platform bindings. Its packages/marmot directory holds typed registries and vocabulary, not a working TypeScript SDK. Interoperability with White Noise has not been verified, and the cryptography has not been reviewed.

PeerRoom

PeerRoom, a static web app for voice calls and screen sharing over WebRTC, now connects peers automatically from a single link, using public Nostr relays for Trystero signaling. Media flows directly between peers. No TURN server is configured, so connections can fail on restrictive networks.

SmartFlow Social

SmartFlow Social pays for campaigns over Nostr Wallet Connect. Source changes harden those payments. Wallet commands get deadlines, and structured wallet errors are interpreted. Before paying, the app checks each invoice’s amount, hash and network. When a payment’s outcome is unknown, the payment stays held for manual resolution. A safety deadline stops an operator from marking it unpaid while the original attempt or its reconciliation could still be running, which prevents paying twice. Release notes for alpha.3 exist in source, but no published release has been established.

BitcoinDistrictRelay

BitcoinDistrictRelay is a deployment stack for running a Nostr relay alongside a Blossom server. It now pins Blossom 6.4.1 by image digest and changes its Caddy admin configuration. The Caddy admin API is still enabled on the container’s loopback interface.

Treasures

Treasures, a Nostr geocaching client, fixed uncertain zap payments. While an NWC reply is pending, the client no longer starts a second payment through WebLN. When the user explicitly chooses WebLN, the client pays the invoice shown on screen.

WordPress Nostr plugins

wp-plugins-nostr, a set of WordPress plugins that show Nostr content on websites, can now use kind 30000 follow sets to choose source authors in its calendar, learning and long-form blocks. An empty or unreadable list adds no authors, and a block with no authors shows no content.

Juke⚡tr

Juke⚡tr, the Nostr media app previously branded Madstr.tv, which keeps that app ID and repository, added a Radio section. It discovers kind 31237 station events and NIP-53 live shows from relays, drops stale live statuses and plays radio and HLS streams with controls specific to live playback. Dated 17 November, a release branch describes Android 1.5 and a web publication. No artifact or deployment has been verified independently.

bkind

bkind, a relay for kind 4 direct messages, removed an undocumented check that rejected certain message shapes. Messages with reply references and messages addressed to the sender now reach the relay’s explicit policy, and regression tests cover both cases. The project also gained a deployment script.

Amethyst

Amethyst, a Nostr client for Android, merged several changes to main without a release. Feed loading now tracks end-of-stored-events against the notes currently held, refetches notes lost from the cache and keeps account feeds warm for 15 minutes when switching accounts (#4809). Emoji packs gain search and previews; before the first addition, Amethyst fetches the newest verified kind 10030 list and refuses to add if no relay answers (#4803). A NIP reader displays official NIPs and NIPs published on Nostr, with highlighted code and pages for each event kind (#4797). Compose signatures are now per account and sync through encrypted app data (#4793).

Upload metadata stripping now covers video and audio, cleans up temporary resources and produces fast-start output (#4790). The Tor switch for Applets and Websites is off by default except in Full privacy mode, so napplets and unconfigured sites connect directly. An explicit site choice takes precedence, and Amethyst uses Tor until those choices have loaded (#4789). Observer, an experimental personal newspaper, adds encrypted AI keys, scheduling and Routstr payments (#4799). It relies on open draft specifications, and its payment tests used fakes.

Later merges, also unreleased, protect unsent work. In the short-note composer, #4819 keeps the text when signing is refused, and also when the signer is unavailable or times out. A voice recording is kept after an upload fails. The composer stays read-only while it waits and allows a retry after a failure (patch). Quitting the app or removing the column still loses pending text. #4821 adds a shared media Studio for cropping and trimming with GIF editing in composers and chat, separate from the metadata stripping in #4790.

On desktop, the bunker now asks for approval before an app connects or a signature is made when trust settings require it, so not every signature triggers a prompt (#4824). #4812 adds clients for local coding agents and a NIP-34 workflow for repositories and proposals. On the Nostr side, it handles repository discovery and linked clones. Proposals are published in the existing format, and no new agent wire protocol is introduced. The agent programs must already be installed, and the work targets the desktop app (merge).

diVine

diVine, a short-video app on Nostr, merged a large set of changes to its main branch. None is confirmed to be in the 1.0.29 release or any later release. #11054 adds native remixes. A remix imports a published video while keeping the previous autosave draft, and earlier imports and credits are reused. The pull request also replaces the earlier opt-in policy, so a video with no reuse tag can now be remixed. A false or malformed tag blocks remixing, and videos already marked false stay blocked. Reusing audio requires explicit consent. A recent block in the author’s kind 0 profile takes priority, and the remix is refused if that check gets no answer. These rules are an app convention, not DRM or server enforcement. #10907 lets users reuse named classic sounds from the feed with attribution. Older sounds can be reused only if their current source can be found, so the change does not grant blanket audio permission. #11176 adds intro and outro effects, alongside smaller fixes for comment ordering, upload errors, full storage and the camera sheet.

Downvotes now wait for startup sync and query read relays for the comment or video (#11103). Arrow state comes from deletion reads scoped to that reaction and is kept when a read is inconclusive. Deleting a downvote removes only that reaction, though unanswered reads can still produce duplicate downvotes. With #11047, the queue for delete-for-everyone requests persists across account switches and holds pending, unconfirmed or blocked deletions until they are retried. It cannot guarantee remote erasure or revoke copies already downloaded. #10737 merges lists against the complete relay version, keeping both remote additions and unsynced local edits. Offline drafts encrypted to their owner now survive sign-out and account switches. Unreadable data goes to a bounded local quarantine before it is deleted, and removing an account erases only that owner’s data. Drafts waiting on permissions need a manual Sync now, and some conflicts can still occur. #11209 recognizes root and parent relationships across revised video IDs and comments that exist only as addressable references, so top-level comments made before an edit stay top-level.

Account switching also received privacy fixes. #11185 stops the outgoing account’s asynchronous stores from writing the incoming account’s shared keys, which could otherwise publish bookmarks in the wrong user’s kind 10003 list. Projections for bookmarks, preferences, seen state, moderation, reports and deletion history pause during a switch and resume on rollback, and snapshots and revisions are stamped with their owner. #11205 keeps private NIP-51 bookmarks out of the unencrypted Saved snapshot and purges older snapshot keys for the signed-in account, while public references are still cached. After a failed read, #11204 recovers private items by decrypting the previously retained encrypted list, once per repository instance. Missing ciphertext or a fresh install leaves those items unrecoverable.

For direct messages, #10920 stores the signed NIP-17 gift wrap for each recipient. When a relay’s OK response is missing, the app resends the same wrap across reconnects and group retries. A permanent refusal may clear the message, and offline sweeps keep unconfirmed work. Delivery and reading are not guaranteed. #10718 sends reports made from direct messages through a moderation DM and suppresses the public kind 1984 report. Including the reported message is opt-in, and oversized details are refused before the report is saved for submission. A later patch removes the support ticket. Reports made from profiles stay public, and delivery to moderators has not been verified.

Keep Android

Keep Android is a signer app. These changes are merged to main, and no release followed this week. Under trust-on-first-use, merged #634 holds the connection, trusts the next connection’s certificate after authentication and warns that the connection may be intercepted. Open #635 proposes pinning the exact SPKI mismatch shown to the user after authentication. It has not been merged.

Approval handling also changes. After the core responds, #627 checks the NIP-55 kill switch again before returning results, which may mean waiting for an audit append. Provider rows that were withheld are abandoned under the same ID. #618 follows the core’s needsFreshAuth flag for sensitive co-signing in both notification and in-app approvals. #628 stops offering or saving remembered NIP-46 relay-auth choices when the relay cannot be read or a batch hides its scope. #619 handles the core refusing to save a relay. Stricter relay parsing and bunker checks come from the core dependency, which #622 updates with a real-relay regression fixture for kill-switch enforcement. That core code was not inspected here. #620 verifies the audit log in 256-row pages under the audit lock and keeps the count and anchor checks. This limits memory use but does not certify the log’s integrity. Relay settings now show connection health, latency and last-connected status (#573). None of these changes guarantees safety against every race or attack.

rnostr

rnostr, a Rust Nostr relay, merged configuration and access fixes to main without a new release. With #46, core and extension settings are validated before a reload is applied. An invalid reload keeps the previous settings, and invalid settings stop startup. Unknown fields in registered or core sections produce errors. Reloads also wait for writes to settle and handle atomic file replacement. They keep environment overrides as exact text and keep rate-limit counters unless the rate rules themselves change. #47 separates auth-required errors from restricted ones, so clients can tell when authenticating will not lift an IP, author or key denial. The restricted_writes field in the relay’s NIP-11 information document now reflects the auth prerequisites configured for writes. LMDB always enables MDB_NOTLS, so reader slots are released with their transactions. The query timeout now also covers scanner setup and sparse scans before the first match.

Two further changes merged to main on November 18. #51 rechecks read permissions on open subscriptions at the next delivery. A policy block closes the connection with code 1008, and missing auth sends CLOSED with an auth-required reason. Events already delivered are not revoked. #50 caps the total length of fragmented WebSocket messages and handles invalid UTF-8.

Subscription and configuration handling also changed. A client at its subscription limit can now replace a REQ by reusing an existing subscription ID, and requests that would add more IDs are still refused (#52). Subscription IDs are JSON-escaped in outgoing EVENT and COUNT result messages and in EOSE and CLOSED control responses (#53). Rate-limiter kind values that would overflow are rejected (#48). When an allowed configuration section has not been registered by any extension, a warning is produced at startup, at registration and after each successful reload (#49).

Rely

Rely is a Go framework for building relays. Open draft #14 against main adds support for answering NIP-77 negentropy sync requests. It stays off until the operator configures hooks. Sessions, snapshots, frames and session lifetime all have limits. The hook must return the complete set of events the requester may see, or an error. Rules set in Reject.Req do not apply to sync, and the draft does not add outbound sync.

Cinderous SDK

Cinderous SDK, an experimental Nostr SDK that includes a Node relay with organization rosters, added roster administration on its main branch. 1f2503a adds opt-in NIP-86 relay management for the Node relay, with SQLite persistence and NIP-98 HTTP authorization bound to the request body. Signed rosters remain the authority on membership. 87795e0 hardens the endpoint. Behind a proxy it requires an explicit NIP86_PUBLIC_URL, and it ignores forwarded host headers and checks authorization before reading the body. The endpoint also validates input and persists changes before applying them. Sessions end when the roster key changes. With a19e192, the relay applies signed kind 10038 roster events directly, even when the HTTP admin API is disabled. 6997838 lets co-admins named by the owner sign rosters. The owner keeps authority over co-admins, and any roster a co-admin signs must still list every co-admin. The Cloudflare Worker version lacks these features.

Version 0.91.0 arrived as a large source commit, 0447d3e. Small mesh group calls use NIP-59 per-recipient signaling with kind 21002 events, default to four participants and allow at most six. Each pair has a deterministic offerer, and a failure between two participants stays within that pair. When a roster removes a member who is already authenticated, the relay sends a NOTICE, closes the connection with code 4003 and drops that member’s subscriptions. Hosts that embed the relay directly must dispatch the returned outbound messages, and the Worker does not change allowlists at runtime. One-to-one calls fix dropped tracks that arrive without a stream and camera transceivers that were never negotiated. They now create fresh MediaStream objects on change, which alters callback behavior.

For IoT devices, the same commit adds long polling through next?wait= with values from 10 to 50. It also adds ack and state endpoints. Queued commands are kept for 10 seconds, with up to eight per device. An opt-in Shelly plaintext translation requires an enable flag, a nonempty list of allowed public keys and per-device keys. It excludes door locks. On that path the relay holds the device keys, so the traffic is not end-to-end opaque to the relay. Python reference-device vectors exist. ESP-IDF and ESPHome pieces are skeletons for spec comparison and do not amount to verified hardware support. Saving a CLI secret is optional. If the write fails, the secret falls back to terminal output with a warning. After a known quota reset, reconnect backoff waits a randomized time of up to 20 minutes. When the reset time is unknown, it probes hourly. Versions 0.88.0 through 0.91.0 are not verified GitHub releases. The cryptography is experimental and has not been externally audited.

nostr-tools

nostr-tools, a widely used JavaScript library for Nostr, merged parsing and connection fixes to master without a release. Bunker parsing for NIP-46 reads relays from nip46.relays, falls back to the older keyed format and returns null for unknown names (#591). NIP-05 local names are lowercased and query parameters URL-encoded (#598), and NIP-30 emoji shortcodes with hyphens are recognized (#593). BOLT11 amounts are read from regtest, signet and testnet prefixes (#595) and from uppercase prefixes (#586). Duplicate nonempty relay hints are removed, and reactions without a p tag parse (#589). Distant NIP-40 expirations are waited out in bounded timer steps, with invalid dates ignored (#585).

Content parsing under NIP-27 no longer mistakes words ending in news: for ws: links and handles blocks that start with ws:// (#583). Balanced closing parentheses stay inside URLs (#581), and lone or oversized hashtag tokens remain plain text (#579). For NIP-19’s encoded identifiers and pointers, oversized TLV values are rejected, preventing undecodable pointers (#577). Relay connections now handle AUTH, REQ and CLOSE messages rejected after a close and clear pending auth and subscription state (#575).

Sorted event lists also got a fix in #602. When several events shared a created_at, binary search could miss one already in the list and insert it again. Insertion now scans the run of same-second events for a matching ID first, and new events keep their existing order. Two targeted tests cover the change.

rust-nostr

rust-nostr, a set of Rust libraries for Nostr, now validates client-initiated nostrconnect pairing separately from bunker connections. Only a response carrying the exact secret from the connection URI can pin a previously unknown signer, and a plain ack is rejected. This closes a connection-spoofing path in remote-signer pairing, and the commit adds focused tests. A changelog entry for 0.45.3 exists, but no 0.45.3 release has been published.

Nostr Notification Server

Nostr Notification Server, mmalmi’s push notification service for Nostr apps, merged a social-graph reader that accepts signed Hashtree directories, verifies the immutable graph bytes and rejects checkpoints that move backwards. A failed refresh keeps the last complete visibility policy. The publisher’s identity authenticates the directory, while the configured graph root decides visibility. No release or deployment has been verified.

Linky

Linky, a contacts-based Nostr messaging and payments app, merged several changes to its main branch, and its developer published Linky 26.11.4 on 18 November. #713 adds proxy-payment currencies to kind 34133 listings and uses fresh content keys for every publish. These listings are shared only with contacts. Listings received from peers are saved in cross-device sync, so a known offer stays visible after relays stop returning it. With #714, contact search can open an npub or Linky name before the person is added, so users can send a first message. #715 retries NIP-05 identity lookups through the same-origin proxy when a host’s direct fetch fails. As a result, verification check marks return for affected hosts such as primal.net.

According to the 26.11.4 release notes, listings and proxy payments sync across devices. Contact search suggests people not yet added and shows who uses Linky, and addresses verified on domains such as primal.net get a check mark. Logging out and cancelling a proxy payment now ask for confirmation, and logout also checks the key backup. Swiping a listing hides or pins it, or pauses it when the listing is the user’s own. Tapping an amount switches its unit, and emoji can be found by name in reactions or after a colon in messages. The published package has not been independently inspected.

The repository also contains a separate operator console, distinct from the Linky app published as 26.11.4. #718 adds a Send action to that console. An operator enters an npub or a Linky name, and a Linky name is resolved through NIP-05. The console then sends a Cashu token inside a Nostr message. If relay delivery fails, the console reclaims the token. This feature exists in source only. It has not been shown to be part of the 26.11.4 package.

MintRadar

MintRadar helps users find and review Cashu mints. Merged #216 adds a k=38172 tag and Cashu-marked u tags to kind 38000 reviews. These tags let other clients that use NIP-87 for mint discovery and reviews, such as cashu.me, read MintRadar’s reviews. Reviews signed before the change are not rewritten. Merged #199 gives manual discovery and Nostr discovery separate budgets.

Notification delivery now follows the recipient’s own inbox choices. Gift-wrapped messages go first to the recipient’s kind 10050 NIP-17 DM-inbox relays and then to their NIP-65 read relays. That list is deduplicated and capped at ten allowed destinations (3c9d5ef). Recipients without a usable inbox list keep the earlier read-relay or fixed-list behavior. The bootstrap reads kinds 0, 10002 and 10050 together and checks author and kind. A refresh waits at most eight seconds for relay lists. A follow-up fix addressed the case in which the NIP-65 list arrives before kind 10050. Before that fix, the subscription closed at that point and DM-inbox discovery was lost. It now stays open in that case (2628cce). These are source and test changes. No deployment or binary that contains them has been established.

Minibits

Minibits is a Cashu wallet. Source changes add NIP-44 v2 encryption to its Nostr Wallet Connect service. A request chooses its scheme with the encryption tag, and the response uses the same scheme. Requests without the tag keep using NIP-04, and an unsupported scheme gets an UNSUPPORTED_ENCRYPTION error encrypted with NIP-44. If the advertised methods or encryption support have changed when the app starts in the foreground, it republishes its kind 13194 info event. It treats the refresh as complete only after reading the event back from a relay. The source is labeled 0.4.5-beta.5, and no binary containing this change was established in the frozen evidence.

Bro

Bro, a bill-payment app that coordinates orders between users and payment providers over Nostr, pushed a long series of repairs to its main branch. Order lists now render from the watchtower’s HTTP snapshot first and then merge relay data into the list in the background (13f99d7, f289efa, 5af59a3). Orders created through the API carry an empty p tag, which hid custom kind 30081 completion and acceptance events from the user. The app now finds completions by the order’s d tag and keeps providerInvoice in updates. It also stops updates from senders without authority from replacing the providerId (f9558a5). Build v817 extends d-tag lookup to acceptances and isolates caught autopay errors, so a dead relay no longer blocks status updates (a4401b6). Acceptance expiry is not part of v817.

User updates are also fetched from fallback relays (322b2bd). A relay screen shows the relays in use, and acceptance fails closed when no relay is available (58bfb11). Watchtower reads have their own rate limit of 600 per 15 minutes for each verified pubkey, with the IP address used when no verified pubkey is present (ed76f3b). Proof images can no longer skip compression. That bypass had left the proof screen black, and the screen gains a defensive error state (6a3fae0).

Stale disputed events can no longer reopen resolved orders, and a completion proof is checked for visibility on at least two relays, with bounded republication in the background (89899ff). Dispute resolutions from older builds that lack the t tag can be read again (407f516). For disputes left open more than 30 days, v817 adds a read-only admin cleanup that applies a resolution found on a relay or, when no trace exists, cancels the order locally without publishing anything (a4401b6). Conflicting proofs pause autopay for mediation, and an allowlist names approved coordinators (e44aca5). Before the bill code appears, a race check prevents double acceptance (486299c). The race winner is the acceptance with the earliest acceptedAt, and a status guard keeps orders that are already progressing or finished from being marked lost (2455b92). A stale lost-race mark is cleared only when positive canonical evidence contradicts it (1ff72a4).

Newer source, which the project describes as a v820 bugfix package for external testers, deals with proof privacy and payment certainty. Orders loaded through the API can lack the user’s public key. Before publishing a completion, the provider now looks up the original kind 30078 order by its d tag, order ID and type. The recovered key is used for NIP-44 proof encryption and for the completion p tag (1a28226). The lookup fails open after a six-second timeout and falls back to the earlier path. For that reason, it does not rule out a plaintext proof. When no NIP-44 payload exists, buyers can now read a nonempty plaintext proofImage that was already published (5f2cda0). That change restores visibility but does not protect images that are already public. Providers that lost an acceptance race stop republishing or renewing their invoices. Forcing completion now requires settled-payment evidence. Previously it accepted an SDK message that the invoice was already paid or an in-progress lock. When payment status is uncertain, the app waits. It neither clears the paid flag nor pays again. Targeted acceptance and completion fetches run alongside the heavier sync, and updates are saved before slower maintenance (bb966d2, a203a23). Sync also revisits a buyer’s completed orders from the last five days that lack settled provider-payment evidence. It handles at most three per pass with a ten-minute cooldown, and it stops without paying when status is unknown (d2534fc). The watchtower sends buyers a proof_ready push, deduplicated for 24 hours, that prompts an immediate sync (c96a589). The source version is now 1.0.134+822 (07d3b52).

The v817 repairs are source fixes with regression tests. Neither v817 nor the v820 package has been confirmed in an app-store release. Retries on the race screen can still fail open. None of these changes guarantees safe settlement or rules out double payment, and none amounts to a security audit.

FIPS

FIPS, a mesh networking stack whose peers discover each other and rendezvous over Nostr, merged rendezvous hardening into its default master branch through b260025 and 0c6feed. When the seen-session cache is full, a node now refuses new traversal offers and keeps its replay guards for fresh sessions. By default the cache holds 4096 entries, more than the 3040 offers the signal gate allows in its 300-second replay window. Inputs from responders and STUN servers are now bounded. Timestamp arithmetic is checked, and unknown transport entries in adverts are ignored while usable endpoints are kept. STUN retries and address families are limited. Npub handling accepts any letter case but rejects invalid NIP-19 encodings, the bech32 format for Nostr identifiers. Discovery, offers and cooldown state use the normalized key. An open-discovery startup suite tests the changes against a lab publisher. No release or testing on the live network has been established.

ContextVM SDK

The ContextVM SDK, which carries Model Context Protocol (MCP) traffic over Nostr, has an open proposal, #120, that maps the CEP-8 payment requirements to fail-closed conformance tests and adds a relay harness with controlled delivery faults. Six commits new to this stacked PR also reject a BOLT11 invoice when its amount or expiry disagrees with the offer or when its network does. Oversized payment-option arrays are rejected before individual elements are validated. Tests are mapped to a requirements manifest, and Bun conformance CI is pinned. Earlier commits in the stack belong to separate work. The PR is unmerged and unreleased, and its test results are the author’s.

Kehto

Kehto is an alpha toolkit for running Nostr napplets, and Paja is its reference developer runtime. It is not a general-purpose client. #421 adopts core 0.41, which removes the local intent contract and rejects messages with an empty sender. #427 delivers messages only to allowed recipients. With #434, Paja starts without a signer unless one is set explicitly and does not store Bunker credentials. For development convenience, #425 sets firewall defaults that allow developer interfaces but block external link opening. #315 checks that ContextVM transfer deadlines fall between 1 and 300000 ms before any I/O, uses one time budget for the whole transfer and limits chunk reassembly. Open #437 proposes rules for which relay hints Kehto trusts and is still under review.

Merged #442, #443 and #445 restore room hosting through explicitly chosen providers. They use a pinned ContextVM registry and soy-rtc/1 signaling encrypted with NIP-44, and one isolated window key serves both ContextVM and WebRTC. Saved provider families can be discovered from an nevent, a schema hash or a website and are checked against their signed inventory and hash. Labels and membership stay local, and signaling and ICE are still set explicitly. Only ordered JSON is supported, without the optional binary or statistics features. Connections across separate networks through NAT or TURN, and with a real Soy browser peer, are untested, and no npm publication of these changes is verified.

marmot-ts

marmot-ts, the TypeScript implementation of the Marmot protocol for MLS group messaging over Nostr, tightened its ensurePublished upkeep. Before deciding that a current slot needs no new key package, it excludes packages whose signed lifetime is expired, not yet valid, absent or longer than the cap. Bounds are inclusive, the maximum range is 7,261,200 seconds and inbound clock skew gets no grace. Replaced private bundles stay in place for separate retirement, and a publication failure still rejects. This source-only work comes with no new release or retirement scheduler and no claim of matching MDK behavior.

Auditable Voting

Auditable Voting, a Nostr-based voting application, merged a remote email relay for delivering admission codes to voters. Organisers can import and edit a resident email roster and generate masked ten-character single-use admission codes. These use the existing paper-admission system, expire after 24 hours by default and can be exported as a CSV with the exact codes. A separate email service sends them. That service is either a local companion over SMTP or cashu.email or the new authenticated email relay. That relay checks the NIP-98 HTTP-auth kind 27235 signature, the timestamp window, the exact endpoint URL, the HTTP method and the SHA-256 hash of the raw body. It also enforces coordinator and election allowlists, stores event IDs to prevent replay and applies rate and recipient limits. The browser signs the exact POST /send body into the NIP-98 header. SMTP secrets can optionally be kept in OpenBao KV v2, and delivery stops if OpenBao fails. Supporting changes classify sender and application errors and retry only through the proxy. Other changes import exported bundles into a local delivery-only mode without registering replacement admissions. Published questionnaires can start a new round without an invited npub roster, though each round still needs new email or paper admissions.

By design, the email relay sees recipient addresses and plaintext admission codes, and the delivery export is sensitive. Reloading the page clears plaintext from the browser but does not revoke admissions already registered. Nostr receives only opaque hashes of the codes, and the voting worker stays separate and uses only Nostr. All of this is merged source code, with no release, public deployment or election security audit. Email delivery has not been observed independently.

Nostroots

Nostroots, the project moving the Trustroots hospitality network onto Nostr, has four open pull requests that harden mobile key handling and server signing. They split an earlier combined pull request into separately reviewable changes, and none had merged by Wednesday. #335 loads Expo Crypto’s native randomness before NIP-06 and nostr-tools load, and it surfaces native entropy failures. The author calls this hardening and reports no demonstrated weak-key vulnerability in production. No native device test is claimed.

#336 waits for generated keys to persist before leaving onboarding and keeps the screen open on failure. It ties the displayed identity to the stored signing key and clears stale recovery words when a key is replaced. Rollback is best-effort because SecureStore has no transaction API, so app termination or another failure can defeat restoration.

#337 normalizes and validates BIP-39 recovery phrases and nsec imports before saving. Rejected inputs include npub values and invalid secp256k1 scalars, along with Bech32 strings that have bad checksums or mixed case. #338 requires an explicit, valid production server signing key and stops the server from silently creating another identity. Development can still use an ephemeral key. No live deployment was tested.

StableKraft

StableKraft is a music and podcast player with Nostr social and favorites integration and value-for-value support. It merged six source changes this week, none of them in a tagged release. #310 removes an automatic audio cache that had no size limit and was written but never read. It purges only that legacy cache bucket and keeps intentional downloads. The author measured 4.52 GB in that cache in one profile. #311 fixes a URL mismatch, relative against absolute, that caused the next song to be warmed up repeatedly, and cleans up listener effects. #313 binds listeners once and keeps paused HLS streams intact.

#312 repairs service-worker precache manifests that returned 404 errors, so the app and its downloads page can start offline. It does not make arbitrary songs available offline. #257 publishes feed favorites only for the chosen feed and leaves track favorites and favorites owned by other apps in place. #314 is defensive configuration and documentation work. Its next-pwa script never ran in this app, so it did not fix playback reloads after reconnects.

Nostr VPN

Nostr VPN connects devices in a private mesh using Nostr discovery and supports paid internet exits. Recent changes are development source only. On Linux, the overlay’s DNS and pairing now work offline when upstream DNS is empty, and malformed DNS settings are still rejected. Private exit capabilities are now advertised under the shared mesh ID. Previously they were advertised under a per-device roster ID. #187 aligns the GitHub and Hashtree defaults with the 4.1.22 source that had already shipped. It leaves the existing tag and binaries unchanged and is not a new 4.1.22 release. Work toward a 4.1.23 candidate has started, but no 4.1.23 binaries have been confirmed.

Open proposal #186 would let a user manually renew a paid exit from the seller’s latest signed copy of the same offer. The seller, mint, price and capacity constraints must still match, and renewal fails when no live offer exists. Open #185 adds consent coverage. As of the cutoff, neither has been merged or shipped.

Servus

Servus, a CMS and blogging engine that also runs a personal Nostr relay, has been discontinued by its maintainer. A README commit on November 18 adds “This project has been discontinued” and “Servus (2022 - 2026)”. No reason, migration path or replacement is given in the notice. It covers the source project and says nothing about sites already running Servus. Operators who use it for a blog or personal relay should treat the code as no longer developed. Links to the tracked servus-social repository now redirect to ibz/servus.

Zapstore server

Zapstore server, the server code behind Zapstore’s Nostr-based app catalog, changed how app search ranks results. With c933887, an exact name shared by several apps no longer gives any one of them the unique exact-match advantage. Keyword scoring gives generic words less weight. Apps in catalog-signed stacks get a curation boost only after text or vector matching has admitted them, so curation reorders matches and cannot add new ones. Stack changes and deletions resync each app’s curated flag.

A second commit, a511c42, adds labeled-query evaluation built on production-catalog fixtures, and that evaluation skips when the fixtures or models are absent. Ranking behavior is shown through tested examples in source. Deployment to the live service and measured production search quality have not been verified.

ClarkQAQ/nostr

ClarkQAQ/nostr, a Go toolkit for building Nostr software, replaced its legacy Pebble event stores with a single storage format called format4 on its default branch (f7df93a, 8cdc8d4). These changes exist only in source and have not been released. Search now matches exact substrings, including short queries. Replacements and deletions are applied atomically, so the next query already reflects them. Count and scan budgets cap the work a single query can do, and the store interface now takes a context and returns errors.

By default the store calls fsync for each committed group of writes. An optional high-performance mode syncs on a timer, every 20 ms by default. If the process or machine crashes in that mode, writes acknowledged since the last successful sync can be lost. The new code does not open stores written in older formats, so operators upgrading from them need to export their events and replay them into a new store.

nostr.watch

nostr.watch is a relay directory that monitors Nostr relays and reports their status. Its crawlers and checkers connect to addresses taken from public Nostr data, so a hostile entry could point them at private networks. Two source changes close much of that path. #988 blocks loopback, private, link-local and carrier-grade NAT addresses, along with local-only hostnames. In the browser, this block protects the relay connections that the browser opens. The same block covers the broker that fetches NIP-11 relay documents and NIP-05 files. It also covers the worker and untrusted profile images. #989 carries the guard into the nostrings trawler and relaymon. Before either one checks a clearnet target, it resolves every address for the name and refuses the target if any of those addresses is local or private. Tor, I2P, FIPS and CJDNS targets stay on their own transports.

The guard has limits. Browser code cannot detect a public name that resolves to a private address. The relaymon guard does not cover a DNS answer that changes between lookup and connection, or DNS resolved on the proxy side. Both changes were committed on 18 November (fbbd20b, 9afaba4). They are development work. No release or deployment has been verified, and a package version commit is not treated as one.

routstrd-auth

routstrd-auth is an authentication proxy for a remote routstrd daemon in the Routstr AI inference stack. For NIP-98 HTTP authorization, it checks a Nostr event signed for that request. Public routes are forwarded without authentication. Source changes on 17 and 18 November tighten that check (416fb47, 0b9cea2, 5840a64). These commits bring together several changes on the main branch.

When a public origin is configured, signatures are bound to that origin. In that configuration, an origin that an attacker supplies through forwarding headers is also rejected. The Cloudron origin is the default. A non-Cloudron install with no origin set still falls back to request headers. Each authorized event ID can be used once, except for the read-only bootstrap GET used while the user table is empty. A bounded in-memory cache in each instance keeps IDs for 125 seconds and refuses new admissions when full. This cache does not survive a restart and is not shared between instances. The last admin can no longer be deleted or demoted. An exact allowlist of methods and paths sorts routes into public, member, admin, inference and proxy classes. Any operation not on the list returns 404, even for an admin. Bearer keys reach inference routes only. Redirects on proxied requests are handled manually and are not followed. Packaging permissions changed as well, and so did the reconciliation of admins set through environment variables.

These changes are development, not a verified rollout. The project’s documentation says the replay guard must wait until the bundled daemon signs nonces. No release or bundled version bump has been established.

Napstr

Napstr’s desktop catalogue sharing over Tor and Napstrfy were covered in September. v0.2.4, published November 17, adds a headless daemon that seeds music from a Linux VPS without the desktop app (commit). The daemon publishes its catalogue and availability over Nostr. It checks gift-wrapped requests and answers with private offers or refusals. Files transfer over Tor. Companion pairing uses Iroh, which encrypts that traffic but does not route it through Tor. According to the daemon’s README, catalogue filenames and tags are publicly visible. The README also states that the daemon connects to relays directly over TLS.

nostr-bunker

nostr-bunker is a Dart implementation of a NIP-46 bunker. Commits on November 18 (ced8364, 3c807ca, c14b6c4, bbb5717) move it from NDK to dostr, which breaks the existing API. Rejected and malformed requests now return errors, and NIP-04 response encryption is fixed. The commits also add switch_relays and logout handling along with immutable app management. State is kept in memory, and persistence remains the integrating application’s job. These changes are on the main branch in source, and no published package containing them has been established.

Lapis nostr-relay

Lapis maintains a fork of a NIP-29 relay, and the repository keeps its Zooid and Unicity provenance. Pull request 1, merged November 17, publishes fork history that had previously been kept locally. For NIP-94 file metadata, that history includes indexing and validation. It also includes Blossom uploads with static media. Plugin-registry assets are part of the same history. The feature code was authored in September, and its commits carry November 17 committer dates. The merge therefore integrates existing work into the public repository and does not introduce a new independent relay.

New projects

Textor

Textor, a static progressive web app for messaging over Nostr relays, published its initial source on 13 November. It offers NIP-17 direct messages and small groups without forward secrecy. For forward secrecy, it offers text-only MLS groups of up to 100 members, built with ts-mls on a Marmot-shaped design. MLS state exists only on the device that joined the group. Interoperability with White Noise, security and deployment have not been tested.

Better way to Internet

Better way to Internet is a conference learning app for Android, written in Go, whose source first appeared on 16 and 17 November. It keeps keys on the device, signs profiles and shows navigation by room and relay alongside public feeds. Its developer published version 1.1.2 on 18 November, and those release notes say the user’s own profile photo goes to the user’s listed media servers, with Primal’s media server used only when no list exists. When the app cannot check that list, it uploads nothing and tells the user nothing was changed. The source can be reviewed, while the published APK has not been independently inspected and no deployment at an event has been confirmed.

Blob Forager

Blob Forager caches Blossom files locally. It looks up authors’ server lists on relays, can fetch files from peer caches and adjusts its disk use as available space changes. Its performance and compatibility with other apps have not been independently tested.

grunq-signer

grunq-signer is a two-part key manager: a browser-extension NIP-07 provider and a NIP-46 remote signer with a relay pool, bunker invitations, sessions and signing approvals. Both parts were implemented on 14 November, and source from 17 November adds signed NIP-05 name claims. The README describes optional NIP-49 key protection along with expiry and permission controls. The 1.0 source and packaging do not mean the extension is available in any browser store, and the project has not been independently tested for security or interoperability.

forum

forum, fiatjaf’s forum client built on NIP-29 relay-based groups, appeared as public source on 15 November (3bf2b30). It supports threads, comments, invitations, member administration and signed relay actions. The README points to forum.fiatjaf.com and describes use across multiple servers. Changes on 16 November add NIP-27 references in comments and Djot formatting for thread bodies. Hosting, privacy and migration behavior have not been independently tested.

signet-nip46-client

signet-nip46-client is a standalone Rust library for remote signing that was extracted from signet-play. It covers bunker and nostrconnect pairing, saved sessions and signer RPC over fray-relay-client. A follow-up shows a signer’s refusal text only when the response echoes the pairing secret, and its tests check reply authors. The library is an extraction with published source. It does not define a new remote-signing protocol or prove compatibility with external signers.

Connect

Connect 0.1.0 is a developer preview for Chromium, installed as an unpacked extension, that combines a local Nostr signer and an encrypted Cashu wallet. Each origin gets its own grants, and every signature and payment needs fresh approval. The project is new and unaudited, and the builder’s tests ran on regtest and in demos, not on mainnet.

gleam-nostr-relay

gleam-nostr-relay is a new Nostr relay by mattn, written in Gleam for the BEAM virtual machine and first published on 11 November. It stores events in PostgreSQL, verifies BIP-340 signatures in pure Gleam and handles each connection’s subscriptions in its own process. The code covers event validation and storage, deletion, expiration and COUNT. Because it does not implement AUTH, it refuses NIP-70 protected events. A change merged on 12 November reduced memory use. Throughput, protocol conformance and security have not been tested.

odin-nostr-relay

odin-nostr-relay is a new Nostr relay written in the Odin programming language. Its initial import implements event, filter and signature processing on PostgreSQL over hand-built HTTP and WebSocket transport, with tests. It is experimental and has not been audited as a production service.

AlphaMessenger

AlphaMessenger is an Android messenger that runs MLS over Nostr. It published its source and a release on November 13. An update on November 15 adds a reserve relay and listens on group members’ relays without writing to them. Its security, its interoperability with other MLS clients and the APK signature have not been independently verified.

SemanticWOT

SemanticWOT is a new recommendation app for Nostr notes that runs locally (c665bee). It builds a co-zap graph from the user’s sent note zaps and uses text embeddings to decide how far recommendations spread through that graph. A diversity step then orders the notes. By default it collects a limited amount of data from nos.lol and needs no private key. Embeddings require an external OpenAI or Ollama service, and in OpenAI mode public note text is sent to OpenAI. No claims have been made yet about recommendation quality or resistance to Sybil attacks.

haja

haja is a new messaging project whose 15 November initial implementation combines NIP-17 gift-wrapped messages encrypted with NIP-44, an authenticated single-purpose relay that keeps messages for at most seven days, and an MCP interface for the user’s agent. Tests enforce the retention cap and the agent’s recipient and daily limits. For now the MCP server holds the user’s key locally, with remote signing planned. A hosted instance documented at haja.chat has not been checked independently. Relay expiry does not delete copies already on recipients’ devices or elsewhere.

Magpie

Magpie distributes software artifacts over Nostr and Blossom through a Maven-compatible interface. In its first source milestone on 14 November, an outbox component finds each publisher’s kind 10002 write relays and domain hints, so publishers need not share one release relay. The README describes release keys pinned and authorized by domain, immutable signed manifests and blob hashes. Its event kinds are still drafts without assigned numbers, and the build-system integration has not been reproduced independently.

NCC-Server

NCC-Server provides server and search tooling for NCC. A November 17 source commit adds a static nsite search interface whose crawler runs in a browser worker. Results are stored in IndexedDB and indexed with MiniSearch, and per-relay cursors let a crawl resume when the user comes back. Configured caps limit the crawler to 20,000 rows and 40 MiB of estimated storage. A source comment notes that the byte estimate is not available in every context, and the row cap still applies there. In this static browser mode the page cannot resolve arbitrary NCC endpoints or verify NIP-05 identifiers, and it makes no claim that a listed service is reachable.

That commit also adds a separate nsite publisher. It hashes the built files and uploads them to Blossom servers using BUD-02, then signs a kind 35128 manifest through NIP-07 and can verify the uploaded hashes. Signing stays with the NIP-07 extension, so the publisher never receives the private key. The maintainer reports Playwright tests and checks of the published files for this work; those results were not independently reproduced.

A later commit adds a read-only operator panel that shows live published records and offers no management actions. Access requires signing in through NIP-07 or NIP-46 with a key that matches the configured operator.

BitPortal

BitPortal is a lobby for VR worlds that finds those worlds through Nostr relays. A November 17 commit adds relay discovery for the lobby and lets creators publish a world explicitly by signing it through BitLogin. Both features are present in source. No test with a live world or a headset has been reported.

brumm

brumm supports identities that span multiple devices and delivers to them offline through public Nostr relays. In a November 18 commit, payloads sealed with Olm are wrapped with NIP-44 under fresh signing keys and left in relay mailboxes. The repository includes a test for devices that are never online at the same time. That test was not run for this entry. The design is not NIP-17, and nothing shows that it interoperates with NIP-17 clients. Its privacy has not been independently audited.

easyrelay

easyrelay is a pre-alpha Nostr relay written in Zig. A November 18 commit merges client authentication and support for protected events. The same merge adds event expiration, rate limits and admission controls, along with tools for deploying and operating the relay. The project carries conformance tests. Nothing yet shows that it holds up in production.

Embr

Embr is a desktop signer daemon that applies a local permission policy to signing requests. A November 17 commit implements NIP-46 remote signing through bunker and nostrconnect connections. The project is pre-alpha and unaudited. The repository contains interoperability test files, but no independent interoperability with outside clients has been shown, and signed release binaries have not been established.

Knight Survival

Knight Survival is a browser game built with WebAssembly. A November 18 commit adds multiplayer. Public Nostr relays carry only peer discovery and connection signaling, and gameplay travels directly between players over WebRTC. The repository includes browser tests, which were not run for this entry.

Mandate

Mandate is a prototype for payout rules that runs on Bitcoin signet. A November 18 commit caps spending with Nostr Wallet Connect budgets. It also publishes a hash-chained log as kind-1 Nostr events. The connected wallet enforces those budgets, and that enforcement was not independently verified. Because the demonstration pays subwallet payees, it is not evidence of mainnet payments. The project is unaudited, and its public log does not guarantee an immutable global history.

Tab

Tab is a prototype for private merchant chat over NIP-17 that verifies invoice payments through Nostr Wallet Connect. A November 17 commit recovers the payer’s state when a paid receipt never reached the relay. After the client wallet is unlocked, the client calls lookup_invoice and runs settlement rechecks one at a time. Pending outcomes stay unknown. According to the README, Tab runs on regtest only and serves no merchants. The project reports local tests, which were not independently run.

Protocol and spec work

NIP-73 adds OpenStreetMap object references

NIP-73 defines identifiers that Nostr events use to reference external content. Compass covered #2224 as an open proposal in February, and it was merged on 16 November. Events can now carry i tags of the form osm:node:<id>, osm:way:<id> or osm:relation:<id>, with osm as the k value. Because the object type is part of the identity, a node and a way with the same number are different objects. Comments can point to a specific map object and no longer have to rely on a geohash area. A reference says nothing about who owns the object, and no shipped client support has been established.

Proposal for discovering relay onion addresses

Open proposal #2550, a draft NIP-0D, lets a relay advertise an onion address for clients that cannot reach its clearnet host from a Tor exit. The relay publishes the address in an Onion-Location header over TLS or in a _onion.<relay host> DNS TXT record. Clients should prefer the header and keep the original path, map http(s) to ws(s) and connect only to the onion target, with clearnet fallback allowed as a MAY. DNSSEC or a trusted resolver is advised, since a TXT lookup made outside Tor reveals interest in the relay. AUTH may use either identity, and clients treat the advertised pair as one relay. The author reports a working relay, but general rollout is not established.

Open proposal resolves nsites through Namecoin

Open proposal NIPs #2540 would let a Namecoin nostr.nsite record point to a static site published under NIP-5A, using NIP-19 identifiers:

  • npub and nprofile resolve to the current root manifest.
  • naddr resolves to the current root or to a named site coordinate.
  • note and nevent pin one exact manifest.

A direct pointer takes precedence over legacy records, and resolution stops if the lookup fails. Manifests are ordered by NIP-01’s event ordering and replacement rules, and files are checked against their Blossom SHA-256 hashes. The proposal separates verification against the blockchain itself from trust in an indexer. A gateway pull request cited in the proposal is not a confirmed release and does not indicate wide support.

Open proposal defines peer-to-peer orders for non-bitcoin assets

Open proposal NIPs #2541 would add kind 35353 for peer-to-peer orders and trades in assets other than bitcoin, with a z tag marking each event as an order or a trade. It reuses NIP-69 vocabulary, but amounts use main-asset units; NIP-69 uses satoshis.

BTC, LBTC, RBTC and custodial BTC are excluded, while bitcoin-pegged tokens on other chains are allowed. The proposal separates token contracts from balances held on a platform and supports fixed prices and orders that can be taken more than once. Trade statements report the executed price and volume, which can differ from the original asking values. A signature identifies the author; it does not prove settlement or a complete trade record and cannot rule out wash trading. An earlier revision lists QvaPay as an implementation, but interoperability has not been checked (#2541).

Open proposal adds L402 authentication for paid relays

NIPs PR #2543 proposes L402 authentication for paid relays over WebSocket. Under the proposal, the relay sends a challenge containing a macaroon and a BOLT11 or BOLT12 invoice. After paying over Lightning, the client returns the macaroon with the payment preimage. The relay then answers with a separate L402-OK message. Access goes to whoever holds the credential, so the relay needs no pubkey whitelist. Macaroon caveats limit which actions are allowed, and the relay rejects any caveat it does not recognize. Credentials can be checked without per-user state, but usage budgets, concurrency and rate limits still need counters shared for each credential. Only the issuing relay, or a sibling relay sharing its secret, can verify a credential, so it cannot be used anonymously across relays. The proposal is open, and no implementation has been identified.

NIP-BE rewrite proposes Noise-secured Bluetooth sessions

Open pull request #2544 rewrites NIP-BE, which carries Nostr over Bluetooth Low Energy. Each session would use a fresh Noise XX key. Advertisements would show only the service, and users could optionally compare a six-digit code. Both sides would authenticate through a modified NIP-42 relay-authentication exchange. Basic NIP-01 relay messages and NIP-77 Negentropy sync messages would flow in both directions at once. Devices recognize each other per session and do not broadcast a permanent identity, though the privacy design has not been audited. Blob transfers can request byte ranges with optional Bao and BLAKE3 proofs. An optional L2CAP channel shares the Noise session and falls back to GATT. iOS overflow advertising works only if Android devices support discovering it. The pull request also proposes removing NIP-BE’s unrecommended label, which has not been approved. The author plans to use the design in next-dipity, but it has not been deployed, tested or benchmarked there.

AI Agent Keys proposal stores provider credentials in an encrypted list

Open proposal #2545, a draft NIP-FA, would let users carry AI provider configuration between clients. It defines a replaceable kind 12000 event holding an ordered list of provider keys and endpoints, NIP-44 encrypted to the author’s own key. Public key tags are ignored, each key may be used only with its own URL, and endpoints must use HTTPS unless they are loopback or keyless. Anyone holding the account key, or able to perform NIP-44 decryption for it, can spend against those credentials, subject only to provider-side limits. Configuration becomes portable without an agent framework being defined, and no deployment or interoperability between providers has been verified.

Scheduled Tasks proposed as NIP-FB

Open #2546 proposes scheduled tasks that run on the user’s own devices. Each task is a kind 34817 event with a POSIX cron schedule and an IANA timezone. Task state, claims and completions are private. Each device opts in to running tasks and waits a random delay before claiming one. Devices read from and write to a majority of the user’s NIP-65 write relays, then wait 20 seconds for a claim to settle. An optional public runner named in a p tag can decrypt and run a task, signs as itself and must check that the requester is authorized. The draft also has rules for daylight saving time and missed runs. Quartz includes some of the building blocks, but no complete scheduler has been shown.

Proposed NIP-FC publishes Maven repositories through Nostr and Blossom

An open proposal describes how to publish JVM, Kotlin and Android artifacts as Blossom files. Each release has a canonical SHA-256 manifest and signed kind 3071 release events, plus addressable kind 33071 snapshots. A bridge serves standard Maven paths. A NIP-05 identifier names the publisher and pins its keys. NIP-65 relay lists and server discovery locate the files. Consumers record the publisher keys and the manifest hash. If a key is compromised, the earliest timestamp does not prove immutability, so continuity depends on local pins. A Gradle integration was not established in the reviewed evidence, and the proposal does not replace Maven Central.

Proposed NIP-1B shares network abuse reports

An open proposal lets operators of any service publish reports of attacks and probes as addressable kind 31984 events. A report can be corrected by replacing it. Single-letter tags make /24 IPv4 ranges, /64 IPv6 ranges, ASNs, apps, user agents and operations searchable, and NIP-32 labels add classification. The text warns that a Tor or VPN exit address does not identify an attacker and discourages harmful detail. A reporter’s signature shows who made the allegation, not that it is true. The author cites about 155 reports covering 9,400 sources on a read-only relay. Independent verification of those figures was not established in the reviewed evidence, and the data should not be used as a trustworthy automatic blocklist.

Scoped Data Grants separates issuer and reader rules

Scoped Data Grants is a proposal for signed capability grants, using kinds 440 and 441, that give access to scoped data. Its latest revision defines the grant’s shape for issuers separately from the rules readers apply. It adds signed refusal fixtures and a local demo of issuing and narrowing grants. It is not an assigned official NIP.

Nostr Archive Standards revise archive declarations to v2

Nostr Archive Standards (NAS), a set of specifications for verifiable Parquet archives of Nostr events, moved its archive declarations and its extracted-data collections and catalogs to version 2 (standards commit). The reference data extractor implements the revised declarations and v2 identifiers, and it compacts conflicting designations. It is a local file library and does not run as a relay service. NAS is not an accepted NIP.

Blossom proposes scoped delegation to another signing key

Blossom, a protocol for media servers that store files by hash and authorize requests with Nostr events, has an open proposal for BUD-11 delegation. The owner signs a kind 24244 token that names one actor, explicit verbs, required server scopes and an expiry. The actor embeds this token in its own kind 24242 authorization. Server and hash scopes intersect, and storage ownership stays with the delegator. A revocation blob under the owner’s direct control disables the delegation, and deleting that marker turns it back on. Tokens must not be published to relays. Mailstr attachments motivated the proposal, and no server or client conformance has been established.

Blossom mirroring gains SSRF guidance

Blossom, the protocol for storing Nostr media blobs on HTTP servers, defines a mirror operation in BUD-04 in which a server fetches a blob from a client-supplied URL. A merged specification change recommends that servers accept only HTTP and HTTPS mirror URLs and block internal, loopback, private and link-local IPv4 and IPv6 destinations. Servers should apply those checks to the IP address they connect to after DNS resolution and again on every redirect; an upload authorization does not replace this protection. This is normative SHOULD guidance that each server still has to implement, and the change establishes no server fix.

Marmot counts an exact relay read-back as a publish acknowledgement

The Marmot group-messaging specification merged #504 for clients that lose a relay’s OK reply. A client can now treat a publish as acknowledged when a relay returns the exact event, with a valid ID and signature, in response to a REQ; results on an existing subscription also count. An empty REQ result proves neither publication nor failure. Clients SHOULD read back their own kind 445 events under the ephemeral key without authenticating as their account, so the read-back cannot link the two. An acknowledgement shows that a relay stored the event, not that the group agrees on its state. The wire format does not change.

Marmot completes relay targets an abandoned publish never reached

Marmot, a protocol for MLS-based group messaging over Nostr, tracks publish obligations per relay. Under durability case 1, a merged change completes the relay targets that an abandoned publish obligation recorded as never sent. A rejecting OK does not count as never sent, because the relay received the event. This closes a case where obligations could stay stranded, and nothing changes on the wire.

Marmot requires extended-length NIP-44 encryption for large messages

The Marmot protocol for MLS group messaging over Nostr merged PR #508 into its specification. Marmot clients and the NIP-44 signers they use must encrypt and decrypt the extended-length version 2 format for plaintexts of 65,536 bytes or more. Notification servers must be able to decrypt it. Group and inbox relays should accept serialized events of at least 2 MiB. Under these limits, a Welcome for one invitee could cover roughly 1,900 members, but only when the group’s tree has blank parent nodes, so this is not a tested limit for every group. The change adds no version negotiation, and local resource limits still apply.

Marmot proposes per-message expiry and burn-after-read

Marmot, a protocol for MLS-encrypted group messaging over Nostr, has an open draft proposal for disappearing messages. For authenticated kind 9 app messages, a sender can set an absolute expiration cap that shortens the group’s retention for the source epoch. A versioned marmot-expiry tag adds a timer on the device that starts when the message is read, plus a required cap for messages that are never opened. Durations range from one second to four weeks. The deadline is saved before the content is shown and survives replay and restart. Burned content is left out of supporting history and backups. Older clients may ignore the tag, and recipients can still copy content, so deletion relies on cooperating clients and cannot be enforced. No MDK implementation or capability negotiation has been established.

NAP-INTENT reconciles handler recommendations and catalog identities

The napplet specifications merged #106 into NAP-INTENT, the draft for app-to-host invocation and handler selection, on master. It merges duplicate IntentInvokeOptions schemas and turns a bare naddr recommendation fragment into a handlerHint, kept separate from the convention’s identity and payload. When an app names a handler explicitly, it uses an opaque catalog identity that is distinct from a recommendation coordinate. Malformed or duplicate hints are rejected. Neither an operation nor a capability is added, and there is no new precedence rule. The existing web projection is aligned with these rules.

NAP-LLM adds optional consent for multi-step sessions

NAP-LLM, a napplet proposal that lets an app ask its host runtime for language-model generations, merged PR #143 as development on nap-llm, not yet integrated into master. A runtime may offer one visible, revocable grant that covers several generations on one handle while the tool set stays the same. The grant must disclose that later prompts, images and tool results will not be reviewed one by one. It must also state limits on duration, count and charges. Authorizing each generation remains the default, and users can decline a session and approve generations one at a time. Revoking the grant cancels work in progress, and generations with an uncertain outcome are not retried automatically. No runtime implements it yet.

NAP-WEBRTC adds data channel semantics

Merged #145 is development on nap-webrtc, not yet integrated into master. Its target, the base proposal, is still open. Napplets can request ordering and retransmission settings, and the shell reports the settings in effect. A separate sendBytes call uses base64 on the wire, and the change also adds advertised payload limits and advisory stats. The peer’s identity must be the signaling key the shell has authenticated, and unauthenticated payloads are not delivered. The proposal says no implementation exists yet.

NAP-NEIGHBOR proposes peer-carried neighborhoods for napplets

Open draft proposal NAP-NEIGHBOR gives each napplet opaque neighborhood addresses for relay, outbox, resource and upload use, carried over the user’s own peers. Each user has a separate view of their own peers. The host manages the neighborhood and keeps each napplet’s addresses separate. Optionally, the host can share proximity information and napplet updates. A neighborhood has no membership list and no privacy boundary, and peers can forward ordinary Nostr events to others. Specs that consume these addresses would need new schemes and upload destinations. No transport implementation exists, and neither delivery nor reach is guaranteed. A companion registry change is part of the same proposal, which replaces earlier mesh drafts that were withdrawn.

NAP-INTENT proposes opening applets by manifest coordinate

NAP-INTENT covers how applets ask the host shell to invoke other apps and how the shell picks handlers. Open #148 lets a manifest coordinate name exactly one installed applet to open or bring into focus. It can also offer an optional verified install, which the user must confirm. Under the proposal, the shell cannot substitute a different handler, change defaults, grant permissions or deliver payloads. Payloads stay with invoke. The proposer links a Myco implementation.

NAP-WEBMCP proposes permissioned tools from running napplets

Open draft #150 proposes NAP-WEBMCP, which would let running napplets register typed tools for AI agents through the host shell. Registering a tool neither authorizes an agent nor grants host permissions; the shell decides which consumers can reach each tool and within what scope. Resetting the document or context removes the tools and cancels open calls, and a call that finishes late is reported separately from the acknowledgement of its cancellation. The bridge bounds JSON schema size, checks replays and mismatched correlations, returns explicit errors on overload and does not automatically retry calls with an uncertain outcome. An optional browser projection is included. It is not a finished browser API, and agents have not been tested against it for conformance.

Cyberspace keeps claimable assets out of public contents hints

Cyberspace, a specification for a virtual world built on Nostr, merged PR #111. Public contents hints now leave out claimable Cashu tokens and NFTs unless the publisher opts in. The PR gives guidance for rewriting hints safely, and NFT hints no longer include a count. Readers should treat contents hints as unverified claims. They do not prove that an asset exists, keep anything private or establish proximity. The change is in the draft specification only and is not in any released client.

Cyberspace avatars drop proof of work and cap content size

Cyberspace is a draft spec for a spatial world built on Nostr. Merged #109 removes the proof-of-work requirement for avatars, which are published as replaceable kind 11333 events. Before parsing, clients must check that avatar content is at most 131072 bytes of UTF-8. They should ignore the old nonce target and show the default avatar when content is too large. A note about signer size limits is non-normative.

Cyberspace draft adds a no-broadcast courtesy for audiences

Cyberspace, a protocol for a shared spatial world built from Nostr events, merged #106 into its draft specification. The change defines a courtesy signal asking audiences not to rebroadcast an event; ordinary readers are unaffected. Clients can ignore the signal, the data stays public and base-chain validity does not change. No client has adopted this draft change yet.

Cyberspace drafts a Games DECK for world discovery and game runs

Cyberspace, a specification for a shared spatial world built from Nostr events, merged #96, its first draft Games DECK. The draft defines how games are discovered in the world and adds an entry marker. Game runs are anchored to that marker and use ephemeral events in the existing kind 20000 to 29999 range, so the draft adds no new kind. No client or production game implements the draft yet.

Cyberspace DNA seed revisions bind their own interpretation

Cyberspace is a protocol for a shared virtual space built from Nostr events. A DNA seed’s revision, identified by its content ID, now determines how validity, pricing, growth, mixing and backward interpretation are evaluated, which makes a separate seed version field unnecessary (#99). Implementers read a seed’s rules from the revision its content ID names. This merged change applies to a draft specification, and revision 1 becomes fixed only when the document leaves Draft. The errata so far are not a released implementation, and no client deploys them.

Cyberspace proposes signed per-world game rules

An open Cyberspace proposal lets a world list its required and optional games-layer rules inline in its signed definition. Game clients lock that configuration for each session and reject worlds whose required rules they do not support. This sets a contract for game clients without changing base-chain validity or requiring the tutorial to be republished. The proposal is still an open draft, and no client has deployed it.

Cyberspace sealed chest looks

Cyberspace has an open draft, #115, for DECK-0004 §3.6. It proposes carrying a large chest appearance as its own encrypted kind 33331 hidden object, referenced from a small look tag, so bag rewrites stop repeating the full geometry. The chest’s signer signs the event, which is encrypted with the containing bag’s region or room key. Readers check the signer, the named d tag and the decrypted payload. A missing or invalid appearance means the chest has no look and must not block opening it. Moving the chest into a bag with another key requires resealing.

The draft, at head commit e31ceb0, proposes a 16,384-byte threshold for sealing and a 240,000-byte maximum for a sealed event. These are proposed ONOSENDAI rules, not Nostr-wide relay limits. The pull request was still an open draft at the cutoff and states that ONOSENDAI implementation waits for merge.

Weather station proposal moves to review

NIPs PR #2163, a proposal for publishing weather station data on Nostr, was marked ready for review on November 17 (timeline event). The draft text, last revised in May, gives each station its own pubkey. Station metadata uses replaceable kind 16158 with geohashes and sensor status. Individual readings use kind 4223, with tags for sensor type and value along with the sensor model, and invalid readings are left out. Both kind numbers are marked temporary.

In a comment on the PR during the review transition, the author said the data shapes have stabilized and pointed to relaying.earth and wss://relay.relaying.earth as working examples. That is the author’s own report and has not been independently verified. The NIP remains an open proposal.

NIP-5D proposes discovering shells by supported NAP domains

NIPs PR #2303 for NIP-5D napplets, covered last week, has now merged a contributed change into its own proposal branch. That November 17 change adds 44 lines of shell-handler rules. The PR itself is still open, and nothing has landed on the NIPs master branch. The pinned text reuses NIP-89 kind 31990 handler events. Each shell lists k tags for the napplet manifest kinds 5129, 15129 and 35129, plus uppercase N tags for each bare NAP domain it supports. A client checks that a shell’s N set covers every R tag the applet requires, then hands off through NIP-89 web templates. Filtering with a NIP-01 #N filter can narrow the candidates, but the client still has to check the full set locally. These advertisements grant no permissions and do not replace the shell’s own checks at load time.

NAP-WEBRTC proposes a common shell signaling profile

NAP PR #152 was opened on November 18 and was still unmerged at the Wednesday cutoff. According to the pinned text, it would replace runtime-specific signaling with a required nap-webrtc/1 profile. Shells hash the napplet manifest address, the room or direct scope, the channel and the protocol into a rendezvous value. Kind 25050 events carry a plaintext hello, and offer and answer signals are encrypted with NIP-44. An applet can suggest shared relays through signaling.relays, and the shell reports which relays it used. Peers must use the same delivery settings and share a default channel named napplet. The proposal specifies a wire contract that shells from different implementers could follow. The cited proposal does not establish interoperability between implementations, and we did not test any clients. Because the rendezvous hash is public, room identifiers with little entropy can be guessed.

Marmot proposes negotiated view-once media

Marmot PR #509, opened on November 17, proposes a view-once profile for images and video (draft at 4a986cf). It can only be activated once every device in the group supports both this profile and encrypted-media v2. A view-once message is an authenticated kind 9 event with empty content and a view-once-v1 marker that sets an unopened deadline. It carries exactly one image or video attachment encrypted under a separate cryptographic domain. Each receiving account-device gets its own opening. It must record a durable claim before fetching or displaying the media and has at most 60 seconds for the attempt, transfer included. The unopened deadline is capped at 45 days, and durable caps also apply at admission time. The sender’s own devices do not use up any receiving openings. Normal preview paths cannot expose the media, and neither can download or export. Portable backups leave out usable originals.

The draft file calls itself adopted, but the PR is still open. The protection depends on clients cooperating. A recipient that keeps the keys can still recover the content, and the profile cannot stop screenshots. MDK draft PR #3527 holds an unmerged implementation proposal that waits for spec approval. Its November 18 commit adds view-once modules to the engine, app and C layers and a SQLite migration for durable consumption. This is proposal code. No shipped client implementation is shown, and no audited implementation is claimed here.

Marmot adds an optional post-link chat inventory

Marmot PR #511 was merged on November 18. It adds an optional post-link chat inventory to the device-group specification. When a new device is linked, the approving device can send it encrypted device-group inventories of kind 477 with tokens for the chats it should end up in. The new device compares those tokens with the chats it has joined, including chats joined through another sibling device. That lets it tell whether it has joined 90 of 100 chats or all of them. Each report is bound to the destination device and the original pairing KeyPackageRef, and it carries a revision, expires and can be paginated. If an inventory is missing or incomplete, progress counts as unknown. Inventories are advisory and do not grant membership. A separate MDK implementation, #3543, merged later the same day. It is not in a stable release or in the 18 November nightly, and no client UI for it is shown.

Marmot sketches agent activity and approvals as editable items

Marmot PR #510 was merged on November 18 and adds an idea page on agents in chats. The page is explicitly non-normative and assigns no event IDs or wire bytes. Under this idea, what an agent says would stay ordinary chat, while its activity, approvals, questions and plans would become editable agent items. Answers and controls target one specific live item, and the agent’s update to that item records what happened. This avoids relying on a runtime acknowledgement that recorded harnesses do not provide. Separate prompt and approve rights would let a group share an agent. Clients that do not recognize the new kinds would still show the ordinary conversation but could not approve or steer the agent. No interoperable client or harness implementation has been shown.

The idea would supersede the one-shot interaction design in Marmot PR #503, which was covered on November 11 and is still open. In a November 18 comment, the author of #503 explained that the PR stays open pending team discussion. The comment explains its status and adds no implementation.

NIP deep dive: public goals and peer-to-peer orders

Two Nostr specs let people publish requests that involve money. A NIP-75 zap goal announces a fundraising target that readers can zap toward, and a NIP-69 order advertises an offer to buy or sell bitcoin for fiat. Clients can find, render and filter both kinds of signed event, though neither kind moves funds. Goal progress comes from separate NIP-57 zap receipts, while trades are taken, quoted and settled on the platform that published the offer. Neither spec requires the other.

Zap goals

The pinned NIP-75 text defines kind 9041 as a regular event, so each goal stands alone with no replaceable address. Its content holds a human-readable description, and two tags are required: amount gives the target in millisatoshis, and relays is a single tag listing the relays that zaps to the goal are sent to and tallied from. Optional tags add:

  • a closed_at timestamp;
  • image and summary display metadata;
  • an r or a tag pointing to an external URL or an addressable event;
  • one or more zap tags that name split beneficiaries under NIP-57 Appendix G.

A NIP-57 zap request aimed directly at a goal carries the goal’s id in its e tag. Under the pinned NIP-75 text, the client MUST also copy the goal’s relays into the request’s relays tag, so receipts land on the relays that the goal names for tallying. An addressable event, such as a NIP-53 live stream, can point to a goal with a goal tag holding the goal id and an optional relay hint; when users zap that event, clients SHOULD put the goal id in the request’s e tag. Relay hints help clients retrieve events without establishing trust or confirming payment.

Progress is the sum of zap receipts that reference the goal and pass NIP-57 validation, which includes checking the bolt11 amount and confirming that the receipt came from the correct zap provider for the correct target. Each receipt should count once, and NIP-75 does not define a complete tallying algorithm. Because readers see only what their relays return, a client that reaches only some of the goal’s relays may show an incomplete total; when those relays already hold every receipt, the total is complete. For closed_at, the pinned NIP-75 text says that receipts published after that timestamp SHOULD NOT count toward progress. That rule governs only what clients count: NIP-75 attaches no payment cutoff or refund to it and, unlike NIP-40 expiration, asks relays to delete nothing.

Retrieved from nos.lol and relay.damus.io, the event below is a real goal whose content identifies it as a qiqstr QA test and asks readers to ignore it. It appears here only to illustrate the NIP-75 format and is no request for donations.

{
  "kind": 9041,
  "id": "499444115e01a11ae3663d594b7bd35f731997b8ede46a86aa9a1184c892e03a",
  "pubkey": "cfdd4a9981b235b8b585480b752fe5be0207be3dfebca0ff5326d7c465646866",
  "created_at": 1794805859,
  "tags": [
    [
      "amount",
      "1000000"
    ],
    [
      "relays",
      "wss://relay.primal.net",
      "wss://vitor.nostr1.com",
      "wss://relay.damus.io",
      "wss://nos.lol"
    ],
    [
      "emoji",
      "100_yeet",
      "https://poster.place/client/emoji/reactions/100_yeet.png"
    ]
  ],
  "content": "qiqstr QA zap goal test, please ignore  :100_yeet:",
  "sig": "1745910f6935c83a2cd1761cb7c905010659bdb6d4999bc86f9aeac0fd4fa017027bd5fa7b000b5ab3242e5963f164bfa24ecda8235e04fd92d3a5c82d172a76"
}

An amount of 1000000 millisatoshis sets a target of 1,000 sats. A client zapping this goal would copy all four URLs from the single relays tag into its zap request, while the emoji tag only tells clients how to draw the :100_yeet: shortcode in the content and carries no payment meaning. No closed_at, image, summary, link or beneficiary tag is present. Under NIP-01, id is the SHA-256 hash of the canonical serialized event and sig is a BIP-340 signature over that id by pubkey. Both verify, showing that this key signed this exact content with the created_at value 1794805859; whether anyone has zapped the goal is outside what either field records.

Amethyst, the Nostr client for Android, creates goals. At commit d48764f, its goal creation view model accepts a positive whole number of sats and multiplies it by 1,000 for the amount tag, then fills relays with the user’s current outbox relays. Before signing and broadcasting the goal, it can add a deadline, image, summary and website. Goal progress bars and zap buttons reached its live-stream headers earlier, in PR #2469.

NosTube, a Nostr video client with live streams, reads goals for streams. At commit 0467076, it fetches the goal linked from a live stream or, when the stream links none, picks the host’s newest open goal among up to twenty recent ones. Its parser requires kind 9041 and an amount of at least 1,000 millisatoshis, checks that the id and pubkey are hex-shaped, accepts only HTTPS images and keeps at most ten distinct relay hints; it performs no signature check of its own. During its progress calculation, NosTube drops receipts timestamped after closed_at and sums the sats from receipts returned by a separate receipt validator. Its goal bar passes the goal id and relays to the zap button and hides that button once the goal has closed or when the host has no Lightning address.

Coracle, a web Nostr client, displays goals. At commit 20cd3da, its note renderer sends kind 9041 to a dedicated component that shows the amount in sats, an optional deadline and the description. Goal creation and receipt totals fall outside the cited code.

Goal descriptions and images are untrusted input, as the NIP-75 topic notes. A client should never execute HTML from a description or present a malformed amount or timestamp as funded progress, and it should limit relay subscriptions and media downloads. Goals and their receipts are public. Because each NIP-57 receipt embeds the signed zap request, a reader can connect the key that signed a request, together with the amount it named, to a particular fundraiser. Receipts are issued by the recipient’s zap provider, and a request key does not prove who paid the invoice. A pseudonymous request names its signing key without establishing the payer’s real identity, while an anonymous request may hide the payer altogether. Readers also see only the receipts that the queried relays return.

Peer-to-peer orders

The pinned NIP-69 text defines kind 38383 as an addressable event, identified by author, kind and d tag. A platform updates an order by publishing a new event at the same coordinate, which replaces the earlier version under NIP-01 rules. An event from a different author with the same d value is a separate order. NIP-69 describes d as a unique identifier for the order without requiring a UUID format.

Besides d, the spec marks these tags as required:

  • k: buy or sell.
  • f: an ISO 4217 currency code.
  • s: the status, one of pending, canceled, in-progress, success or expired.
  • amt: the bitcoin amount in satoshis. With a value of 0, the satoshi amount is obtained from a public API after the taker accepts the order.
  • fa: a fiat amount, or two values giving the minimum and maximum of a range.
  • pm: the payment method or methods.
  • premium: the premium percentage the maker is willing to pay.
  • network and layer: the bitcoin network and the settlement layer.
  • expires_at and expiration: the two time tags described below.
  • y: the platform that created the order.
  • z: the fixed value order.

Optional tags:

  • source: a URL that can redirect to the order.
  • rating: a maker rating, calculated however the platform chooses.
  • name: the maker’s name.
  • g: a geohash used for face-to-face trades.
  • bond: the amount of a security deposit.

Each time tag has its own role in the pinned NIP-69 text. After expires_at, a pending order’s status SHOULD change to expired; after expiration, relays SHOULD delete the event under NIP-40. Relays can deliver events late or return versions that a newer event at the same coordinate has replaced under NIP-01 addressable-event rules. Before showing an order as open, an orderbook should confirm that it holds the newest created_at for that coordinate and that its s status and expires_at still describe an open offer.

Publishing an order advertises an offer without reserving liquidity, holding escrow, proving funds or settling a trade. Taking the offer, quoting the price, handling disputes and holding funds all stay on the publishing platform. A valid signature identifies the broadcaster, which is often a platform key. The signature says nothing about solvency or honest trading. Similarly, a bond tag announces a deposit without proving that anyone paid it. Ratings from different platforms are not comparable, since NIP-69 leaves the calculation to each platform. Clients should present source as a link the user chooses to follow and never run it as code. Fiat currency, payment methods, geohash and posting times are all public, and together they can reveal a trader’s habits.

Mostro, a peer-to-peer Lightning exchange that coordinates trades over Nostr, is checked here at commit 2211a7e. It publishes public orders with empty content and the order’s UUID as d, recording the id of each event. Its created_at values always increase, even when a take or cancel lands in the same second as the first pending event, so the later event still replaces the pending one under NIP-01 ordering. Before publishing, its order validation rejects ranges with only one end and checks fixed fiat amounts, non-negative sats, range limits and quote bounds.

RoboSats, a Lightning peer-to-peer exchange run by independent coordinators, is checked at commit babf62e. It signs orders with the coordinator’s key and sends them to a local strfry relay, deriving each d value as a UUID from an MD5 hash of the coordinator alias and the order id. Its tags cover type, currency, amount or range, payment methods, premium, source, expiration, bond, platform, network and layer, with a geohash added when coordinates exist. A published order maps to pending and every other internal state maps to success, so only two of the five defined statuses appear. RoboSats builds pm values by splitting the payment-method text on spaces.

lnp2pBot, a Telegram bot for peer-to-peer Lightning trades, is checked at commit 6d91a79. Its tag builder emits the order fields d, k, f, s, amt, fa (one amount or a range), pm and premium, along with fixed values network=mainnet, layer=lightning, y=lnp2pbot and z=order. A local rating combines the maker’s rating, account age and review count. For source, the builder links to Telegram, choosing the community channel for community orders, and it takes expiration from its configuration.

Absent from that output are the required expires_at tag and the optional bond. Whenever a public order changes, the bot signs and verifies an event and then publishes it to its configured relays. Differences such as RoboSats’ two-status mapping and lnp2pBot’s missing expires_at give an orderbook spanning several platforms good reason to parse orders defensively.

History

NIP-75 was merged on 2023-09-01 in commit 08bd050598, “NIP-75: Zap Goals (#757)”, by Alejandro, adding a target and a grouping on top of NIP-57 zap requests and receipts. Francisco Calderón added the order proposal that became NIP-69 as xx.md on 2024-06-27 in commit f57d559. On 2024-11-04 it was renamed to 100.md in f72a2f6 and then to 69.md in bff61dd. Among its references, the pinned NIP-69 text lists an earlier 31001.md proposal and n3xB.