Silk Road forums
Support => Customer support => Topic started by: FireDog1974 on May 07, 2013, 11:18 am
-
Ty for locking, but still not understand the process!!!
SR tumbler is when you send BTC from buyer to seller inside SR.
In my case, I send BTC from my wallet to my SR account.
When I check the block chain with my SR btc-adress, I see that it has been used to to send to another adress.
I did not make any purchase.
So I am a little confused! :(
-
This is exactly what I'm struggling to understand. My btc are now in a wallet containing 110BTC, just 3.5 are mine.
-
Hey guys no worries, thats SR scrambling the transactions for more anonymity, i think.
lots of people are having delays right now you should see your money eventually.
-
Ty for locking, but still not understand the process!!!
SR tumbler is when you send BTC from buyer to seller inside SR.
In my case, I send BTC from my wallet to my SR account.
When I check the block chain with my SR btc-adress, I see that it has been used to to send to another adress.
I did not make any purchase.
So I am a little confused! :(
Hi FireDog1974,
The tumbler tumbles all payments and transfers. As stated in my response to your previous thread, you can read more about it here:
http://dkn255hz262ypmii.onion/wiki/index.php?title=Buyer%27s_Guide#Tumbler
Regarding the deposit delay, please see DPR's thread on the issue here:
http://dkn255hz262ypmii.onion/index.php?topic=156937.0
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In order to fight off the recent DoS attack we had to do substantial reconfiguration to the entire Silk Road system. We are still working out the kinks, and there are a couple of isses that have to be addressed. One is deposits and withdrawals not showing up in a timely manner. We found one problem the new config was causing to this system and fixed it today, so deposits/withdrawals should be flowing now. If you still don't have yours, please message support on the main site.
The other issue is being logged out seemingly at random. We are still looking for the cause of this problem, but I assure you it is a top priority and we will get it fixed soon.
Thank you for your patience as we recover from the recent attack.
- -DPR
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iQEcBAEBAgAGBQJRiS6cAAoJEAIiQjtnt/olb7YH/2a3hoZzUbxR2PswIH6z5VSV
IgTIsFrXYXvYQBVfzDCyyKT4NPTfZJCw+cffHgQiO0lzY7a+j6RQJMmTxI5A0oaA
+XjWWtTSbER7zOfzse9AxTU3a0Zh6fv6A6rwtbAEADJxlGfNLzbyREspRbFyU3XF
1ISfyawi8lfx4UAy30EUuGvDjlh/ofVBsNEhY7tlGCwQAl/hI3zFqy1kA7mO3zcJ
JkSZMPffvW+U63VcRfXj2gxlweZgoeHzK5tyPW97niSTHNdQnvDvgrnZg6O39yLU
dbcq8ELOc9gRXPzXQKhOdsg+xPQWUkjS1mUsxqG3xfHNcAy+iGG7gqoZfqLDEfE=
=Am3B
-----END PGP SIGNATURE-----
Thread locked as resolved.
Libertas