Skip to content
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

Help avoid leaking identifying information about counterparties for bank transfers requiring contact name #1544

Closed
nothingmuch opened this issue May 16, 2018 · 1 comment
Assignees

Comments

@nothingmuch
Copy link

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.

@cbeams
Copy link
Member

cbeams commented Jun 6, 2018

Closing as moved to bisq-network/payment-methods#12.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants