This long Block is killing my psychic. I’m trying to stay positive for the long haul but, it’s hard. I’ve been running a rig-to-rig compare with ethermine.org and my reward here on ETH is less than half with ethermine.org.
Don’t let your psychic into the same room with the mining rigs.
Unfortunately, I’m sitting above one of my rigs to keep warm.
if im the one to find a block yall have to buy me a beer
according to this… when the block is found will I get only 0.0268 eth?
Yes that is the case.
How long have you been mining at the pool?
I am at the pool for two days
Okay, the you should have filled the PPLNS queue already and the numbers match.
So yes, when a block is found this will be your reward. The higher the pool hashrate, the faster we find blocks, the more often you will get paid this reward.
So don’t be shy to spread the word, we need more miners.
Yeah guys the point is to get more hash rate to find those blocks faster. People getting scared of high variance blocks doesn’t make it any easier. If you look at the ETC pool, you’ll see tons of high variance blocks, but the blocks happen much faster there because ETC is easier to mine at this point. (it’s also worth quite a bit less).
While good luck isn’t a guaranteed thing, we have had good luck streaks the same as bad luck streaks on ETH. It’s worth pointing out again that whenever our ETH has a good luck streak, everyone wants a piece, but they jump ship when things dip (hence the need for PPLNS)
I was at nanopool before this. I was getting 0.05 eth every 4.5 days.
In here finding block depends on lock and we dont know how long will it take.
also when more miners come my round share and reward will be less as I understood…
Yes. You have to share the cake with more people, thus your cut will be smaller. But then again, more people will bring more cakes.
Technically finding blocks ANYWHERE (any mining pool, or solo mining) depends on luck, or more properly, chance. And you don’t know how long it will take on those pools either. But over time they average out. I’ve seen very large bitcoin pools go a week or more without finding a block (kanopool in particular). It happens.
If you flip a coin once a day, you have one chance a day of getting heads.
If you flip 2000 coins a day, you have 2000 chances of getting heads.
If you have 2000 people each flip one coin a day, you have 2000 chances of one of them getting heads.
And as @entropic616 said, when people bounce it reduces our hash rate, meaning we flip fewer coins.
The welcome-to-the-pool post has some good guidance on this (he said with all due modesty).
It seems “law of large numbers” is the new “gambler fallacy.”
Server have problem ?
Yes. Bare with me, restarting pools right now.
Ok perfect …rig ok now
To be sure throw your keyboard somewhere else loll
My host restarted the network interface for a subnet. And while the servers were offline they flashed new bios to the mainboard which I had to revert before I was able to start the server at all.
Operation is back to normal now.
IT guys always give heart-stopper moments of sheer terror when they don’t announce their intentions.
On another note, I get 141ms to the server from Dallas, TX:
Here are all of the hops the link is going through to get to Germany.
Target Name: eth.anorak.tech IP: 22.214.171.124
Date/Time: 4/24/2018 7:31:57 PM to 4/24/2018 7:32:08 PM CDST
1 0 ms my net
2 9 ms [126.96.36.199] texas.rr.com
3 25 ms tge0-0-4.crtntxjt01h.texas.rr.com [188.8.131.52]
4 26 ms agg33.crtntxjt01r.texas.rr.com [184.108.40.206]
5 14 ms agg21.dllatxl301r.texas.rr.com [220.127.116.11]
6 12 ms bu-ether14.dllstx976iw-bcr00.tbone.rr.com [18.104.22.168]
7 11 ms 0.ae0.pr1.dfw10.tbone.rr.com [22.214.171.124]
8 11 ms ix-ae-23-0.tcore2.DT8-Dallas.as6453.net [126.96.36.199]
9 130 ms if-ae-2-2.tcore1.DT8-Dallas.as6453.net [188.8.131.52]
10 132 ms if-ae-37-3.tcore1.AEQ-Ashburn.as6453.net [184.108.40.206]
11 131 ms if-ae-2-2.tcore2.AEQ-Ashburn.as6453.net [220.127.116.11]
12 135 ms if-ae-12-2.tcore4.NJY-Newark.as6453.net [18.104.22.168]
13 127 ms if-ae-4-3.thar2.NJY-Newark.as6453.net [22.214.171.124]
14 129 ms if-ae-1-3.thar1.NJY-Newark.as6453.net [126.96.36.199]
15 127 ms if-ae-3-3.tcore3.NJY-Newark.as6453.net [188.8.131.52]
16 127 ms if-ae-9-2.tcore1.L78-London.as6453.net [184.108.40.206]
17 132 ms if-ae-3-2.tcore1.PYE-Paris.as6453.net [220.127.116.11]
18 155 ms if-ae-11-2.tcore1.PVU-Paris.as6453.net [18.104.22.168]
19 130 ms if-ae-9-2.tcore2.FNM-Frankfurt.as6453.net [22.214.171.124]
20 129 ms if-ae-59-2.tcore1.FR0-Frankfurt.as6453.net [126.96.36.199]
21 137 ms [188.8.131.52] FR0-Frankfurt.as.net
22 141 ms core21.fsn1.hetzner.com [184.108.40.206]
23 141 ms ex9k2.dc4.fsn1.hetzner.com [220.127.116.11]
24 141 ms anorak.tech [18.104.22.168]
Ping statistics for eth.anorak.tech
Packets: Sent = 8, Received = 8, Lost = 0 (0.0%)
Round Trip Times: Minimum = 140ms, Maximum = 196ms, Average = 151ms
Well you have a great ping time. Here my ping is much, much longer and I don’t have any problems…
Pinging eth.anorak.tech [22.214.171.124] with 32 bytes of data:
Reply from 126.96.36.199: bytes=32 time=388ms TTL=48
Reply from 188.8.131.52: bytes=32 time=390ms TTL=48
Reply from 184.108.40.206: bytes=32 time=390ms TTL=48
Reply from 220.127.116.11: bytes=32 time=389ms TTL=48
Ping statistics for 18.104.22.168:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 388ms, Maximum = 390ms, Average = 389ms
Considering the distance that’s rather good for Western Australia to Germany.