We’ve developed a two-pronged model. Strict mode means relays must implement the NIPs and their kind numbers. From the panel, you can select which kind numbers you want enabled. Unlimited mode means that relays will store any kind numbers. Clients do the verification. Relay operators can blacklist certain kind numbers in unlimited mode if they want to narrow it down a bit. Check out the demo panel at:

H.O.R.N.E.T Storage

All-In-One Nostr Relay with Dashboard Panel🌐 Host Files as Scionic Merkle Trees or Blossom Blobs🌸🌳

Check out the relay:

GitHub

GitHub - HORNET-Storage/HORNETS-Nostr-Relay: Nostr Relay with Dashboard🌐 Choose Paid, Public or Invite-Only Mode👥 Self-Host Your Posts and Code📂

Nostr Relay with Dashboard🌐 Choose Paid, Public or Invite-Only Mode👥 Self-Host Your Posts and Code📂 - HORNET-Storage/HORNETS-Nostr-Relay

Would be interesting to see a breakdown of relay implementations, I'd guess most use strfry which had its latest commit last year @sandwich

According to legacy nostr.watch, `nostr-rs-relay` still dominates. https://nostr.watch/relays/statistics But this **only includes `wss` relays, not `ws` or `onion`**. I'm monitoring via NIP-66 for `wss` and `ws` but not `onion` yet, could be calculated pretty easily by anyone...