-
Notifications
You must be signed in to change notification settings - Fork 604
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NIP 47 using deprecated NIP 04 for encryption #1639
Comments
Already happening: #1531 |
@vitorpamplona why has this not been merged? |
As always, we need 2+ implementations to catch up to it before the merge. |
Alby says they implement this, doesn't Amethyst use nip 44 as well? |
Not as they wrote. We dynamically pick if it is NIP-04 or NIP-44 by the contents and not by the |
Given this is a security risk, wouldn't you rather we prioritized security? |
I wouldn't call it a security risk... But regardless of what it is, the NIP repo is a reflection of reality as opposed to an imposer of reality. We need lots of people to adopt specifications/changes before things get merged. |
Is it prudent to move to NIP 17 or NIP 44 for encryption, giving that NIP 04 leaks meta data?
The text was updated successfully, but these errors were encountered: