From b2819a5013dc9548166d53ca1035d3e76bbe2df8 Mon Sep 17 00:00:00 2001 From: Logan Johnson Date: Fri, 9 Oct 2026 12:17:31 -0400 Subject: [PATCH] docs(nips): NIP-CL tag filters match before limit Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz> Signed-off-by: Logan Johnson --- docs/nips/NIP-CL.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/nips/NIP-CL.md b/docs/nips/NIP-CL.md index 5888cdb071..a88ab43977 100644 --- a/docs/nips/NIP-CL.md +++ b/docs/nips/NIP-CL.md @@ -112,6 +112,10 @@ Values in one tag filter combine with OR, as in NIP-01. So `"#t": ["workspace", "notes"]` finds channels with either label. To require a label and a creator, use `#t` and `#P` together. +The relay MUST match `#t` and `#P` before it applies `limit`, as NIP-01 +requires. A relay that reads the newest channel events first and matches tags +after can return a short or empty page while matching channels exist. + ## Trust A client that relies on these tags MUST check that the relay's key signed the