Damus
jb55 profile picture
jb55
@jb55
Using NIP-SNS for private team data. Its like giftwrap+PNS.

- Zero metadata on envelope (no tags).

- Knowledge of the team key allows you to seal posts to the team channel

- Seals are member-signed, nip44 encrypted inner-envelopes with rumors inside.

- Adding team members is just sharing your team key via giftwrap. No need to rewrap existing notes to new members.

- Members posting SNS notes under this channel reveals no info to relays.

- Member sealed notes can’t be leaked to relays just like giftwraps.

- it’s basically giftwraps without the p tag, because the p tag is already known from the team pubkey

- its an encrypted channel where members can share notes to each other!

- Key rotation is just giftwrapping the new team key (generation+1) to the new member set (allows you to remove members)

Added support for this to nostrdb so it will automatically unwrap these.

Going to use this for most of the shared private data in notedeck (shared issue boards, shared agent sessions, notion/obsidian style notes, etc)

Cheers! 🍻

https://github.com/damus-io/notedeck/blob/master/docs/nip-sns-sealed-shared-storage.md
192❀️10πŸ‘€2πŸ™‚1πŸ€™1
⚑ Dee Kay ⚑ · 2w
Is this meant for a tight team of knwon members since key-shares go direct to the newcomer and never touch the channel?
3mily · 2w
Keep on building big horse 🐎
Constant · 2w
So...its this concord protocol thing?
ngmi · 2w
Sounds super cool. We use armada atm for most stuff, obviously not optimal. This could be a great addition. Any ETA?
JSKitty · 2w
This is pretty much Concord Protocol, adopted by nostr:npub1hrujuc08r4zcdtn0u6ts7u7apldcjqgftz0z7stmaaz9hwaf9jxs66f3yh , Armada, Amethyst, and a bunch others, come join us in developing it! πŸ™ https://github.com/concord-protocol/concord/