Once I finish NIP-17 support I think I'm going to start looking into nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk double ratchet NIP. It requires the client to keep state, but If I remember correctly it requires a lot less decryption requests from the users pubkey since it uses rotating random keys

https://github.com/nostr-protocol/nips/pull/1813

nostr:nevent1qvzqqqqqqypzqfngzhsvjggdlgeycm96x4emzjlwf8dyyzdfg4hefp89zpkdgz99qyf8wumn8ghj7mn0wd68yat99e3k7mf0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqh76z8vrufl3f2x6r3w2tgzm53uvmguugg8s03v8e2d26z7f7ta7sfvcnpm

Reply to this note

Please Login to reply.

Discussion

nostr:nprofile1qyfhwumn8ghj7anpw4k8gtnfwf5hxtn5duqzq3frhevd89d3kxt2nwxg9vpck6y4evptdq7scff6j4gx3kapltxs8cp55g is there any documentation available on how you implemented this? It would be great if there were a NIP detailing double ratchet message encryption.

Ok I see you made a JS library for doing this, thanks:

https://github.com/mmalmi/nostr-double-ratchet