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
It may be helpful to break up attacks and/or countermeasures based on when privacy breaches actually take place.
For example, a change output might be attributed to you as a sender based on the transaction the output belongs to, or based on future transactions due to behavior of you and/or your counter-party.
There are related countermeasures for both of these. Since users tend to stick with the same wallet and wallet client behavior tends not to change drastically over time, the countermeasures will often apply to both times of potential privacy breach, but this is not necessarily always the case.
The text was updated successfully, but these errors were encountered:
Yes, definitely. I also expect that it would be a high entropy approach, though.
For reference, oxt.me provides temporal analysis on a per-address basis, but the same could easily be done for clusters of addresses: https://oxt.me/address/tiid/133522641
Proposed attack (wording needs to be refined): Identify ownership of change output based on temporal patterns of output spends and how they coincide with temporal patterns of clustered addresses.
For reference, oxt.me provides temporal analysis on a per-address basis, but the same could easily be done for clusters of addresses: https://oxt.me/address/tiid/133522641
Actually, OXT provides the same analysis on a per-entity basis too. :)
It may be helpful to break up attacks and/or countermeasures based on when privacy breaches actually take place.
For example, a change output might be attributed to you as a sender based on the transaction the output belongs to, or based on future transactions due to behavior of you and/or your counter-party.
There are related countermeasures for both of these. Since users tend to stick with the same wallet and wallet client behavior tends not to change drastically over time, the countermeasures will often apply to both times of potential privacy breach, but this is not necessarily always the case.
The text was updated successfully, but these errors were encountered: