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

[commlinx]

I also have a question about the wallet thing I just started mining yesterday my self. Should I only use the address in the bitcoin program or can I put the address to the wallet.dat in the bitcoin folder?

Yes use the address in the bitcoin client. The wallet.dat is only accessible to your own computer, and it's vital you don't give others direct access to it because they could take your coins.

[nzbtc]

On the user stats page where it shows us our current workers; Does the 'Found Block' Column mean that one of my workers solved a block and earned the pool 50BTC?

http://imigi.tk/3lefzx/2.png

[commlinx]

On the user stats page where it shows us our current workers; Does the 'Found Block' Column mean that one of my workers solved a block and earned the pool 50BTC?

Yes that's what it means

[nzbtc]

On the user stats page where it shows us our current workers; Does the 'Found Block' Column mean that one of my workers solved a block and earned the pool 50BTC?

Yes that's what it means

Sweet! Thanks for clearing it up. Glad to help out the pool!

[dikidera]

I am specifically requesting a payout button for the "confirmed rewards". As i set my threshold to 4.60 while my unconfirmed reward was 4.62. But i never even imagined that we would get an invalid block. So, every one of my rewards got confirmed, but never crossed the threshold.

Now i can't withdraw it. And i have switched to another pool for for a bit thus i can't mine. And even if i do, waiting for 100 confirms which could take more than 12 hours is....

Nvm, fixed.

[andyb]

Today the error is back (with port forwarding disabled)

Running command: poclbm.exe --user=xxxxxx  --pass=xxxxxxx -o mining.bitcoin.cz -p 8332 -d0 --verbose -v -w128
Listener for "Default" started
Listener for "Default": 23/05/2011 11:03:12, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:03:18, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:03:24, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:03:30, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:03:36, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:03:45, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:03:54, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:04:00, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:04:06, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:04:12, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:04:18, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:04:27, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:04:33, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:04:40, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:04:46, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:04:50, Server temporarily down for maintenance
Listener for "Default": 23/05/2011 11:04:56, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:05:02, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:05:13, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:05:19, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:05:20, Server temporarily down for maintenance
Listener for "Default": 23/05/2011 11:05:26, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:05:30, Server temporarily down for maintenance
Listener for "Default": 23/05/2011 11:05:35, Server temporarily down for maintenance
Listener for "Default": 23/05/2011 11:05:41, Problems communicating with bitcoin RPC
Listener for "Default": 23/05/2011 11:05:47, Problems communicating with bitcoin RPC

turning on port fw doesn't fix the problem

[Justsomeforumuser]

@andy90
It's not you it's the server. See the part where it says
"Server temporarily down for maintenance"

Yea.

About this @Slush:

I have now TWICE seen Total Reward BTC drop. This morning I had 0.82xxxx, I refreshed an hour later during the maintenance, and now there are only 0.81507997  BTC total.

Is this unconfirmed blocks getting suddenly invalidated or is something lost during maintenance?

[dishwara]

Too much server down..  yesterday & today (just now)

Any attack on pool?

[cablepair]

this has happened every day for the last three days
right around 6AM EST.

I know slush is aware of it because I have brought it to his attention every day for the last three days. Not sure what the issue is.

[slush]

I have now TWICE seen Total Reward BTC drop. This morning I had 0.82xxxx, I refreshed an hour later during the maintenance, and now there are only 0.81507997  BTC total.
Is this unconfirmed blocks getting suddenly invalidated or is something lost during maintenance?

Two blocks were invalid yesterday, so twice unconfirmed reward drop for those blocks. Those invalid blocks were not caused by pool problems, but there were more block found in network at same time (for example pool block 4706 was found in the same second as another block which was accepted by bitcoin network).

[slush]

Too much server down..  yesterday & today (just now)
Any attack on pool?

Yes, three days, same time, it is really strange. Pool is up again, it recovered itself. I'm in discussion with server provider if there is everything OK on internal network...

[andyb]

So... I was actually right when I said I was really unlucky to start mining and the server to go down immediately after that yesterday? and apparently today too.

It's not you it's the server. See the part where it says

I saw that but I thought maybe it's just a bug or something, because I was also getting alot of "Problems communicating with bitcoin RPC", I didn't expect the server to be down for maintenance right when I started mining. Then I played with bypassing the router and port fw and GUIMiner started working, by coincidence apparently. Heh...
It would be nice to have a "server online/offline" on the website.

[cablepair]

thanks for being on top of things slush.

;>

[slush]

"Problems communicating with bitcoin RPC"

It is usually HTTP 50x status or something like this, so it can be anything on pool side. From internal network troubles, to bitcoind deadlocks.

[slush]

It would be nice to have a "server online/offline" on the website.

Best indicator is "Current server load (60 sec average):" on stats page. It is usually around 800-1000rq/s. When it fall to 50 or something, then server is down .

[andyb]

Best indicator is "Current server load (60 sec average):" on stats page. It is usually around 800-1000rq/s. When it fall to 50 or something, then server is down .

 good to know, thx

[amazingfunksta]

Quick question, is this normal, considering my average?

http://img.photobucket.com/albums/v93/amazingfunksta/bitcoin.jpg

Odd how it's normally 0.07 to 0.08 but then one round it was randomly 0.002.

Thanks,

[urtur]

Quick question, is this normal, considering my average?

This block is weird: I also have my reward an order of magnitude below normal.

[slush]

Quick question, is this normal, considering my average?

Same issue as yesterday, fixed. I'm sorry for troubles like this, I'll watch reward balancing more carefully for those problematic rounds.

[sniper_sniperson]

Cool