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
In the UK faster payments only technically require a sort code and account number, but at least my bank also takes a name for the recipient, and saves this name as a contact.
In lieu of a name, one could paste the peer ID into the name field, but this allows the bank to correlate transfers with specific bisq users, by simply observing bisq nodes, so I think this should be discouraged, by providing an easier alternative.
To help users avoid inadvertantly divulging this information, an HMAC of the peer ID could be provided using the wallet key, resulting in a deterministic identifier that that is is unique for each sender and does not correlate with publicly available data on the bisq network itself.
The text was updated successfully, but these errors were encountered:
In the UK faster payments only technically require a sort code and account number, but at least my bank also takes a name for the recipient, and saves this name as a contact.
In lieu of a name, one could paste the peer ID into the name field, but this allows the bank to correlate transfers with specific bisq users, by simply observing bisq nodes, so I think this should be discouraged, by providing an easier alternative.
To help users avoid inadvertantly divulging this information, an HMAC of the peer ID could be provided using the wallet key, resulting in a deterministic identifier that that is is unique for each sender and does not correlate with publicly available data on the bisq network itself.
The text was updated successfully, but these errors were encountered: