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

[slush]

I just "fixed" the lost blocks 917,923,926 by doubling rewards for rounds #13919, #13920, #13921. I'm sorry for inconvenience.

[digital]

I just "fixed" the lost blocks 917,923,926 by doubling rewards for rounds #13919, #13920, #13921. I'm sorry for inconvenience.

Thanks Slush!

Just out of curiosity, did you figure out what cause the bug in the first place?

[slush]

Hm, actually not. Mysql log didn't tell me anything significant, but it clearly failed during the insert to block table.

I just "fixed" the lost blocks 917,923,926 by doubling rewards for rounds #13919, #13920, #13921. I'm sorry for inconvenience.

Thanks Slush!

Just out of curiosity, did you figure out what cause the bug in the first place?

[pekv2]

Hm, actually not. Mysql log didn't tell me anything significant, but it clearly failed during the insert to block table.

I just "fixed" the lost blocks 917,923,926 by doubling rewards for rounds #13919, #13920, #13921. I'm sorry for inconvenience.

Thanks Slush!

Just out of curiosity, did you figure out what cause the bug in the first place?

Oh nice. Can this happen more often please :p . Thanks for the double up.

[slush]

m0mchil just released new version of poclbm with native support of Stratum. Can anybody check it and confirm that it works as expected? I don't have a reason to think an oposite, I just don't have GPU here around to check it myself.

[Portnoy]

m0mchil just released new version of poclbm with native support of Stratum. Can anybody check it and confirm that it works as expected? I don't have a reason to think an oposite, I just don't have GPU here around to check it myself.

Working fine for me.  Although I don't see anything different. The last version worked fine for me with Stratum.

[slush]

Portnoy: Can you confirm that it is connecting to port 3333 instead of 8332? If so, then poclbm is mining on Stratum interface and thus giving you all benefits included in this protocol.

[Portnoy]

Portnoy: Can you confirm that it is connecting to port 3333 instead of 8332? If so, then poclbm is mining on Stratum interface and thus giving you all benefits included in this protocol.

Sure. How do I do that?

This is what I have in my batch file:
poclbm.exe [userdetails]@localhost:8332 -d0 -v -w128 -f1

Should I change that 8332 above to 3333? 

[slush]

Portnoy, the main reason for native support in miners is that users don't need mining proxy. So try to point latest poclbm to http://api.bitcoin.cz:8332 again, it should redirect to Stratum automatically (by following X-Stratum HTTP header in the response). Or you can put stratum://api-stratum.bitcoin.cz:3333 instead, to point miner to stratum interface directly.

[Portnoy]

Portnoy, the main reason for native support in miners is that users don't need mining proxy. So try to point latest poclbm to http://api.bitcoin.cz:8332 again, it should redirect to Stratum automatically (by following X-Stratum HTTP header in the response). Or you can put stratum://api-stratum.bitcoin.cz:3333 instead, to point miner to stratum interface directly.

I live in Western Canada... is one of those better than another for my location?

I set it back to poclbm.exe [userdeatils]@api.bitcoin.cz:8332 -d0 -v -w128 -f1

The way I had it before trying Stratum, although now I am using the new version of poclbm.exe. 

[digital]

So...

All of a sudden one of my workers isn't getting any shares through, the miner is working fine, but every time a share is submitted the proxy log says that it was rejected by the pool and my "worker is not authorized"

As far as I know, nothing has changed.  I did just recently download the latest version of the proxy, but I'm pretty sure it had been working for several hours, and just in the last hour or so it started doing this...

Any thoughts?

[digital]

Well, I ended up restarting the proxy and everything is working now.

But it might be something to keep in mind because I downloaded the newest proxy around 2pm today, then everything ran great until about 7pm.  Then I started getting the shares rejected with an error that said my worker was not authorized.  It looked like it started with a new block.

After restarting the proxy it started working again.

I'll keep an eye on things going forward and report any other oddities...

[slush]

I live in Western Canada... is one of those better than another for my location?

I set it back to poclbm.exe [userdeatils]@api.bitcoin.cz:8332 -d0 -v -w128 -f1

The way I had it before trying Stratum, although now I am using the new version of poclbm.exe. 

In new poclbm, you should see some informational message that it is switching to stratum, correct?

Both proxy and native support will work good, except that with native support in miner you don't need to run special software on the machine.

[slush]

All of a sudden one of my workers isn't getting any shares through, the miner is working fine, but every time a share is submitted the proxy log says that it was rejected by the pool and my "worker is not authorized"

As far as I know, nothing has changed.  I did just recently download the latest version of the proxy, but I'm pretty sure it had been working for several hours, and just in the last hour or so it started doing this...

Yes, this is quite interesting. I have similar bug report by another user. However I'm running latest proxy version overnight and don't see any problem. What miner are you using?

[slush]

There's some uncertainity how to connect newest poclbm to the pool using Stratum.

You don't need to change any settings in your miners, just connect them to "api.bitcoin.cz" port "8332" as usual. Pool is advertising special HTTP header which tell poclbm how to switch to Stratum automatically. You should see message about switching to Stratum in the console.

[digital]

All of a sudden one of my workers isn't getting any shares through, the miner is working fine, but every time a share is submitted the proxy log says that it was rejected by the pool and my "worker is not authorized"

As far as I know, nothing has changed.  I did just recently download the latest version of the proxy, but I'm pretty sure it had been working for several hours, and just in the last hour or so it started doing this...

Yes, this is quite interesting. I have similar bug report by another user. However I'm running latest proxy version overnight and don't see any problem. What miner are you using?

That machine was using Guiminer w/ OpenCL.    Not exactly sure which version, cause I don't have the machine in front of me right now, but if I had to guess I would say it's probably the most recent version.

[slush]

digital, please PM me with some logs if you'll see such bug again. I understand it's quite annoying, but I need some log or error message to debug&fix it.

[Portnoy]

I live in Western Canada... is one of those better than another for my location?

I set it back to poclbm.exe [userdeatils]@api.bitcoin.cz:8332 -d0 -v -w128 -f1

The way I had it before trying Stratum, although now I am using the new version of poclbm.exe. 

In new poclbm, you should see some informational message that it is switching to stratum, correct?

Yes it says something like, "diverting to stratum".

Both proxy and native support will work good, except that with native support in miner you don't need to run special software on the machine.

I see, so one doesn't need that mining_proxy.exe anymore with this new version of poclbm. 

Thanks for the info. 

[digital]

digital, please PM me with some logs if you'll see such bug again. I understand it's quite annoying, but I need some log or error message to debug&fix it.

No problem, I'm happy to help.  If it pops up again i'll definitely send you over the logs...

[keystroke]

Hi Slush,

Can you tell us more about the democratic mining you propose? Would that give miners the ability to select which transactions go into a block?

Re: "I already have some ideas for Stratum mining protocol extension, where miners will be able to suggest their own merkle branch (I call it internally “democratic mining”), which will solve such issues as centralized selection of transactions. For now I decided to focus on such a solution, which will fit to majority of miners and do some extensions later."

Thanks!