The ciphertext being decrypted in his screenshot is a NIP-04 one, notice it ends with an "?iv=..." parameter.

Reply to this note

Please Login to reply.

Discussion

Thanks for catching that. This will help improve the detection logic in these random cases.

What I'm saying is that the app that created this backup encrypted the seed with NIP-04 instead of NIP-44. It was a bug there. Just fix that, don't go around trying to detect edge cases.

Right, what I mean by edge case is that the app that created the backup was an earlier proof-of-concept that few people except myself and nostr:npub1vxd0dfst8ljvwva2egrpc53ve8ru78v8aaxfpravchkexmfmmu3sqnrs50 have used before, meaning the chance of other users experiencing this issue is low. It allowed both encryption methods because one of the signer extensions tested did not support NIP44, so our import function needs just to detect this. That's what this fix will cover.