Quote from: Bungadek on February 19, 2018, 05:06:32 AM

Quote from: ckai93 on February 19, 2018, 02:38:14 AM

a few hours back pool shows that rig went offline but the miner still submit shares.
i've restarted the miner and still submit shares as usual but pool still doesn't show that.
been in touch with ethermine support but they insist that it wasn't a server side fault.

still not sure if it was a pool or miner issue but till then, i'll continue using claymore.

Had the same issue connected to the asia1.ethermine.org. Looks like the difficulty had been raised on that pool too?

Switched to the us server for now and its reporting as normal.

Be good to know if you hear anything back!

guess i'm not the only victim here. are u using -proto 2 for stratum proxy?
here's the reply I got from ethermine:

Quote

Hi XXXXXXX,

It is normal that some of our servers do not respond to ping requests.

Our initial investigation resulted that you where a victim of a so called BGP hijacking attack. The attacker was able to spoof the IP addresses of our mining server and redirect your hashrate to his own stratum server. If you look at your mining software log you will see that your miner was disconnected from our pool at the time the issue started. When it reconnected it was redirected to the attackers server. This can be seen by the work packages provided by the stratum server. While our stratum has a fixed difficulty of 4000MH the server from the attacker sent out work packages with a difficulty of 10000MH. For example:

Real work package: New job #9591c733 from asia1.ethermine.org:14444; diff: 4000MH
Attacker work package: New job #9538fa6e from asia1.ethermine.org:14444; diff: 10000MH

Furthermore our work package includes 4 parameters while the work package of the attacker included only 3 parameters:

Real work package: Received: {"id":5,"jsonrpc":"2.0","result":["0x9591c733c9eccdc842b361e699142278cfba5de5a17bf4a49d8a36de62a23f89","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4e0e58"]}
Attacker work package: Received: {"jsonrpc":"2.0","id":0,"result":["0x6facf1be3f19166290f14f39a8bef0ae7ec3f282fa7378f9f3a098f1bf1ce81f","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

Unfortunately there is not much we can do from our side against such kind of attacks as the current Ethereum stratum protocol is neither encrypted nor authenticated. The only real solution to avoid this type of attack is to implement an encrypted and authenticated stratum protocol via SSL. We will be working together with the mining software developers to implement such a method.

We are very sorry for the inconvenience this incident has caused.

so yea, for people using -proto 2 for stratum server, I would be super cautious about it. But since I have yet to see this kind of problem with Claymore, I'll be sticking with them as PhoenixMiner actually gave me lower or equal hash rates as compared to Claymore; plus I'm not that heavy of a miner even if there's a 1 mh/s bump per card.