NIP-76: Private Channels - Draft 2 - Includes Client Implementation and Tool kit library

[d-krause]

Overview

• Each Private Channel message is encrypted with a unique key, signed with another unique key, and reveals no identifying information about the author or the intended recipient.
• Event signatures are verified through channel chainCode key derivation.
• Channel Keys are exchanged via event pointer strings, encrypted (by password or computed secret), which are the keys to a single nostrEvent called an Invitation.

First Client Demo at https://nostr-nip76.web.app/private-channels

For those of you not familiar with blockcore-notes, just login with a private key (demo keys provided in the link), or create an entirely new profile. blockcore-notes prompts you for a password on each signing event. If you did not enter a password during account creation, just leave the password blank, and click OK.

Links

• nip76-tools (especially see HDKIndex.ts & content classes)
• Client DEMO at https://nostr-nip76.web.app/private-channels
• NIP-76 Pull Request

[sondreb]

Great work, thanks for this PR! Please fix the nip-76 reference and I'll test it locally.

[sondreb]

This is all great work!

Can this be adopted to also support extension and not private key in the app? The initPrivateChannels method is constructed to have access to private key and I mostly use Notes using extension.

We can extend the Blockcore Wallet extension with additional features that might be needed to improve the private channel user experience.

[d-krause]

@sondreb

Can this be adopted to also support extension and not private key in the app?

Sure. I will look into this. I need about a week to make the necessary changes.