[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[slush]

Btw I blocked few IPs on webserver. 40rq/s because of some Windows toolbar crap? Are you serious?

So if you can mine but cannot access site, fix your mining tools and tell me your IP.

[slush]

I'm switching off pool for few minutes, going to database migration.

Edit: Everything went as expected, downtime was less than 5 minutes.

[cablepair]

Mine at a SMPPS pool and then you will love the longer rounds

Mine at an SMPPS pool with longer rounds and it will take a long time to get your coinage out. I've been waiting for 6 weeks for some coins from bitpit, an ESMPPS pool.

Mine at an SMPPS pool that's had a bunch of shorter rounds and your time to payout is reduced.

eligius takes at the very most 3 days to get a payout but its a big (three days worth) payout

and btw: I am not trying to advertise eligius here just reponding to organofcorti's comment - Slush's pool is a great pool - I mined my first 100+ bitcoins ever at his pool back last spring.

[organofcorti]

Mine at a SMPPS pool and then you will love the longer rounds

Mine at an SMPPS pool with longer rounds and it will take a long time to get your coinage out. I've been waiting for 6 weeks for some coins from bitpit, an ESMPPS pool.

Mine at an SMPPS pool that's had a bunch of shorter rounds and your time to payout is reduced.

eligius takes at the very most 3 days to get a payout but its a big (three days worth) payout

Off topic (sorry Slush) but I'll bite - is this your experience or Eligius' guarantee? If an SMPPS has a run of long blocks and ends up with a negative buffer, you could be waiting more than three days for a payout.

[DeathAndTaxes]

If the overall hashrate on a different timescale then worker hashrate in the API.

obfuscated API results

Code:

{
   "username": "YoMamma", "rating": "none", "send_threshold": "1.00000000", "confirmed_reward": "0.33935663", "workers": 
   {
      "YoMamma.SaltyMiner": {"last_share": 1320066559, "score": "909.1899", "hashrate": [b]2031[/b], "shares": 1251, "alive": true}, 
      "YoMamma.TiredMiner": {"last_share": 1320066556, "score": "817.6093", "hashrate": [b]2088[/b], "shares": 1286, "alive": true}
   }, 
   "wallet": "1NnhmuvWcvLA6Nfk9qsBHRkhezLJdy52nN", "unconfirmed_nmc_reward": "19.84041906", "unconfirmed_reward": "0.77621847", "estimated_reward": "0.18220834", "hashrate": "[b]1780.191[/b]"
}

Salty is 2.031 GH/s, Tired is 2.088GH/s however overall is 1.780GH/s   Minor but the OCD side of me is going crazy. ... numbers must match ... numbers must match.   

[slush]

If the overall hashrate on a different timescale then worker hashrate in the API.

Salty is 2.031 GH/s, Tired is 2.088GH/s however overall is 1.780GH/s   Minor but the OCD side of me is going crazy. ... numbers must match ... numbers must match.   

Workers hashrates are calculating from shares in current round, however total hashrate of user is calculated from submits in last 10 blocks. So it's more exact, but have latency.

[DeathAndTaxes]

If the overall hashrate on a different timescale then worker hashrate in the API.

Salty is 2.031 GH/s, Tired is 2.088GH/s however overall is 1.780GH/s   Minor but the OCD side of me is going crazy. ... numbers must match ... numbers must match.   

Workers hashrates are calculating from shares in current round, however total hashrate of user is calculated from submits in last 10 blocks. So it's more exact, but have latency.

Thanks.  I know you (always) got a million things to do but small change of the definitions on API setup page would make that more clear.

[slush]

You're right, I added small notice about caching.

[allinvain]

Reward from current round #8628 will be calculated wrongly. I'll fix it manually later.

Current status:
* Website moved
* api.bitcoin.cz moved
* api2.bitcoin.cz still in London
* database still in London

If you see some performance problems on api.bitcoin.cz, tell me.

To be continued...

Hey slush, I know that we can use either api or api2, but is there a "preferred" api server to use or it all comes down to our choice. I've been using the api2 one for the longest time, partly because at the time when I switched you were getting DDoS'ed like hell and partly because it's the default in guiminer.

[slush]

Hey slush, I know that we can use either api or api2, but is there a "preferred" api server to use or it all comes down to our choice. I've been using the api2 one for the longest time, partly because at the time when I switched you were getting DDoS'ed like hell and partly because it's the default in guiminer.

It's absolutely up to your choice. I need load balancing on more URLs for playing with that hashrate. For example now api.bitcoin.cz is on new server and I'm fine-tuning server settings thanks to this, while api2.bitcoin.cz is still in London.

However in few hours both URL will be on the same machine again, so there's not a big difference.

[JA37]

Just to let you know this is probably the first pool to have a miner above 18 000ft. Don think I got a share while up there, but I was connected and chugging along with my measly cpu. #braggingrights

[cablepair]

Mine at a SMPPS pool and then you will love the longer rounds

Mine at an SMPPS pool with longer rounds and it will take a long time to get your coinage out. I've been waiting for 6 weeks for some coins from bitpit, an ESMPPS pool.

Mine at an SMPPS pool that's had a bunch of shorter rounds and your time to payout is reduced.

eligius takes at the very most 3 days to get a payout but its a big (three days worth) payout

Off topic (sorry Slush) but I'll bite - is this your experience or Eligius' guarantee? If an SMPPS has a run of long blocks and ends up with a negative buffer, you could be waiting more than three days for a payout.

there are plenty of pool stats available including being able to see the actual pool buffer which is huge btw.

[slush]

OK, also api2.bitcoin.cz moved to new location. DNS is already propagated, so I restarted old backends few times, which usually force miners to reconnect and use correct DNS, however I still see connection attempts to old machines. Please restart your miners, old infrastructure will be turned down in few hours...

Btw this is pool support thread, you should really move somewhere else and not spam here :-).

[Iyeman]

hmm website and pools went down for me about 20 minutes ago. just me or bigger issues?

[DeathAndTaxes]

Down for me too.  Nice thing is cgminer rollover support is solid.  Only lost ~30 seconds or so.

[bz]

I'm getting connection problems using GUIMiner v2011-08-24. After doing ipconfig /flushdns I've tried "slush's pool" and other with both api.bitcoin.cz and api2.bitcoin.cz.

[slush]

I'm working on it.

Edit: Originally I though it was another DDoS attack, because server was insanely overloaded (load like 320) and almost not responding. But then I realized some info about hardware failure in system logs, which point me to the fact that it was some hardware issue. I'm in touch with server support and we're finding some solution. However pool is now running and if this happen next time, downtime will be minimal, because I already know what to watch. It's kinda funny that I was almost a year resisting to order real server for pool exactly for the reason of possible hardware failure - and it happen first day of running the pool on bare metal. Life is full or lucky and unlucky "rounds" :-). I'm sorry for troubles, but I'm solving it with very high priority.

[Bigpiggy01]

Ummm is something up with NMC payouts and rewards?

It looks like they aren't executing. And there have been a couple of longish rounds where I don't see any rewards on the stats page 

[slush]

Ummm is something up with NMC payouts and rewards?

It looks like they aren't executing. And there have been a couple of longish rounds where I don't see any rewards on the stats page  

Um, processing of rewards should be fine (except NMC reward for #8644, which I need to recalculate manually, but I'm too tired to do it now).

But are you sure your miners are connected to correct machine? api.bitcoin.cz/api2.bitcoin.cz (currently the api2 has better performance)

Edit: Btw yes, payouts are paused for now, I'm waiting for some blocks to mature to consolidate wallets from old servers to new one. Payouts will be enabled in few hours. I'm sorry that I forgot to announce this.

[Bigpiggy01]

Thanks

Keep up the good work.

except NMC reward for #8644, which I need to recalculate manually, but I'm too tired to do it now

That was the one I was thinking of the other block matches the long NMC block we had so it should all be good.