Analyzing XC mixer transaction by spamming.
Dev refused bounty.
lets start with this wallet that received a payment from the mixer
and we can walk through it backwards
I'll make it easy
this is the received mix transaction
http://cryptexplorer.com/tx/9bc580ea9b7ec69d53dbc28e9cc42f1ea810925137d6cc8c1011e904f7c18bac#o0
and you have address XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV - which made the payment
Okay so we know 2 things, XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV SENT a payment to XVrqrpe2ZDmykAnjcAHN6McbuDEjBZSvRZ
now - can that be tied back to the original transaction?
Hmm. I don't see any link back to the original transaction
maybe this will help
original transaction --->>>> which was sent TO this address "XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G"
http://cryptexplorer.com/address/XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G
so now I've revealed the transaction ^^^^^ with this data you should be able to find the original senders wallet ^^^^^^ then take that original senders wallet and search XVrqrpe2ZDmykAnjcAHN6McbuDEjBZSvRZ for the link
what is his point? the mixer address [output] used for this transaction is visible? well of course it yes, we aren't using quantum physics to send the coins, the issue is the mixers input address and original senders output address
since we provided the "last leg"of the TX, he can only back trace to the mixer itself, so far he has NOT Proven anything else
And chaeplin is adding that the mixer only uses one address for you, so once you know A, you can trace it. Which is what I said before. You have to assume A is known.
that is not how the mixer work's
The highlevel summary is this
The mixer tells the client to send coins to wallet b, however wallet C is used to send coins to the final user, there is NO link from wallet B to wallet C unless somebody manually moves the coins from C to B
seeing how the inputs at http://cryptexplorer.com/address/XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G are unspent, you can't - it is impossible
ah, somebody is spamming that address w/ transactions 0.003 and 0.03
It's me, sorry.
Now you get my point.
XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G is a NEW address aka wallet b.
> block 28768
>
block 28764 to block 28768
Simple python scripts analyze the transaction.
Dev wants hard link.
Now where is link between
XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV and XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G
Easy part.
Mapping.
If there is many transactions, We don't need this.
Block explorer will show the link.
x11coind sendmany 123 '{"XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G": 0.003, "XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV":0.003}
x11coind sendmany 123 '{"XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G": 0.03, "XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV":0.03}'
!
Watch out.
!
When coins is spent, hard link will appear.
Dev refused bounty.
http://cryptexplorer.com/address/XVrqrpe2ZDmykAnjcAHN6McbuDEjBZSvRZ
There is the wallet that received a mix transaction...
There is the wallet that received a mix transaction...
lets start with this wallet that received a payment from the mixer
and we can walk through it backwards
I'll make it easy
this is the received mix transaction
http://cryptexplorer.com/tx/9bc580ea9b7ec69d53dbc28e9cc42f1ea810925137d6cc8c1011e904f7c18bac#o0
and you have address XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV - which made the payment
Okay so we know 2 things, XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV SENT a payment to XVrqrpe2ZDmykAnjcAHN6McbuDEjBZSvRZ
now - can that be tied back to the original transaction?
Hmm. I don't see any link back to the original transaction
maybe this will help
original transaction --->>>> which was sent TO this address "XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G"
http://cryptexplorer.com/address/XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G
so now I've revealed the transaction ^^^^^ with this data you should be able to find the original senders wallet ^^^^^^ then take that original senders wallet and search XVrqrpe2ZDmykAnjcAHN6McbuDEjBZSvRZ for the link
what is his point? the mixer address [output] used for this transaction is visible? well of course it yes, we aren't using quantum physics to send the coins, the issue is the mixers input address and original senders output address
since we provided the "last leg"of the TX, he can only back trace to the mixer itself, so far he has NOT Proven anything else
So when you send from original address A to the receiving address D , it goes to the mixer B, the mixer makes a new address C to send the amount to the receiver D? And Chaeplin doesn't get only A?
And chaeplin is adding that the mixer only uses one address for you, so once you know A, you can trace it. Which is what I said before. You have to assume A is known.
that is not how the mixer work's
The highlevel summary is this
The mixer tells the client to send coins to wallet b, however wallet C is used to send coins to the final user, there is NO link from wallet B to wallet C unless somebody manually moves the coins from C to B
seeing how the inputs at http://cryptexplorer.com/address/XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G are unspent, you can't - it is impossible
ah, somebody is spamming that address w/ transactions 0.003 and 0.03
It's me, sorry.
Now you get my point.
XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G is a NEW address aka wallet b.
Code:
this is the received mix transaction
http://cryptexplorer.com/tx/9bc580ea9b7ec69d53dbc28e9cc42f1ea810925137d6cc8c1011e904f7c18bac#o0
http://cryptexplorer.com/tx/9bc580ea9b7ec69d53dbc28e9cc42f1ea810925137d6cc8c1011e904f7c18bac#o0
> block 28768
Code:
Hash9bc580ea9b7ec69d53dbc28e9cc42f1ea810925137d6cc8c1011e904f7c18bac
Appeared inX11Coin 28768 (2014-06-11 20:21:51)
Number of inputs2 (Jump to inputs)
Total in2.2
Number of outputs1 (Jump to outputs)
Total out2.19999
Size344 bytes
Fee0.00001
Raw transaction
Inputs
Index Previous output Amount From address ScriptSig
0 84da450271...:1 0.955069 XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV 71:3044...9b01 33:03eb...cd11
1 1c9523ca31...:1 1.244931 XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV 73:3046...9401 33:03eb...cd11
Outputs
Index Redeemed at input Amount To address ScriptPubKey
0 Not yet redeemed 2.19999 XVrqrpe2ZDmykAnjcAHN6McbuDEjBZSvRZ DUP HASH160 20:cb0b...0bf4 EQUALVERIFY CHECKSIG
Appeared inX11Coin 28768 (2014-06-11 20:21:51)
Number of inputs2 (Jump to inputs)
Total in2.2
Number of outputs1 (Jump to outputs)
Total out2.19999
Size344 bytes
Fee0.00001
Raw transaction
Inputs
Index Previous output Amount From address ScriptSig
0 84da450271...:1 0.955069 XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV 71:3044...9b01 33:03eb...cd11
1 1c9523ca31...:1 1.244931 XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV 73:3046...9401 33:03eb...cd11
Outputs
Index Redeemed at input Amount To address ScriptPubKey
0 Not yet redeemed 2.19999 XVrqrpe2ZDmykAnjcAHN6McbuDEjBZSvRZ DUP HASH160 20:cb0b...0bf4 EQUALVERIFY CHECKSIG
Code:
original transaction --->>>> which was sent TO this address "XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G"
http://cryptexplorer.com/address/XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G
http://cryptexplorer.com/address/XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G
>
Code:
XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G
Transaction Block Approx. Time Amount Balance Currency
042451b856... 28764 2014-06-11 20:13:06 0.396016 0.396016 XC
c9e67b0f21... 28764 2014-06-11 20:13:06 1.803984 2.2 XC
Transaction Block Approx. Time Amount Balance Currency
042451b856... 28764 2014-06-11 20:13:06 0.396016 0.396016 XC
c9e67b0f21... 28764 2014-06-11 20:13:06 1.803984 2.2 XC
block 28764 to block 28768
Code:
* ====> Working block height 28764 has 8 tx
* ====> Searchng XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G
tx: 2 percent 100 value 2.2
*===> block reached
*===> Searchng 28768 : diff : 4
*===> XVrqrpe2ZDmykAnjcAHN6McbuDEjBZSvRZ 2.19999 link is : XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G <----> XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV
* ====> Searchng XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G
tx: 2 percent 100 value 2.2
*===> block reached
*===> Searchng 28768 : diff : 4
*===> XVrqrpe2ZDmykAnjcAHN6McbuDEjBZSvRZ 2.19999 link is : XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G <----> XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV
Simple python scripts analyze the transaction.
Dev wants hard link.
Now where is link between
XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV and XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G
Easy part.
Mapping.
If there is many transactions, We don't need this.
Block explorer will show the link.
x11coind sendmany 123 '{"XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G": 0.003, "XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV":0.003}
x11coind sendmany 123 '{"XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G": 0.03, "XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV":0.03}'
!
Watch out.
!
When coins is spent, hard link will appear.
Code:
{
"account" : "123",
"address" : "XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV",
"category" : "send",
"amount" : -0.00300000,
"fee" : -0.00001000,
"confirmations" : 34,
"blockhash" : "1f986c7643436e328456252db9d0def76a97f9c2bae10e3ee73a9d427f8f149f",
"blockindex" : 2,
"blocktime" : 1402520792,
"txid" : "eaaa2b356d49c2b5953ecbe4ec112ba8a7fd94c73ee6181b7b837749eca5568e",
"time" : 1402520581,
"timereceived" : 1402520581
},
{
"account" : "123",
"address" : "XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G",
"category" : "send",
"amount" : -0.00300000,
"fee" : -0.00001000,
"confirmations" : 34,
"blockhash" : "1f986c7643436e328456252db9d0def76a97f9c2bae10e3ee73a9d427f8f149f",
"blockindex" : 2,
"blocktime" : 1402520792,
"txid" : "eaaa2b356d49c2b5953ecbe4ec112ba8a7fd94c73ee6181b7b837749eca5568e",
"time" : 1402520581,
"timereceived" : 1402520581
},
{
"account" : "123",
"address" : "XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV",
"category" : "send",
"amount" : -0.03000000,
"fee" : -0.00001000,
"confirmations" : 34,
"blockhash" : "1f986c7643436e328456252db9d0def76a97f9c2bae10e3ee73a9d427f8f149f",
"blockindex" : 3,
"blocktime" : 1402520792,
"txid" : "d191290208e31f6cf09c360b9f8bb671cea32dded456f00061a00496c8c60263",
"time" : 1402520778,
"timereceived" : 1402520778
},
{
"account" : "123",
"address" : "XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G",
"category" : "send",
"amount" : -0.03000000,
"fee" : -0.00001000,
"confirmations" : 34,
"blockhash" : "1f986c7643436e328456252db9d0def76a97f9c2bae10e3ee73a9d427f8f149f",
"blockindex" : 3,
"blocktime" : 1402520792,
"txid" : "d191290208e31f6cf09c360b9f8bb671cea32dded456f00061a00496c8c60263",
"time" : 1402520778,
"timereceived" : 1402520778
}
"account" : "123",
"address" : "XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV",
"category" : "send",
"amount" : -0.00300000,
"fee" : -0.00001000,
"confirmations" : 34,
"blockhash" : "1f986c7643436e328456252db9d0def76a97f9c2bae10e3ee73a9d427f8f149f",
"blockindex" : 2,
"blocktime" : 1402520792,
"txid" : "eaaa2b356d49c2b5953ecbe4ec112ba8a7fd94c73ee6181b7b837749eca5568e",
"time" : 1402520581,
"timereceived" : 1402520581
},
{
"account" : "123",
"address" : "XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G",
"category" : "send",
"amount" : -0.00300000,
"fee" : -0.00001000,
"confirmations" : 34,
"blockhash" : "1f986c7643436e328456252db9d0def76a97f9c2bae10e3ee73a9d427f8f149f",
"blockindex" : 2,
"blocktime" : 1402520792,
"txid" : "eaaa2b356d49c2b5953ecbe4ec112ba8a7fd94c73ee6181b7b837749eca5568e",
"time" : 1402520581,
"timereceived" : 1402520581
},
{
"account" : "123",
"address" : "XZvkTGD9hMiRuMByqCkHgRTNAu5J5fWnJV",
"category" : "send",
"amount" : -0.03000000,
"fee" : -0.00001000,
"confirmations" : 34,
"blockhash" : "1f986c7643436e328456252db9d0def76a97f9c2bae10e3ee73a9d427f8f149f",
"blockindex" : 3,
"blocktime" : 1402520792,
"txid" : "d191290208e31f6cf09c360b9f8bb671cea32dded456f00061a00496c8c60263",
"time" : 1402520778,
"timereceived" : 1402520778
},
{
"account" : "123",
"address" : "XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G",
"category" : "send",
"amount" : -0.03000000,
"fee" : -0.00001000,
"confirmations" : 34,
"blockhash" : "1f986c7643436e328456252db9d0def76a97f9c2bae10e3ee73a9d427f8f149f",
"blockindex" : 3,
"blocktime" : 1402520792,
"txid" : "d191290208e31f6cf09c360b9f8bb671cea32dded456f00061a00496c8c60263",
"time" : 1402520778,
"timereceived" : 1402520778
}
Hard Link appeared.
http://chainz.cryptoid.info/xc/block.dws?29113.htm
http://chainz.cryptoid.info/xc/block.dws?29111.htm
http://chainz.cryptoid.info/xc/address.dws?XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G.htm
http://chainz.cryptoid.info/xc/address.dws?XYyMMG1VQHyRhAQWGdRQ9AEfdwSuG7w18G.htm