From a079d1c13e8f1b6be67a2c493decaf0cce8ed6af Mon Sep 17 00:00:00 2001
From: fiatjaf <fiatjaf@gmail.com>
Date: Thu, 10 Apr 2025 23:01:48 -0300
Subject: [PATCH] add hyperloglog filter for counting nip22 replies to any
 event.

---
 45.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/45.md b/45.md
index 4866e579..64481ea1 100644
--- a/45.md
+++ b/45.md
@@ -62,6 +62,7 @@ This NIP defines (for now) two filters eligible for HyperLogLog:
 
 - `{"#p": ["<pubkey>"], "kinds": [3]}`, i.e. a filter for `kind:3` events with a single `"p"` tag, which means the client is interested in knowing how many people "follow" the target `<pubkey>`. In this case the `offset` will be given by reading the character at the position `32` of the hex `<pubkey>` value as a base-16 number then adding `8` to it.
 - `{"#e": ["<id>"], "kinds": [7]}`, i.e. a filter for `kind:7` events with a single `"e"` tag, which means the client is interested in knowing how many people have reacted to the target event `<id>`. In this case the `offset` will be given by reading the character at the position `32` of the hex `<id>` value as a base-16 number then adding `8` to it.
+- `{"#E": ["<id>"], "kinds": [1111]}`, i.e. a filter for the total number of comments any specific root event has received. In this case the `offset` will be given by reading the character at the position `32` of the hex `<id>` value as a base-16 number then adding `8` to it.
 
 ### Attack vectors