Merge branch 'main' into copilot/revamp-contributing-workflow

Author: cameri

.changeset/empty-nip40-tests.md

@@ -0,0 +1,4 @@
+---
+---
+
+Test-only NIP-40 integration coverage; no release version bump required.

.changeset/fix-upsertmany-tiebreak.md

@@ -0,0 +1,5 @@
+---
+"nostream": patch
+---
+
+Fix replaceable batch upserts to apply NIP-01 tie-breaker semantics when timestamps are equal by comparing event IDs.

.changeset/full-donuts-allow.md

@@ -0,0 +1,5 @@
+---
+"nostream": minor
+---
+
+added NIP-45 COUNT support with end-to-end handling (validation, handler routing, DB counting, and tests).

.changeset/invoice-user-repo-unit-tests.md

@@ -0,0 +1,5 @@
+---
+"nostream": patch
+---
+
+Add unit tests for InvoiceRepository and UserRepository with sinon-stubbed DB client

.changeset/nip-02-integration-tests.md

@@ -0,0 +1,5 @@
+---
+"nostream": patch
+---
+
+Add integration tests for NIP-02 contact lists (Kind 3)

.changeset/uppercase-tag-filters.md

@@ -0,0 +1,5 @@
+---
+"nostream": patch
+---
+
+Support uppercase tag filters (#A-Z) in filter schema validation

CONFIGURATION.md

@@ -87,7 +87,7 @@ The schema ships with a small, query-driven set of indexes. The most important o
 | `events_active_pubkey_kind_created_at_idx`   | `REQ` with `authors`+`kinds` ordered by `created_at DESC, event_id ASC`; `hasActiveRequestToVanish`; by-pubkey deletes. Composite key `(event_pubkey, event_kind, event_created_at DESC, event_id)` so the ORDER BY tie-breaker is satisfied from the index without a sort step. |
 | `events_deleted_at_partial_idx`              | Retention purge over soft-deleted rows. Partial on `deleted_at IS NOT NULL`.                             |
 | `invoices_pending_created_at_idx`            | `findPendingInvoices` poll (`ORDER BY created_at ASC`). Partial on `status = 'pending'`.                  |
-| `event_tags (tag_name, tag_value)`           | NIP-01 generic tag filters (`#e`, `#p`, …) via the normalized `event_tags` table.                         |
+| `event_tags (tag_name, tag_value)`           | NIP-01 generic tag filters (`#e`, `#p`, `#K`, `#I`, …) via the normalized `event_tags` table. Both lowercase and uppercase single-letter tag filters are supported. |
 | `events_event_created_at_index`              | Time-range scans (`since` / `until`).                                                                    |
 | `events_event_kind_index`                    | Kind-only filters and purge kind-whitelist logic.                                                        |
 
@@ -108,6 +108,17 @@ npm run db:verify-index-impact
 
 The hot-path index migration (`20260420_120000_add_hot_path_indexes.js`) uses `CREATE INDEX CONCURRENTLY`, so it can be applied to a running relay without taking `ACCESS EXCLUSIVE` locks on the `events` or `invoices` tables.
 
+## Tag filter scope
+
+Subscription filters support single-letter tag filters using the `#<letter>` key syntax (NIP-01). Both lowercase (`#a`–`#z`) and uppercase (`#A`–`#Z`) variants are accepted.
+
+| Scope | Examples | Usage |
+|-------|---------|-------|
+| Lowercase (`#a`–`#z`) | `#e`, `#p`, `#a`, `#k` | Standard NIP-01 tag queries; parent-level references in NIP-22 comment threading |
+| Uppercase (`#A`–`#Z`) | `#E`, `#P`, `#A`, `#K`, `#I` | Root-level references in NIP-22 comment threading and other NIPs that use uppercase to distinguish root vs. parent scope |
+
+**NIP-22 comment threading (kind 1111):** NIP-22 comment events use lowercase tags (`#e`, `#a`, `#i`, `#k`) to reference the immediate parent and uppercase tags (`#E`, `#A`, `#I`, `#K`) to reference the root item. Filters must therefore accept both cases to allow clients to query the full comment thread hierarchy. For example, to find all comments on a root event: `{"kinds":[1111],"#E":["<root-event-id>"]}`, or to find comments of a specific root kind: `{"kinds":[1111],"#K":["1"]}`.
+
 # Settings
 
 Running `nostream` for the first time creates the settings file in `<project_root>/.nostr/settings.yaml`. If the file is not created and an error is thrown ensure that the `<project_root>/.nostr` folder exists. The configuration directory can be changed by setting the `NOSTR_CONFIG_DIR` environment variable. `nostream` will pick up any changes to this settings file without needing to restart.
@@ -163,6 +174,7 @@ The settings below are listed in alphabetical order by name. Please keep this ta
 | nip05.mode                                  | NIP-05 verification mode: `enabled` requires verification, `passive` verifies without blocking, `disabled` does nothing. Defaults to `disabled`. |
 | nip05.verifyExpiration                      | Time in milliseconds before a successful NIP-05 verification expires and needs re-checking. Defaults to 604800000 (1 week). |
 | nip05.verifyUpdateFrequency                 | Minimum interval in milliseconds between re-verification attempts for a given author. Defaults to 86400000 (24 hours). |
+| nip45.enabled                               | Enable or disable NIP-45 COUNT handling. Defaults to true. |
 | paymentProcessors.lnbits.baseURL            | Base URL of your Lnbits instance. |
 | paymentProcessors.lnbits.callbackBaseURL    | Public-facing Nostream's Lnbits Callback URL. (e.g. https://relay.your-domain.com/callbacks/lnbits) |
 | paymentProcessors.lnurl.invoiceURL          | [LUD-06 Pay Request](https://github.com/lnurl/luds/blob/luds/06.md) provider URL. (e.g. https://getalby.com/lnurlp/your-username) |

README.md

@@ -61,6 +61,7 @@ NIPs with a relay-specific implementation are listed here.
 - [x] NIP-33: Parameterized Replaceable Events
 - [x] NIP-40: Expiration Timestamp
 - [x] NIP-44: Encrypted Payloads (Versioned)
+- [x] NIP-45: Event Counts
 - [x] NIP-62: Request to Vanish
 
 ## Requirements

package.json

@@ -18,7 +18,8 @@
     28,
     33,
     40,
-    44
+    44,
+    45
   ],
   "supportedNipExtensions": [
     "11a"

resources/default-settings.yaml

@@ -53,6 +53,8 @@ nip05:
   domainWhitelist: []
   # Block authors with NIP-05 at these domains
   domainBlacklist: []
+nip45:
+  enabled: true
 network:
   maxPayloadSize: 524288
   # Uncomment only when using a trusted reverse proxy and configuring trustedProxies.