You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have days researching about replace nip04 with nip44 because I heard it's an important upgrade, so I've been reading and playing a bit with it trying to understand it.
My final thoughts are we will implement it but with a low priority, nip44 improves the cryptography, yes, but the issues that concerns us are still there, on an nip44 event we still shows the origin and the destiny pubkey, so anybody can just monitorize Mostro's pubkey and know who are operating on p2p.
We still covers this case with ephemeral pubkeys and in the future we can think on running some kind of servers that send/receive messages to Mostro from brand new pubkeys to ofuscate a bit more Mostro's and make even more difficult surveillance
Another con we can find is nip07 extension getalby still don't support nip44, probably not much of them support it yet.
I was reading about the nip17 that you mentioned a few days ago in the telegram group, now wouldn't it be an even better option than the nip44? because the metadata is hidden from the public
It must replace nip 04 which is used to establish communication between Mostro and both parties
The text was updated successfully, but these errors were encountered: