I recall using a GPG connected network of computers to verify the authenticity of a resource public key. Authenticating purpose, potential site and email address association. Clients then would authenticate, replicate, distribute the list. ls there a "signed" block list (Merkle root) or repository of either suggested "fake" or proven authentic Nostr pub keys. A list the Nostr client after verification can reference and use as a live filter flagging any potential harmful pub key references? eg. "filter known scam accounts". I find the manual checking pub keys process with site lists cumbersome.
Does this already exist in existing clients? #nostr #bitcoin
ChainsLight / TG
npub1zy…8ykjg
2025-04-02 16:38:31
Author Public Key
npub1zya050rzhrvwuwtmfxn8fpuuw7zczzr73wu5yv6xl0j9hv4rahssk8ykjgPublished at
2025-04-02 16:38:31Event JSON
{
"id": "e84468f0577df4f393baedabfa48535d3b321a9bebecda074b94646c8213b6f7",
"pubkey": "113afa3c62b8d8ee397b49a674879c778581087e8bb9423346fbe45bb2a3ede1",
"created_at": 1743611911,
"kind": 1,
"tags": [
[
"t",
"nostr"
],
[
"t",
"bitcoin"
]
],
"content": "I recall using a GPG connected network of computers to verify the authenticity of a resource public key. Authenticating purpose, potential site and email address association. Clients then would authenticate, replicate, distribute the list. ls there a \"signed\" block list (Merkle root) or repository of either suggested \"fake\" or proven authentic Nostr pub keys. A list the Nostr client after verification can reference and use as a live filter flagging any potential harmful pub key references? eg. \"filter known scam accounts\". I find the manual checking pub keys process with site lists cumbersome.\nDoes this already exist in existing clients? #nostr #bitcoin \n",
"sig": "bad9a9cb53013a3033b82b5a89ab071536f3687829e78a0a225bb3130a8a70d468668f82a003cb2233ccb74d1d89b632071832b88ad7ed515797810fc558146b"
}