Nostr Web Client

For some Nostr applications, it is important to have data that can be verified, but that you don't want to be published (eg SIGit agreements, medical records, or internal application data). One way to achieve this is by sealing (kind 13) but this has some drawbacks - such as the fact that only the sender and receiver can decrypt / verify the content.

NIP-59 suggests that removing the signature is one way to prevent events from being published. But this also stops it from being verified.

With this in mind, we would like to #asknostr for feedback on the following idea.

Using negative kind numbers for private data

Negative kind numbers MUST NOT be published to relays, and relays MUST NOT accept negative kind numbers

Thoughts?

Gigi 1y ago

You've been working on medical data nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z, right? Any thoughts on negative kinds?

Reply to this note

Please Login to reply.

Discussion

jb55 1y ago

Ive been personally using negative numbers to sign things, i think its a decently elegant solution

Vitor Pamplona 1y ago

As of now, kind is an unsigned int. So negative numbers cannot exist until we change how nostr encodes event kinds, which might change everything.

But GiftWrapped & Sealed medical data is a thing. We have been doing a bunch of experiments. It's hard to crack the growth of it, but definitally possible.

Nostr Dev Team 1y ago

Well that answers that, thanks!