Discussion
Cool, I am doing some with unique key per relationship and credentialing with those keys.
I am pretty sure there is a simple model underneath it all. Just haven’t figure it out yet. I think it’s something like generating a new npub, publish a kind xxxx event that this is the next npub.
Do we have good tools for hierarchical keys in Nostr? I think cold card has something but it is experimental still.
Not sure. We could do something similar to hkd with xpub, but I think the way to go is to publish events that point to the next valid npub. The trick is absolute ordering, so that if the original npub is compromised it can’t trick you to a bogus new npub.
original npub is master xpub? or original in an event? I think if npub gets compromised you would use a prior npub to announce/verify another new npub right?
Yeah, that the idea. The trick is the ordering of npubs so that (n+1) npub can announce that (n) npub is no longer valid. Similarly, someone can determine which events were valid and at which point they are invalid. Likely will require an open timestamp.
wouldn't there be a case where you could announce validity of npub (n) with (n-1) or any prior npub that is still good?
TBH, I haven’t thought it through completely. The question, I believe is specifying the validity period or state of a prior npub with something like “expired”. The problem is that the prior npub, if compromised, could specify a bogus n+1 pub. I think this is an open timestamp-like problem.
I'll check this out!
I was playing around with tbd which is jack Dorsey's project: https://developer.tbd.website/projects/ssi/
I am not sure where that is going TBH (pardon the pun). The leadership is too opinionated for my liking.