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

[digital]

I should now add that I have a seperate macine running bamt and mining through another machine at home running the proxy.  That setup hasn't submitted a share in about 40 minutes. And that is around 700 mhash.

My other two, 350mhash, and 70mhash (my laptop), are both using the latest guiminer, and submitting shares this whole time.

[snaidervp]

thats bad for you, sorry

[digital]

people must be getting connected back up because I'm seeing my estimated reward go slowly back down to normal...

[snaidervp]

its me!! sorry for that


Pool luck (Pool bad luck, actually) 40%

[Uliss]

What is going on?
For the second day in a row the pool creates visibility of work!

[5120-01-518-6126]

I'm not sure, I'm actually using the latest guiminer, with the dropdown just set to slush's pool.  It doesn't actually say what url it uses for that setting.  But I am still submitting shares, albeit inconsistently...

out-of-the-box guiminer defaults slush's pool to getwork.  To change to stratum, click on the worker's tab and stop the miner.  Draw down the Server list, picking "other" at the bottom.  With that a box labeled Host will show under Server.  Type in stratum.bitcoin.cz and change the Port box to 3333, save the settings, and start the miner.

[bigbeninlondon]

I have a question about the JSON.  Right now the recent rounds JSON looks kind of like this:

Code:

{
   "blocks": {
      "234240": {
         "is_mature": 1,
         [...]
      }, 
      "234241": {
         "is_mature": 1,
         [...]
      }
   }
}

Shouldn't it be

Code:

{
   "blocks": [
      "234240": {
         "is_mature": 1,
         [...]
      }, 
      "234241": {
         "is_mature": 1,
         [...]
      }
   ]
}

As in, the blocks should be an array?

I'm having a hard time trying to figure out how to loop through the blocks object's inner objects without an array.  Others who have parsed this, can I get a little assistance?

[5120-01-518-6126]

To all those who pointed out my guiminer problem was because I had all three miners pointed at the same gpu, you were right - I was
smart enough to set the GTX 480's up correctly but forgot to check the same when I cloned 2nd & 3rd gpu from my first 7870 miner.

guiminer connects to stratum.bitcoin.cz:3333 ok, and all three are putting out 360+ MH/s.


I gave cgminer one last try with Murf's suggestion:

It is trying to connect via the old getwork protocol over http. try:
cgminer -o stratum+tcp://stratum.bitcoin.cz:3333 -u [my worker id] -p {my worker wd]  --intensity 9

with command line = cgminer -o stratum+tcp://stratum.bitcoin.cz:3333 -u [worker id] -p [worker pass]  --intensity 9

Same problem, returns the following (tested after the recent stratum stability issue was resolved):

probing for an alive pool
pool 0 JSON stratum auth failed: (null)
No servers were found that could be used to get work from.
Please check the details from the list below of the servers you have input
Most likely you have input the wrong URL, forgotten to add a port, or have not set up workers
Pool: 0 URL: stratum+tcp://stratum.bitcoin.cz:3333  User [it's showing the right worker id]  Password: [it's showing the right pass]
Press any key to exit, or cgminer will try again in 15s.

cgminer works ok if I throw in the --scrypt flag and connect to a stratum-based LTC pool, so mebbe something wrong in the 3.0.1 build
I downloaded.  For now, I'll be using guiminer.

[digital]

I'm not sure, I'm actually using the latest guiminer, with the dropdown just set to slush's pool.  It doesn't actually say what url it uses for that setting.  But I am still submitting shares, albeit inconsistently...

out-of-the-box guiminer defaults slush's pool to getwork.  To change to stratum, click on the worker's tab and stop the miner.  Draw down the Server list, picking "other" at the bottom.  With that a box labeled Host will show under Server.  Type in stratum.bitcoin.cz and change the Port box to 3333, save the settings, and start the miner.

Wrong.  If that was the case I would have warnings all over my account page, and each miner would have a red no next to it instead of a green yes.

Which means that the current guiminer, out of the box, supports stratum.  That procedure was required on older versions of guiminer, but not any more.

As I've said before, I'm a lifer, and was a beta tester of stratum.  I'm on top of things.

[gbx]

Slush - would it be possible to get the mining_proxy.exe to automatically reconnect when stratum goes down and comes back up?  I had to close and relaunch the executable and missed some good mining opportunities between the time stratum came back up, and when I restarted the .exe

Thank you!

[digital]

Slush - would it be possible to get the mining_proxy.exe to automatically reconnect when stratum goes down and comes back up?  I had to close and relaunch the executable and missed some good mining opportunities between the time stratum came back up, and when I restarted the .exe

Thank you!

Mine reconnected just fine.  I'm at work with a 700mhash machine at home running bamt through the proxy.  It took a couple minutes, but it started submitting shares on it's own just fine.

[nightengale]

I know the luck comes and goes, but what is going on? Has it gotten this bad before?

[ewitte]

Really bad but at least while it was not even connecting I figured out how to boost my LTC mining settings.  Couldn't get into forum until now, etc.

[ewitte]

Mine reconnected just fine.  I'm at work with a 700mhash machine at home running bamt through the proxy.  It took a couple minutes, but it started submitting shares on it's own just fine.

I didn't touch the one at home also and it started up on its own as well.

[5120-01-518-6126]

I'm not sure, I'm actually using the latest guiminer, with the dropdown just set to slush's pool.  It doesn't actually say what url it uses for that setting.  But I am still submitting shares, albeit inconsistently...

out-of-the-box guiminer defaults slush's pool to getwork.  To change to stratum, click on the worker's tab and stop the miner.  Draw down the Server list, picking "other" at the bottom.  With that a box labeled Host will show under Server.  Type in stratum.bitcoin.cz and change the Port box to 3333, save the settings, and start the miner.

Wrong.  If that was the case I would have warnings all over my account page, and each miner would have a red no next to it instead of a green yes.

Which means that the current guiminer, out of the box, supports stratum.  That procedure was required on older versions of guiminer, but not any more.

As I've said before, I'm a lifer, and was a beta tester of stratum.  I'm on top of things.

I will defer to your time in service.

Perhaps my guiminer version is older than yours.  The original poclbm.ini created by my version of guiminer when I first installed it had "api2.bitcoin.cz" as the hostname and port 8332 as the port for the miners I created using the "slush's pool" server selection.  I thought those settings pointed to the getwork server (nslookup shows an IP of 176.31.157.134).

After configuring my miners as described above, poclbm.ini shows "stratum.bitcoin.cz" for hostname and 3333 for port.  nslookup for stratum.bitcoin.cz shows slush's Amazon EC2s (54.xxx)

[ewitte]

Mine shows api2.bitcoin.cz but always "diverting to stratum.bitcoin.cz"

[digital]

I'm not sure, I'm actually using the latest guiminer, with the dropdown just set to slush's pool.  It doesn't actually say what url it uses for that setting.  But I am still submitting shares, albeit inconsistently...

out-of-the-box guiminer defaults slush's pool to getwork.  To change to stratum, click on the worker's tab and stop the miner.  Draw down the Server list, picking "other" at the bottom.  With that a box labeled Host will show under Server.  Type in stratum.bitcoin.cz and change the Port box to 3333, save the settings, and start the miner.

Wrong.  If that was the case I would have warnings all over my account page, and each miner would have a red no next to it instead of a green yes.

Which means that the current guiminer, out of the box, supports stratum.  That procedure was required on older versions of guiminer, but not any more.

As I've said before, I'm a lifer, and was a beta tester of stratum.  I'm on top of things.

I will defer to your time in service.

Perhaps my guiminer version is older than yours.  The original poclbm.ini created by my version of guiminer when I first installed it had "api2.bitcoin.cz" as the hostname and port 8332 as the port for the miners I created using the "slush's pool" server selection.  I thought those settings pointed to the getwork server (nslookup shows an IP of 176.31.157.134).

After configuring my miners as described above, poclbm.ini shows "stratum.bitcoin.cz" for hostname and 3333 for port.  nslookup for stratum.bitcoin.cz shows slush's Amazon EC2s (54.xxx)

The version number is displayed right at the top of the guiminer window.  the most recent one is v2012-12-03...

[gbx]

Slush - would it be possible to get the mining_proxy.exe to automatically reconnect when stratum goes down and comes back up?  I had to close and relaunch the executable and missed some good mining opportunities between the time stratum came back up, and when I restarted the .exe

Thank you!

Mine reconnected just fine.  I'm at work with a 700mhash machine at home running bamt through the proxy.  It took a couple minutes, but it started submitting shares on it's own just fine.

Weird.  Mine was just pages of errors.. I closed and reopened and it was fine;

I wonder if it was holding onto an old address in DNS?

[5120-01-518-6126]

I'm not sure, I'm actually using the latest guiminer, with the dropdown just set to slush's pool.  It doesn't actually say what url it uses for that setting.  But I am still submitting shares, albeit inconsistently...

out-of-the-box guiminer defaults slush's pool to getwork.  To change to stratum, click on the worker's tab and stop the miner.  Draw down the Server list, picking "other" at the bottom.  With that a box labeled Host will show under Server.  Type in stratum.bitcoin.cz and change the Port box to 3333, save the settings, and start the miner.

Wrong.  If that was the case I would have warnings all over my account page, and each miner would have a red no next to it instead of a green yes.

Which means that the current guiminer, out of the box, supports stratum.  That procedure was required on older versions of guiminer, but not any more.

As I've said before, I'm a lifer, and was a beta tester of stratum.  I'm on top of things.

I will defer to your time in service.

Perhaps my guiminer version is older than yours.  The original poclbm.ini created by my version of guiminer when I first installed it had "api2.bitcoin.cz" as the hostname and port 8332 as the port for the miners I created using the "slush's pool" server selection.  I thought those settings pointed to the getwork server (nslookup shows an IP of 176.31.157.134).

After configuring my miners as described above, poclbm.ini shows "stratum.bitcoin.cz" for hostname and 3333 for port.  nslookup for stratum.bitcoin.cz shows slush's Amazon EC2s (54.xxx)

The version number is displayed right at the top of the guiminer window.  the most recent one is v2012-12-03...

Same version I have.  Did you look at your poclbm.ini file?  But you said your account was showing a stratum connection, so my guess is that Slush has a proxy on api2.bitcoin.cz:8332.  That would make us both right

[killingtime]

api.bitcoin.cz:8332 is indeed a proxy to both getwork and stratum, but if getwork is down, then connecting to this wigs out and you may or may not properly switch over to stratum.  This happened recently.  Probably best to just use stratum.bitcoin.cz:3333