Replying to Avatar fiatjaf

The latest nak v0.17.4 implements support for managing decoupled encryption keys that fix NIP-17 completely, as per https://github.com/nostr-protocol/nips/pull/1647

See this amazing infographic that explains how it works:

If you call `nak dekey --sec ` 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: https://github.com/fiatjaf/nak/releases/tag/v0.17.4

date i say that in 2026 we'll finally have working DMs across many apps?

Reply to this note

Please Login to reply.

Discussion

We need a new DM spec then obviously 🤭

once a couple apps introduce NIP-EE, then we will get a new DM NIP. as is tradition.

More like 4 new dm nips 😂😂

sadly this is also very possible.

We're pretty close, I'm introducing another interoperability issue with decoupled keys so let's postpone that goal to 2027, but I think after that we will definitely be good.

i figured by 2027 we'd be moving to marmot and NIP-EE?