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
Doing so subverts some of the protection intended by public data encryption. For example, currently address hash160s are hashed again using sha256 and used as bucket keys. While this prevents being able to go from bucket key (sha) -> address, if an attacker knows an interesting address and wanted to determine whether this wallet controlled it or not, this is as simple as looking up sha256(hash160) in the db.
Instead, keys should be crypted with the public crypto key, so if public encryption is used, this attack/privacy leak is not possible.