Add mention of the Janus attack to subaddresses article

This commit is contained in:
Piotr Włodarek 2021-01-20 17:01:52 +01:00
parent 962f29b689
commit 99ea3072d0

View file

@ -14,9 +14,11 @@ This use case overlaps with integrated addresses. Subaddresses are generally pre
## Prevent payer from linking your payouts together ## Prevent payer from linking your payouts together
To prevent the payer from linking your payouts together simply generate a new subaddress for each payout. To prevent the payer from linking your payouts together simply generate a new subaddress for each payout.
This way services like [Shapeshift](https://shapeshift.io) wouldn't know it is you again receving Monero. This way specific service (like anonymous exchange) that sends you Monero won't (easilly) know it is you again receving Monero.
Note it won't help if you have an account with the service. Then your payouts are already linked in the service database, regardless of Monero. The exception to this is when a service (or group of colluding services) decides to actively attack you, one address at the time, with the so cold [Janus attack](https://web.getmonero.org/2019/10/18/subaddress-janus.html), which risks them losing funds. If you need perfect unlinkability of your receivables, the only solution remains to use a separate seed (separate Monero wallet).
Also, note it won't help if you have an account with the service. Then your payouts are already linked in the service database, regardless of Monero.
## Group funds into accounts ## Group funds into accounts