Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 1044. (Read 4382653 times)

You don't need any port forwarding. Please write me exact times when you see 'server down for maintenance', I'll search logs.


Yes, that's normal.


Yes

Yeah thats ok..the reward will be sent to that address..

Hello bitcoin world.

I have no experience to this whole bitcoin thing, so I'm as noob as you can get.
I've started mining only yesterday and it's going almost great. I have one problem though, which I may have fixed on my own but I just wanted to check with you guys.

My problem is that while mining with GUIMiner (latest version), after a few minutes  I was getting a lot of connection problems and "server down for maintenance". At first I thought that I was just unlucky but then I connected my pc directly to the modem, bypassing the router, and it connected with no problems.  After a bit of searching today I've configured my router (netgear) to trigger port range 8332 to 8338 (the second one was just a guess, the first number I got using Tcpview.exe to see where the program was trying to connect).
 In the end this seems to have done it. What range exactly should I forward (if any)?

But I am no expert when it comes to networks and configuring port triggering and all this stuff. I don't even know if what I did helped or it works now just by coincidence.

 also, what's the normal % of stale/invalid shares? I seem to get about 1%.
 2nd: I got my key (wallet thingy) by installing the official bitcoin program which showed a "your Bitcoin Address" And I used that in the "My account" page. Is that ok?

Thanks

Waiting for LP man, hope you done it soon 

Firstly, reward is not necessary related to time, but to rounds. When pool is very lucky for some time, you can earn 1BTC per hour and in oposite, you can earn 0.01 in three hours.

But in this case, this round was affected by pool outage and hourly score renormalizing was skipped, so I'll recalculate rewards again to make it more fair.

Edit: better?

unfortunately our rewards are based on our share of the hashing of 50 btc block that must be split up evenly among all the workers. So a 3 hour share does not necessary pay more or less than a 3 min round. It would be nice if we were paid by the amount of time we are hashing but it simply does not work that way

Slush,

I am just a little curios how you estimate the hash rate of your pool. Not just yours, but in general, how is that done? Are you simply looking at the frequency of how often blocks are found compared to the current target?

Just curious.

Slush, can you please add ssl to the login area? You can get a cert for free from startssl for example.

Because pool didn't find a block until end of hour, everything fixed up and using share based rewarding isn't necessary now.

1x load balancer (I'm preparing second one for ip failover), 4x application servers, 1x database server

All servers are virtualised Intel Xeon quadcores and typical load is 0.2 (so roughly 5% of maximum load) giving me enough space for more workers . I'm using more application servers mainly because I'm running more bitcoin daemons and I want to isolate them (they ocasionally have disk I/O peaks, so running them on more servers improve their speed a lot).

Damn, you're right. After this round finish, I'll recalculate block using share based algorithm to minimize unfairnes in rewards.

It looks like server failed during the hourly score recalculation process.
I see a very large total round score but pieces got by my miners for shares they found are tiny.

it was down a bit, but I think it works fine now.

Bitcoinwatch is downloading hashrate from my stats page. I turned off website for a moment, because of investigating troubles. So that's reason why bitcoinwatch displayed zero hashrate.

Actually pool was not completely down, but majority of users had connection problems. It looks like troubles on provider's internal network and I'm solving it with his support. Pool is back up, but we're still finding any reason for network lockups to prevent outages like that for the future.

Hey slush, you have about 4000 workers. And 800-1000 getworks/s. What CPU does your server have and what is the load?

Slush has disappeared completely from bitcoinwatch.. it's completely down.

Yes, I'm looking for the reason right now.

naa its doing the same yo-yo thing it was doing yesterday

up and down and up and down

'problems connecting with bitcoin rpc'

I wonder what happens at this time of day because its the exact same time this happened yesterday, maybe the server does back up or something at this time?

we have a problem
mining server have going down  


ps: hay it work fine, fix it so fast 

Okay, what confused me was that the total reward number was more than confirmed + unconfirmed.