Gm @Pip the WoT guy can you pls post the raw leaked nsecs on your website sir, I think users need that concrete evidence before abandoning their nsecs, perhaps with a quick login to verify type thing
Login to reply
Replies (7)
+1
+1
+1
+1
I am doing something better already.
When calling the VerifyReputation endpoint you get a proof of leak.
It's a signature using the leaked nsec, of the message "vertex-proof-leak:<pubkey>"
All documented here:
Public nsec lists is really a bad idea.
If one doesn't know how to check the signature, then can use npub.world
View quoted note →
Verify Reputation
Verify Reputation returns reputation information about a pubkey, including a list of pubkeys who follow it sorted by an algorithm. This service pow...
I do want to know this before I leave my Nsec. as far as I know, I haven't put it anywhere else, than in amethyst. And nothing strange has happened at all Jan 2026? Curious how and what you read? @Pip the WoT guy 👀👌
Your nsec appeared in two events:
1. Profile badge signed by you:
Profile badges signed by @Derek Ross, since it's referencing your event by the "d" tag, which is the nsec
31 Jan 2026 is the same date as other leaks. Maybe there was some bug in a client that supports Profile Badges (?)
Nostr Event 30009 - Badge Definition
Nostr Event 30008 - Profile Badges