nwcprovider only advertises nip04 in its kind-13194 info event. Most clients (Alby SDK, Damus, Amethyst, Primal etc.) prefer nip44_v2 and fall back to nip04 with a deprecation warning.
Would be good to advertise nip44_v2 and implement the matching encrypt/decrypt paths. NIP-44 v2 needs HKDF-SHA-256 + ChaCha20 + HMAC-SHA-256, all available via the cryptography dep that LNbits already pulls in (same approach pynostr's existing encrypt_message takes for AES-CBC).
nwcprovider only advertises
nip04in its kind-13194 info event. Most clients (Alby SDK, Damus, Amethyst, Primal etc.) prefernip44_v2and fall back tonip04with a deprecation warning.Would be good to advertise
nip44_v2and implement the matching encrypt/decrypt paths. NIP-44 v2 needs HKDF-SHA-256 + ChaCha20 + HMAC-SHA-256, all available via thecryptographydep that LNbits already pulls in (same approach pynostr's existingencrypt_messagetakes for AES-CBC).