"CoinEX.pw ‏@CoinexPW  22 Std.
CoinEx will start refunding accounts next week. Don't panic. Keep calm & carry on."

Thx for Update!! sounds pretty nice )

Thx ,
I just want to help !!
And I think it should be able to do something similar!

Here is my brainstorming:
All Exchanges needs a blacklist service which is able to determinate the way of stolen BTC's.
This sevice has to look backwards along all transactions of this address and then block it if there is a withdraw address observed which is marked as hacked. then if thats the case the exchange should either block it or better move it to a safe place by doing automatic transaction between e.g. 10 offline wallets! That should be safe
Hacked withdraw addresses should be stored at one global service, having multiple backups on other servers and synchonizing mechanisn to ensure security.

So the asshole(s) who still got the BTC (if not already exchanged to real money..) will fail !!!!!!!?

Best for all, and me

Thx for the update!!

I would love to help finding this asshole(s)!
It should be able to track dem down by retracking the wallet address(s) used for all transactions to get the IP's, by comparing against known wallet addresses which were included during the transactions of all exchanges  (starting by coinex withdraw wallet addresses) ?!?! maybe another GOOD genius "hacker" could get it more closer.

NSA where are your fucking illegal tools to track this dude ^^

Wish you get it running soon it was a great exchange platform !!

Hiiiii,

I build a small PogoPlug (E02) miner running ArchLinux and bfgminer/cgminer/minepeon with 2x Antminer U1.

Now I tried to get a HEX16A2 working with cgminer v3.12.3 rev and patch for cgminer 3.12.3 from technobit.
Patching and compiling cgminer was no problem.
The HEX16A2 is recognized if it's plugged in the additional powered 7-Port USB-Hub.
The HEX16A2 is not recognized if it's not plugged in the additional powered 7-Port USB-Hub ;P

Now comes the Issue:
The miner is listed with an error "*** err: (-9) LIBUSB_ERROR_PIPE" using "cgminer -n" until I run cgminer normal the first time to start hashing,
then asking cgminer "cgminer -n" again, it lists the HEX16A2 correctly.

The end result is the miner won't start hashing. But the miner is listed in cgminer if its plugged.
And the miner is correctly detected as HEXc if I don't use the parameter "--set_default_to_c"

I tried to change voltage and hashspeed but nothing helped..
The miner works on Windows XP with Hexminer v1.0.0.2 without problems..
I used the shell to setup/build the cgminer and I made a picture showing ALL the information (highlighted RED) which I described above (Commands, Configuration, Some System Info, Issue "cgminer -n").



I appreciate all the help I could get & THX!!!

sHoRtBuSseR , Can u please share the solution because i am running into the same issue -.-

Need fast help pls

Big Thx!!!