|
Nyquist wins the 142nd Derby. PPOC, if you find a block before midnight east, 2.42BTC is yours. Everyone else, there is still 1BTC for finding a block.
|
|
|
|
|
Picks are now closed for the contest. The block finding bonus is valid for all blocks found before midnight east (5 hours and 20 minutes from now). Good luck to everyone!
|
|
|
|
There is no limit to how many times a horse can be picked. However, miners can only pick a single horse.  |
|
|
|
LOL... going for the odds-on favorite, I see |
|
|
|
|
With p2pool merged mining, there are no payouts of the merge-mined coins to miners. Either you would have to write some code to figure out how to pay those coins to your miners, or you'd have to do something manually.
|
|
|
|
please understand newtons third law. That law presides over the entire universe and all energy contained within. This pool cannot defy newtons laws. For every action there is equal and opposite reaction. Stop denying this fact and you will see why there is the highs and lows.. Or perhaps be able to accept them better.
I'm hoping you're joking and I just haven't had enough coffee yet to see it. If you are not, then please allow me to correct your statements. While Newton's Third Law does indeed state that for every action there is an equal and opposite reaction, that has absolutely nothing to do with BTC mining. Just because you've had a good luck streak does not mean there is a corresponding bad luck streak, and vice-versa. |
|
|
|
Hey Jonny -- thanks for talking with me earlier today...
I just checked the miner status -- and right on target -- I sure wish I had used that as a definer all this time -- it would have saved me a LOT of mental anguish -- lol...
Are there any contests planned for this weekend???
Glad to help. As for contests/promotions... Well, today marks the 142 running of the Kentucky Derby. So, let's have a little promotion to honor it Everyone who solves a block today will get 1 BTC. You may also pick a horse. If your horse wins and you've solved a block, you will get an additional 1.42 BTC bonus. You don't need to actually solve a block to make a pick, but you do need to solve a block to get any BTC. The running list of picks will be maintained on the 2nd post of this thread located here: https://bitcointalk.org/index.php?topic=1330452.msg13576670#msg13576670Good luck! |
|
|
|
And the EU stratum server is finally back online. Sorry for the downtime, folks. I can already see users connected and submitting hashes |
|
|
|
|
You are most assuredly not "that guy". Your 4 S7s, even if by some strange occurrence were in fact misbehaving represent about 0.061% of the pool's hash rate. If you had 400 S7s... well... even then you'd only be 6.1% of the pool.
|
|
|
|
|
Just an update... the EU datacenter has resolved their issues; however, now my stratum server is unreachable. I'm still working with them to resolve the problem.
|
|
|
|
|
Just part of the human condition.
Ease up on the rumor mill folks. Kano has always been very forthcoming regarding any suspicious behavior on the pool. He's also been kind enough to PM other pool operators, including myself, to let us know his findings so we can also take action. Furthermore, he's running a lot of analytics behind the scenes to identify potential block withholding attacks.
Regarding the lost orphan race with f2pool, that is definitely still an open question.
So until Kano comes forward to declare there is any kind of foul play, it is safe to accept things are as they appear: shit luck.
|
|
|
|
|
Me too... had 1PH running on it. Ended up canceling and refilling my 5P order on WH.
I still haven't gotten a resolution other than, "We have actually an issue on our network, all our administrator are working on it".
Soon as I know more, I'll update here.
|
|
|
|
|
Just an update... datacenter hosting my EU servers is having issues. I am working with them to understand what is happening and an ETA on service restoration.
As of now, the EU stratum server is offline. Please point your gear to the US stratum node for the time being. I will be updating the thread as I come to learn more.
Thanks!
|
|
|
|
No clue. Let me check the logs to see if that provides any info.
Also, are you connecting to port 3334? That diff starts at 65535 and lowest it goes is 8192.
Yes, I'm on port 3334 ... It disconnects and connects again randomly ... Edit: It happened again just now ... Ok... you're connected to both my US and EU stratum servers. The US stratum server logs show nothing out of the ordinary. The EU stratum server logs show a couple of workers. One from I'm assuming your own gear, the other from NH Amsterdam proxy. The one coming from the NH proxy was submitting shares fine, but then it disconnects. There's definitely no "difficulty too low" problem on my end... here are your most recently submitted shares from that order: 2016-05-06 13:24:42 [Pool] [bitcoin] (Thread 6) Share accepted at diff 12673.33069351/13075.50487595 by eghigo.worker2 [37.58.65.213]
2016-05-06 13:24:55 [Pool] [bitcoin] (Thread 6) Share accepted at diff 12673.33069351/35108.28503008 by eghigo.worker2 [37.58.65.213]
2016-05-06 13:25:00 [Pool] [bitcoin] (Thread 6) Share accepted at diff 12673.33069351/25616.28048247 by eghigo.worker2 [37.58.65.213]
2016-05-06 13:25:03 [Pool] [bitcoin] (Thread 6) Share accepted at diff 12673.33069351/13540.38685708 by eghigo.worker2 [37.58.65.213]
2016-05-06 13:25:06 [Pool] [bitcoin] (Thread 6) Share accepted at diff 12673.33069351/24829.04734732 by eghigo.worker2 [37.58.65.213]
2016-05-06 13:25:14 [Pool] [bitcoin] (Thread 6) Share accepted at diff 12673.33069351/18078.31012933 by eghigo.worker2 [37.58.65.213]
2016-05-06 13:25:17 [Pool] [bitcoin] (Thread 6) Share accepted at diff 12673.33069351/19512.18161107 by eghigo.worker2 [37.58.65.213]
2016-05-06 13:25:18 [Pool] [bitcoin] (Thread 6) Share accepted at diff 12673.33069351/22088.41303395 by eghigo.worker2 [37.58.65.213]
2016-05-06 13:25:22 [Pool] [bitcoin] (Thread 6) Share accepted at diff 12673.33069351/182879.02455499 by eghigo.worker2 [37.58.65.213]
Then, the order stops submitting shares altogether. Once that happens for over 10 minutes, the pool disconnects your worker. The worker immediately reconnects, but doesn't attempt to submit any shares: 2016-05-06 13:27:06 [Pool] [bitcoin] (Thread 2) Authorized eghigo.worker2[37.58.65.213]
2016-05-06 13:37:36 [Pool] [bitcoin] (Thread 2) Connected timed out for eghigo.worker2 [37.58.65.213]: last submitted a share was 630 seconds ago
2016-05-06 13:39:38 [Pool] [bitcoin] (Thread 4) Authorized eghigo.worker2[37.58.65.213]
2016-05-06 13:49:42 [Pool] [bitcoin] (Thread 4) Connected timed out for eghigo.worker2 [37.58.65.213]: last submitted a share was 604 seconds ago
2016-05-06 13:51:32 [Pool] [bitcoin] (Thread 5) Authorized eghigo.worker2[37.58.65.213]
2016-05-06 14:02:17 [Pool] [bitcoin] (Thread 5) Connected timed out for eghigo.worker2 [37.58.65.213]: last submitted a share was 645 seconds ago
It's a problem on NH end, not on my pool. |
|
|
|
Jonny any idea why I keep getting disconnected from the pool? It's a rental on WH and I keep getting the following error:
Disconnected. Pool difficulty too low for high speed.
No clue. Let me check the logs to see if that provides any info. Also, are you connecting to port 3334? That diff starts at 65535 and lowest it goes is 8192. |
|
|
|
I know of a few ways they can do it.
so to everyone here that is renting from NH / WH consider that
f2pool can send dead hashers to WH/NH with ease
Can you explain what you mean by "send[ing] dead hashers?" When you pay for miners at *Hash - you have no idea what the miners are and what they are doing. *Hash don't care either coz they get paid BEFORE you mine and they wont lose anything. The people who own the miners will get paid no matter what also. Thus someone could provide "bad hash power" on *Hash and no one would know unless they mined a VERY large amount and kept track of the statistics ... ... ... Even if you did mine a very large amount and keep stats, there's no way to tell which miners of the ones in your order are the bad actors. Miners connect/drop/reconnect to your order based on whatever algorithms *hash uses, and by the settings the hardware owners configure. Basically, as a renter you can absolutely never make an informed decision about whether the hashing power you're renting is behaving badly. |
|
|
|
I think the thing that bothers me the most about the replies by macbook-air is not the accusation of racism, or the statements about probability. What bothers me the most is the misdirection away from kano's original query: Is f2pool taking a deliberate measure to work on their own old blocks for some amount of time hoping to win their own orphan races? In other words, are they abusing their large hash rate percentage and trying to game the system? Here are kano's original theories on why block 410419 was orphaned at all: So basically the cause was one or more of the following:
FUPool is REAL slow getting their blocks to the CN relay.
FUPool works on their own blocks after they see other pool blocks if they are found soon after.
FUPool had most of their 410419 block transactions not in the relay so was really slow getting their block into the relay (compression was almost zero as you can see) Edit: but I don't think this is it coz it was prolly the relay did that coz it already had our block using the transactions.
I bolded the one to help make it clearer. |
|
|
|
|
Show Posts
