The latest nak v0.17.4 implements support for managing decoupled encryption keys that fix NIP-17 completely, as per
See this amazing infographic that explains how it works:
If you call `nak dekey --sec <whatever>` you'll generate a new decoupled encryption key that is stored locally and announced with a kind:10044 event. After that if you use `nak gift wrap` or `nak gift unwrap` that key will be used by default (when wrapping both keys will be tried if possible).
If you run `nak dekey` on another device/client (or with another --config-path) that other device will announce itself as in need of the decoupled key, then you can run `nak dekey` again on the first device and it will automatically send the key to the second -- and like that the key is shared among all your devices.
Call `nak dekey --rotate` to discard the current decoupled key and generate and announce a new one.
Download here: 
GitHub
nip4e: decoupling encryption from identity by fiatjaf · Pull Request #1647 · nostr-protocol/nips
this is inspired by MLS, but much simpler, and definitely not trying to be a group communication system, but only a way for users to encrypt things...
If you call `nak dekey --sec <whatever>` you'll generate a new decoupled encryption key that is stored locally and announced with a kind:10044 event. After that if you use `nak gift wrap` or `nak gift unwrap` that key will be used by default (when wrapping both keys will be tried if possible).
If you run `nak dekey` on another device/client (or with another --config-path) that other device will announce itself as in need of the decoupled key, then you can run `nak dekey` again on the first device and it will automatically send the key to the second -- and like that the key is shared among all your devices.
Call `nak dekey --rotate` to discard the current decoupled key and generate and announce a new one.
Download here: GitHub
Release v0.17.4 · fiatjaf/nak
a command line tool for doing all things nostr. Contribute to fiatjaf/nak development by creating an account on GitHub.