The methodology is in the post and everything is open source — anyone can reproduce it. This dataset isn't public because at least 38 people don't know their key is exposed. Future analyses will release everything. Happy to share privately for legitimate research.

Filtering the noise from Nostr's nsec leak data https://bigbrotr.com/blog/exposed-nsec-analysis/

There's no truly effective solution if you send your nsec online or if it gets exfiltrated. First lesson in cryptography

UPDATE: we deployed a DVM for this. Send a Kind 5300 event signed with your keys and it tells you (NIP-44 encrypted, only you can read) if your nsec has been exposed. Source and instructions: https://github.com/BigBrotr/nsec-leak-checker

We analyzed 40M events archived by BigBrotr and found 16,000+ valid nsec keys published in plaintext. 90% republished by a single bot. The rest: users confusing nsec with npub, AI agents leaking credentials in logs. https://bigbrotr.com/blog/exposed-nsec-analysis/ #nostr #security #bigbrotr

Agreed. BigBrotr API is live at api.bigbrotr.com/docs if you want to take a look — Several endpoints covering relays, events, metadata, and pre-computed analytics.

great work on Pensieve, the retention cohort analysis is really clever. We took a different path on event archiving — BigBrotr crawls each relay's full history with completeness verification and tracks exactly which events live on which relays. Same goal, different trade-offs.

BigBrotr vs Pensieve — a technical deep dive into two open-source approaches to indexing Nostr. How do you ensure you're not missing events? How do you decide which relays to connect to? Same network, very different answers. https://bigbrotr.com/blog/bigbrotr-vs-pensieve/ #nostr #bigbrotr #pensieve

Easier monitoring means a more transparent and healthier network for everyone.

More like limitless and complete streaming from any relay you can subscribe to.

Cc

this might help for your Vertex analytics — I'll DM you the full dataset.