https://jumble.social/ has launched DM support, implemented as NIP-17 DMs on top of NIP-4e (https://github.com/nostr-protocol/nips/blob/per-device-keys/4e.md).
At the moment only coop supports this protocol, so communication is currently only possible between Jumble and coop users.
Benefits of NIP-4e (decoupling the encryption key from the user's identity key):
- The encryption key can be rotated regularly, reducing the risk that a compromised or lost key exposes historical messages
- Encryption and decryption no longer require the user's identity key. Previously, using DMs with a bunker remote signer resulted in a poor user experience
Jumble
npub17n…7fyh9
2026-04-15 02:00:11 UTC
Author Public Key
npub17n4cuc4d6y6qh89dekvxrenfkt5s0n49xns00uavjaxpr36c55dq87fyh9Seen on
wss://relay.damus.ioPublished at
2026-04-15 02:00:11 UTCEvent JSON
{
"id": "0bf1be31e4a2e43db6e1b7febd46ac2fc6bde9a2e723da0352f9a91d1af323f5",
"pubkey": "f4eb8e62add1340b9cadcd9861e669b2e907cea534e0f7f3ac974c11c758a51a",
"created_at": 1776218411,
"kind": 1,
"tags": [
[
"client",
"jumble"
]
],
"content": "https://jumble.social/ has launched DM support, implemented as NIP-17 DMs on top of NIP-4e (https://github.com/nostr-protocol/nips/blob/per-device-keys/4e.md).\n\nAt the moment only coop supports this protocol, so communication is currently only possible between Jumble and coop users.\n\nBenefits of NIP-4e (decoupling the encryption key from the user's identity key):\n\n- The encryption key can be rotated regularly, reducing the risk that a compromised or lost key exposes historical messages\n- Encryption and decryption no longer require the user's identity key. Previously, using DMs with a bunker remote signer resulted in a poor user experience",
"sig": "3ebe4109c4c151d27c133e60167b8ac05818a37ae72fa1a8a2c672c694fdd2721cda1d6b06f698d0a9513eaf280dbd407124136d37ce1528b180a2cd9308b896"
}