Replying to Avatar PABLOF7z

Introducing Kind0.io

A NIP-41 proof of concept.

What is NIP-41? A simple way to migrate from a compromised key into a new key while signaling to your followers what happened.

It works by whitelisting your next npub ahead of time and timestamping it to something that can order events chronologically (ie the Bitcoin blockchain)

When a key is lost or compromised the new key can sign a migration event, timestamp it as well and then clients can choose to act on it.

For more discussion on this, listen to nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8 's recent Bitcoin.review where they go over the why and the tradeoffs.

Here’s is a very rough video of a very rough tool to implement this whole flow.

This is not the last word on key management; there is still a lot of work to be done, but this is a small step in the right direction that will allow us to migrate the existing nostr social graph to more cryptographically complex schemes for whoever wants to do that.

https://cdn.satellite.earth/3f1bf208810669bd3a9eaa7a0b9c7ff2d75d1abc893a6b2db8463d6f4923d083.mp4

Avatar
Orange Crush 2y ago

Could a slight variation in this theme be used to designate disposable child keys for private messaging?

As illustration, I DM someone a child key w/ validation which opens a private message channel where they reply to that validated child key with a message and a new child key & validation of their own and we continue replying — each time designating/validating a new key for reply. As the messages are encrypted to the users disposable keys, no one need know that the child keys exist or that we have continued our conversation.

Reply to this note

Please Login to reply.

Discussion

No replies yet.