> If _my_ trust network wants "npub's mom + wife have the say over npub's new nsec", then the way _we_ use the protocol should allow for that.

You haven't responded to the meat of this part, but I think it's because I didn't explain it enough:

I think you're incorrect that the nsec is the ultimate source of identity. *I* am the ultimate source of identity, and the nsec is a layer I use to connect with other people. the same ultimate source of identity can use a subsequent nsec. operating at the nsec-layer then sure, nostr doesn't have an easy solution - but I'm operating a layer deeper, at the same layer as the ultimate human source of identity. That's why I'm saying I prefer "trust-maxxing".

Bob is a human and Alice is a human. They like communicating digitally. They both agree that Bob's human family and Alice's human family are great sources to rely on - in human land - for information about each other.

Bob loses his nsec. Bummer. But it's just a tool - Bob and Alice and their families still exist the same, human way. So Alice points some of her digital tools and particular parts of Bob's family's digital tools and she finds out about Bob's new nsec.

The problem has been solved at the deeper, human layer. Our tools are just along for the ride; and they answer to us, not the other way around.

I don't need a blockchain telling me what's true, and I don't want a protocol interrupting the way us humans prefer to interact.

Reply to this note

Please Login to reply.

Discussion

None of this changes the fact that what you are suggesting requires a hard fork. It can be done in a "nostr-like" way, but it requires a hard fork.

You leave me with no choice but to assume that you can't read or are unwilling to let what I'm saying into your head.

Show me where the fork is buried in what I'm saying.

"you precisely can have your most trusted people attest to your new key"

that's what you said, and that's exactly where the fork is buried.

Assuming of course that you want this attestation to have some technical bearing. If just for warmth and funsies then no fork is needed.

If you want the attestation to be technically meaningful here are few things that have to happen (and that do happen on Farcaster and elsewhere):

Everyone who followed your old key before timestamp x (time of theft) now follows your new key, automatic.

DMs sent to your old key can be read using your new key (and no longer read using your old key)

Posts from your old key show with your new avatar and handle to anyone browsing.

And 50 other things.

How are these things to happen Nostr? If what you’re suggesting is just a nostr-native alternative to an adding your NIP05 to your new key then we already know what a non-solution that is. And if you want those things above to happen then you don't need a blockchain per se but you need a hard fork.

oh, that's where our miscommunication is. why did this take so long to get to?

i don't require that whole list of stuff. i just want to know with some confidence if someone has a new npub.

Ah okay, fair enough, though I'm not sure that's so much of a value add. The real issue is that normies will never accept a network where if you lose control of your account the best you can do is let everyone know you're starting again completely from scratch at some new account.

the expectation that you can somehow sort things out after a hack and not lose all of your history is far too engrained.

i do want it to have technical bearing, but not beyond what the protocol currently supports. and this is already much more than in view:

https://straycat.brainstorm.social/about-trusted-assertions.html

we're basically there.

If I lose this nsec or it gets compromised I think I'm done here. I may use nostr but the bill cypher nym will be dead, any continued use would be under a different name.

#nostard thinks he's more than just an nsec