NIP-12

Generic Tag Queries

MergedBehaviour

Deprecated: merged into NIP-01. It introduced filters on any single-letter tag, such as {"#t": ["nostr"]}.

Status: Folded into another NIP; kept only so old links work.
Last changed: Nov 16, 2023

Try it

Edit the form or the JSON: both stay in sync, the badge says whether the result is valid, and tapping any field explains it.

Examples

Form

REQ Client → relay

subscription_id

Subscription id chosen by the client.
filter · Edit as JSON
Filter with #<letter> keys and lists of values.

A NIP-01 REQ whose filters use #<letter> keys.

How this NIP works

Step 1 of 3

Now part of NIP-01

Every relay that speaks NIP-01 supports these filters; this NIP only remains for history.

Who does what

Step 1 of 5

Ready. Press play or step forward to send the first message.

Text version

#	From	To	Message
1	Client	Relay	Ask for kind 1 events tagged t=nostr.
2	Relay	Relay	The relay looks up its index of single-letter tag values.
3	Relay	Client	Bob's note has ["t", "nostr"], so it matches.
4	Relay	Client	All stored matches were sent.

In the course

No course chapter covers this NIP yet. The editor above is the quickest way in.

Replaced by

NIP-01 Basic protocol flow description
Tag filters are defined in NIP-01 now.

Specification

Specification text is quoted in English from the nostr-protocol/nips repository. Our explanations and the interface are translated. Source on GitHub at commit 0046368

Read the spec11 words, quoted from the repository at commit 0046368.

Moved to NIP-01.

At a glance