Post
Topic
Board Announcements (Altcoins)
Re: [ANN] [KEY] KeyCoin | Fair Launch | Daily Updates | 8/9 Status Update
by
Megalodon
on 10/08/2014, 15:37:43 UTC
"Two examples of KeyCoin deanonymization with new deanonymizer program":
http://crypto-news.tumblr.com/post/94329216643/two-examples-of-keycoin-deanonymization-with-new
Seriously are you still on that? Tracking an anonymous transaction when there are practically no other transactions moving about isn't exactly difficult because it's not hard to make an educated guess as to the source transactions by looking back a few blocks and taking fees into account along the way. Anyone could do this by examining the block explorer. (You don't need a program to come to an educated guess).
These transactions seem to be fairly old and are from the good old times when there were at least some transactions in the blockchain
However, if I were to send several anonymous transactions of equal amounts, all from unique wallets, all within a short space of time there is no way in hell this program (or anyone trying to decipher it manually) would be able to come to an educated guess because there would be too much transaction congestion to figure out which transactions came from which wallet or end up at which destination.
That's true. If several wallets send the same amount at almost the same time, then this method won't work 100%.
However, this method still gives you list of the addresses that sender exerts at least some control over them (it owns private keys or it has the power to use them to create "fake" transactions). The "working" anonymity implementation should not allow even such "guesses" - such guesses are more than enough for someone (law enforcement etc.) to track you.
And this method could probably be modified to distinguish "fake" transactions from the "real" ones based on the the way how "real" transactions look in the blockchain (for example, "real" transactions use inputs that are outputs of the transactions in the same block, one could also "color" some coins and send them through the mixer etc.).

But the devs will have to prove that such attacks don't and can't work (even in the case when - for example - someone decompiles precompiled binaries etc.).

I'll tell you what I'll do. I'm going to set up a test for you with 6 brand new 100% isolated wallets, 5 of which will be the starting point for 5 anonymous transactions of equal value. The other will be a receiving wallet with 5 receiving addresses (one for each incoming transaction).
You can then test the program on the 5 incoming txids/block heights and see if you can figure out which wallet initiated any of them. I guarantee neither you or the program will be able to figure it out which addresses sent coins to which addresses. If you do it will be pure luck.

I can't run this program because I'm currently on linux box and I'm not going to mess with mono.
I don't understand what are you trying to prove. If you send same amount at the same time, then this program may find the wrong addresses. There's no need to prove this because it can be seen from source code.
However, it can (with modifications) find all these addresses that you control. This is enough for deanonymization.


I lol'd, you haven't even tested it yourself, now you're saying it needs modifications to work lmao. Thanks for showing everyone how full of shit you are. Now gtfo, key devs will deliver their promises soon enough. We need a moderated thread to ban this blabbering buffoon.