jorge
Jorge

Public Key

npub1xpq2h8xgevveqzukrwz2l7w2uyz4emm0h0m2e0r8jepvj2pkh9dszpjjl7

NIP-05 Address

Profile Code

nprofile1qqsrqs9tnnyvkxvspwtphp90l89wzp2uaahmha4vh3nevskf9qmtjkcppamhxue69uhkummnw3ezumt0d5q3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k706nt8w

Publishing to

nostr.mom

relay.damus.io

nos.lol

Author Public Key

npub1xpq2h8xgevveqzukrwz2l7w2uyz4emm0h0m2e0r8jepvj2pkh9dszpjjl7

Show more details

Last Notes

2026-10-25 08:03:04 UTC

- reply

This is gonna be unpopular but I need to say it anyway. There are legit reasons for using multiple keys:
1. I want to avoid a single point of failure. In case my "twitter" nsec is ever compromised, I don't want my whole Nostr life gone.
2. If app ownership needs to be transfered to someone else, how would I do it when everything is tied to my personal omni-key?
3. Imagine a company where many people are involved in the development/deployment of the app(s). Which key should it use? The one of the CEO? Or the most popular employee's one? It makes perfect sense to me to have app-specific keys.
4. Web of trust is nice but how does it work for people who are just starting? Even their most popular npub doesn't have enough reputation.
5. Similarly to #4, some people might not even be beginners but just aren't very active on social networks. Same impact for their npub.