Monero Pool now reporting again!
Thanks!
Topic: [ANN][Pool][CryptoNight Coins] - Easyhash.io - 0.1 fee - page 5. (Read 11036 times)
Yep - I'm outta here
There must be something wrong with pool.
You can mine directly to exchange on etn.luckypool.io. Gonna go there and give a try.
You can mine directly to exchange on etn.luckypool.io. Gonna go there and give a try.
If no reply, will have no choice but to change pools. Shame cus yesterday I earnt nearly $30
I have been consistently mining at 4k/hs and payout just $1... certainly not what the calculator or nicehash says. It was fine yesterday but today the pool seems dead?
How come we get 0 ETN (Height 60383, 60382)? Why are blocks not confirmed?
heres my stat for 24hr exactly, 10KH RX580 12 GPU, calculator through the day i entered the difficulty every few hrs manually, estimated rewards lowest 600 highest 1200... i mined 407 total , this is why whatomine took it off for 24hrs and then put a 30% reduction on it
^ my 24hr stats: calc is wrong because of hashrates it’s not just this it’s all etn pools, and when i say blocks behind the network / blockchain lags i went 4-5 hrs with no payment the blockchain in the etn daemon /wallet even said at the time 126 block delay. should have a basic understanding the blockchain for etn is new and lags.. can even be hackerone trying to DoS/pen test
you should read the whole thread - there are issues with etn network consider the calculators busted or add a 30-40% pool fee the calc for a closer number
i get payouts every 1-2hrs, if the etn network blocks are behind 4-5hrs later but full balance comes through..
i get payouts every 1-2hrs, if the etn network blocks are behind 4-5hrs later but full balance comes through..
I am manually calculating it out, not using a calculator (time over coins made). What I'm saying is looks like coins being made are about right for the time they have been mining, their calculator is just wonky cause the hash rate is all over the place so the weekly payout is all over the place. They need to fix that by doing a overall average hash rate instead of a per instance hash rate.
So what that means is after the first block is mined which is 4 to 5 hours then payouts come in 1 to 2 hrs?
Until an Admin for easyhash answers questions here i would consider this pool to be
DEAD
DEAD
maybe server can’t take the connections i’m randomly losing connect now oh well
Can someone please check the monero pool and see if shows any pool hashrate. I have not seen anything for 18 hours after 24 days of mining with no block.
i really don't like this random hash that all pool show, 2.0 KH/sec now, 1.4,,, 3.2, why, i have constant 4.0 KH/sec all time
you should read the whole thread - there are issues with etn network consider the calculators busted or add a 30-40% pool fee the calc for a closer number
i get payouts every 1-2hrs, if the etn network blocks are behind 4-5hrs later but full balance comes through..
i get payouts every 1-2hrs, if the etn network blocks are behind 4-5hrs later but full balance comes through..
HI!
What would be the reason for error i just got:
'You ip was banned'?
(stratum+tcp://etn.easyhash.io:3632 / gtx1080 client - cc miner 2.2.2-cuda9).
I am mining from 2 separate physical locations, but I don't think that has to do anything with anything.
If I restart the client it starts normally and mines on. Thank you.
What would be the reason for error i just got:
'You ip was banned'?
(stratum+tcp://etn.easyhash.io:3632 / gtx1080 client - cc miner 2.2.2-cuda9).
I am mining from 2 separate physical locations, but I don't think that has to do anything with anything.
If I restart the client it starts normally and mines on. Thank you.
Hi just started with EasyHash, when do you guys do your payouts?
I've mined 7 coins already and still no payouts.....
Also the weekly calculator is all over the place, I should be getting oh 300 bucks a week, but its going from 100-300, no consistency.
I've mined 7 coins already and still no payouts.....
Also the weekly calculator is all over the place, I should be getting oh 300 bucks a week, but its going from 100-300, no consistency.
Thx NetWhiz, we'll test that theory out -- im now using ssl on 1 miner and another miner i just turned vpn on and using a Amsterdam server location i believe the host provider is dig ocean/amsterdam .. I'll report back if it happens again i setup a cron to send me an email when the error pops up
try using 1 miner with SSL stratum+ssl://etn.easyhash.io:3633 , testing that now and we'll see what happs when it flakes out next
Can also use a VPN like expressvpn, install connect to an EU server
----if its a multiple miner per IP issue a service like expressvpn you can connect all your miners to different servers
Can also use a VPN like expressvpn, install connect to an EU server
----if its a multiple miner per IP issue a service like expressvpn you can connect all your miners to different servers
this happens, not overclocked
GPU2 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU0 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU0 t=33C fan=69%, GPU1 t=38C fan=68%, GPU2 t=34C fan=70%, GPU3 t=38C fan=68%, GPU4 t=35C fan=68%, GPU5 t=38C fan=69%
GPU5 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU4 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU3 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU2 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU3 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU0 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU1 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU0 t=33C fan=70%, GPU1 t=39C fan=68%, GPU2 t=34C fan=70%, GPU3 t=39C fan=68%, GPU4 t=36C fan=68%, GPU5 t=39C fan=69%
XMR: 12/09/17-11:18:07 - New job from etn.easyhash.io:3632
GPU3 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU1 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU4 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU3 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU0 t=32C fan=70%, GPU1 t=38C fan=68%, GPU2 t=34C fan=70%, GPU3 t=38C fan=69%, GPU4 t=35C fan=69%, GPU5 t=39C fan=69%
GPU3 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU5 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU1 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU3 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU3 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" val
GPU2 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU0 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU0 t=33C fan=69%, GPU1 t=38C fan=68%, GPU2 t=34C fan=70%, GPU3 t=38C fan=68%, GPU4 t=35C fan=68%, GPU5 t=38C fan=69%
GPU5 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU4 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU3 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU2 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU3 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU0 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU1 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU0 t=33C fan=70%, GPU1 t=39C fan=68%, GPU2 t=34C fan=70%, GPU3 t=39C fan=68%, GPU4 t=36C fan=68%, GPU5 t=39C fan=69%
XMR: 12/09/17-11:18:07 - New job from etn.easyhash.io:3632
GPU3 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU1 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU4 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU3 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU0 t=32C fan=70%, GPU1 t=38C fan=68%, GPU2 t=34C fan=70%, GPU3 t=38C fan=69%, GPU4 t=35C fan=69%, GPU5 t=39C fan=69%
GPU3 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU5 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU1 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU3 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" value.
GPU3 found incorrect share. If you see this message often, make sure you that you did not overclock it too much, also try to reduce "-h" val
Found out it has to do with multiple miners from the same IP connecting. 1 miner works, more than that is rejects the shares. They need to fix this again ASAP!
and now its working again:
XMR: 12/09/17-11:37:46 - SHARE FOUND - (GPU 2)
XMR: 12/09/17-11:37:46 - SHARE FOUND - (GPU 5)
XMR: 12/09/17-11:37:49 - SHARE FOUND - (GPU 3)
XMR: 12/09/17-11:37:51 - SHARE FOUND - (GPU 3)
XMR: 12/09/17-11:37:51 - SHARE FOUND - (GPU 4)
Share accepted (1297 ms)!
Share accepted (1360 ms)!
Share accepted (1407 ms)!
Share accepted (1469 ms)!
Share accepted (1516 ms)!
Share accepted (1578 ms)!
Share accepted (1641 ms)!
Share accepted (1688 ms)!
Share accepted (1750 ms)!
XMR: 12/09/17-11:37:53 - SHARE FOUND - (GPU 0)
XMR: 12/09/17-11:37:57 - SHARE FOUND - (GPU 4)
XMR: 12/09/17-11:38:00 - SHARE FOUND - (GPU 3)
XMR: 12/09/17-11:38:00 - SHARE FOUND - (GPU 1)
Share accepted (1125 ms)!
Share accepted (1219 ms)!
Share accepted (1266 ms)!
Share accepted (1282 ms)!
XMR: 12/09/17-11:38:02 - SHARE FOUND - (GPU 2)
Share accepted (2547 ms)!
XMR: 12/09/17-11:38:11 - SHARE FOUND - (GPU 3)
XMR: 12/09/17-11:38:11 - SHARE FOUND - (GPU 3)
XMR: 12/09/17-11:37:46 - SHARE FOUND - (GPU 2)
XMR: 12/09/17-11:37:46 - SHARE FOUND - (GPU 5)
XMR: 12/09/17-11:37:49 - SHARE FOUND - (GPU 3)
XMR: 12/09/17-11:37:51 - SHARE FOUND - (GPU 3)
XMR: 12/09/17-11:37:51 - SHARE FOUND - (GPU 4)
Share accepted (1297 ms)!
Share accepted (1360 ms)!
Share accepted (1407 ms)!
Share accepted (1469 ms)!
Share accepted (1516 ms)!
Share accepted (1578 ms)!
Share accepted (1641 ms)!
Share accepted (1688 ms)!
Share accepted (1750 ms)!
XMR: 12/09/17-11:37:53 - SHARE FOUND - (GPU 0)
XMR: 12/09/17-11:37:57 - SHARE FOUND - (GPU 4)
XMR: 12/09/17-11:38:00 - SHARE FOUND - (GPU 3)
XMR: 12/09/17-11:38:00 - SHARE FOUND - (GPU 1)
Share accepted (1125 ms)!
Share accepted (1219 ms)!
Share accepted (1266 ms)!
Share accepted (1282 ms)!
XMR: 12/09/17-11:38:02 - SHARE FOUND - (GPU 2)
Share accepted (2547 ms)!
XMR: 12/09/17-11:38:11 - SHARE FOUND - (GPU 3)
XMR: 12/09/17-11:38:11 - SHARE FOUND - (GPU 3)
its the etn network im trying electromine as well same errors so.. again, etn sucks lol.. what happens when the cell phone mining app comes out ... thats like a massive ddos attack lol.
Jump to: