Jack Riddle[Any/All]

Profile picture drawn by Paws and Claws and licensed under the Creative Commons Attribution Sharealike 4.0 International license(cc-by-sa 4.0)

  • 2 Posts
  • 228 Comments
Joined 9 months ago
cake
Cake day: May 1st, 2025

help-circle









  • As I understand it, this happens cryptographically. Send keys can be added to form a larger key, which gets used to sign the pool of transactions. Because the signature used your key as well, the recipient can verify that they have received your coins(from a pool you signed). The important part is that it is impossible to tell who signed what part of the pool, just that one of the people in the pool did. Because all money is pooled together and sent at the same time, it is not possible to read from the amounts sent which transaction belongs to who.


  • I believe the way they deal with this is by having the recipient create a one-time address for every sender, so it is not possible to recognize patterns between senders and recipients. Another thing is that every wallet has two associated keys. There is a “spend key”, which is a write-only key that can spend money from the wallet, and a “view key”, which can be used to view the contents of the wallet. You can publish the view key if you want that to be public information, but you don’t have to.



  • You might be right, I have not followed xmr closely. You might also notice that this vulnerability is unlikely to deanonimise you, but the point was more that it is a mistake they shouldn’t have made. Their last audit looks fine, though it was made by a blockchain auditing company which I don’t know. I don’t think there is much harm in using xmr for this, groups who would be capable of exploiting vulnerabilities in this kind of project are unlikely to do so, unless an issue of national security becomes associated somehow


  • xmr is a cryptocurrency which aims to make reading transactions from the chain impossible. Iirc the main mechanism of this is that they bundle a lot of transactions together and send out coins from that pool only once it is large enough, without preserving each specific coin. This repeats for a few proxies. You could trace a coin from origin to endpoint, but this would be pretty much useless as you cannot know whether the endpoint was the intended one or not.