[~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More

[d3athrow]

been getting a lot of this today

[23/05/2011 19:19:38] Warning: work queue empty, miner is idle
[23/05/2011 19:19:38] Connected to server
[23/05/2011 19:19:51] Result: d3f7f67a accepted
[23/05/2011 19:19:54] Disconnected from server
[23/05/2011 19:20:07] Warning: work queue empty, miner is idle
[23/05/2011 19:20:07] Connected to server
[23/05/2011 19:20:35] Result: 561388de accepted
[23/05/2011 19:20:38] Disconnected from server
[23/05/2011 19:20:44] Result: b75b9146 accepted
[23/05/2011 19:20:51] Warning: work queue empty, miner is idle

[1713247620]

1713247620

[1713247620]

1713247620

[1713247620]

1713247620

[1713247620]

1713247620

[steelhouse]

Seems to be going good, just got a block and 166 gH/s, hopefully 200 gH/s by friday.

[eleuthria]

Seems to be going good, just got a block and 166 gH/s, hopefully 200 gH/s by friday.

Bit of bad luck today to make up for all the good luck we've been having.  Hopefully with the new dedicated hosting provider this weekend, we can surpass 250 gH/sec by the end of the month.  The current hardware will probably stop keeping up around that point.



Payout Lock is now an optional feature of the pool, defaulting to off.  If you have not set your preference, you will see an alert on the left side navigation menu until you enable the lock or hide the warning.

This feature is highly recommended for users.  If your account password (or email) were compromised, the person could access your account, change the wallet, and take your balance for themselves.  With this lock, such an attack would require 24 hours to complete, with an email being sent to your confirmed address (if one has been set), and warnings appearing on the sidebar.

[IlbiStarz]

Seems to be going good, just got a block and 166 gH/s, hopefully 200 gH/s by friday.

Bit of bad luck today to make up for all the good luck we've been having.  Hopefully with the new dedicated hosting provider this weekend, we can surpass 250 gH/sec by the end of the month.  The current hardware will probably stop keeping up around that point.



Payout Lock is now an optional feature of the pool, defaulting to off.  If you have not set your preference, you will see an alert on the left side navigation menu until you enable the lock or hide the warning.

This feature is highly recommended for users.  If your account password (or email) were compromised, the person could access your account, change the wallet, and take your balance for themselves.  With this lock, such an attack would require 24 hours to complete, with an email being sent to your confirmed address (if one has been set), and warnings appearing on the sidebar.

Yeah, first a 6 hour block, then a 4 hour block

Really love the payout lock, I'm surprised no other pools thought of it/use it.

[xanadu]

Feature request:

Would you consider having the "My Workers" view flag the worker field "Last Share" that have gone ~300 seconds (5 min) with a yellow background and ~900 seconds (15 min) with red? In your spare time of course 

That would enhance using the stats page as a simple monitoring tool for my worker farm, I have monitoring in place to show that the individual machines are up and running but not for the actual mining processes.

Thank you for all of the work on this pool!

(#791)
-X

[IlbiStarz]

Feature request:

Would you consider having the "My Workers" view flag the worker field "Last Share" that have gone ~300 seconds (5 min) with a yellow background and ~900 seconds (15 min) with red? In your spare time of course 

That would enhance using the stats page as a simple monitoring tool for my worker farm, I have monitoring in place to show that the individual machines are up and running but not for the actual mining processes.

Thank you for all of the work on this pool!

(#791)
-X

And to follow up, maybe even an email after an hour or so of no shares.

[lebish]

Keep up the good work!  Any chance you'd consider open-sourcing the backend RPC server code?

The server is running a (mostly) standard pushpool, so open sourcing my pool would not accomplish too much .

I think he may have been referencing your PHP code that interacts with bitcoind and pushpool, does the user management, etc. Since that's the one chunk every pool is developing on their own, it'd be great to see someone release the "front half" since pushpool (the "back half") was open sourced.

[d3athrow]

Seems to be going good, just got a block and 166 gH/s, hopefully 200 gH/s by friday.

Bit of bad luck today to make up for all the good luck we've been having.  Hopefully with the new dedicated hosting provider this weekend, we can surpass 250 gH/sec by the end of the month.  The current hardware will probably stop keeping up around that point.



Payout Lock is now an optional feature of the pool, defaulting to off.  If you have not set your preference, you will see an alert on the left side navigation menu until you enable the lock or hide the warning.

This feature is highly recommended for users.  If your account password (or email) were compromised, the person could access your account, change the wallet, and take your balance for themselves.  With this lock, such an attack would require 24 hours to complete, with an email being sent to your confirmed address (if one has been set), and warnings appearing on the sidebar.

So you have any idea why its doing this?

Code:

[24/05/2011 02:42:46] Disconnected from server
[24/05/2011 02:43:01] Result: e9866ea1 accepted
[24/05/2011 02:43:02] Warning: work queue empty, miner is id
[24/05/2011 02:43:02] Failed to connect, retrying...
[24/05/2011 02:43:18] Connected to server
[24/05/2011 02:43:19] Disconnected from server
[24/05/2011 02:43:31] Result: 5ecda2f6 rejected
[24/05/2011 02:43:35] Warning: work queue empty, miner is id
[24/05/2011 02:43:35] Failed to connect, retrying...
[24/05/2011 02:43:50] Connected to server
[24/05/2011 02:43:51] Disconnected from server
[24/05/2011 02:43:55] Result: 6d5a909a rejected
[24/05/2011 02:44:07] Warning: work queue empty, miner is id
[24/05/2011 02:44:07] Failed to connect, retrying...
[24/05/2011 02:44:23] Failed to connect, retrying...
[24/05/2011 02:44:39] Failed to connect, retrying...
[24/05/2011 02:44:54] Connected to server
[24/05/2011 02:44:57] Result: ed31c76b accepted
[24/05/2011 02:45:20] Result: a56dfd13 accepted
[24/05/2011 02:45:32] Result: e2f73ffd accepted

[andrepcg]

i have this question regarding block confirmations.

when you say "51 until confirmed", what does the number 51 represent? hours? minutes? shares?

thanks!

[EpicBacon]

i have this question regarding block confirmations.

when you say "51 until confirmed", what does the number 51 represent? hours? minutes? shares?

thanks!

It means that 51 blocks need to be solved by the network.

[eleuthria]

So you have any idea why its doing this?

Code:

[24/05/2011 02:42:46] Disconnected from server
[24/05/2011 02:43:01] Result: e9866ea1 accepted
[24/05/2011 02:43:02] Warning: work queue empty, miner is id
[24/05/2011 02:43:02] Failed to connect, retrying...
[24/05/2011 02:43:18] Connected to server
[24/05/2011 02:43:19] Disconnected from server
[24/05/2011 02:43:31] Result: 5ecda2f6 rejected

I haven't heard any other reports of that level of idle/disconnects showing up.  What speed is your miner running at, and where are you located geographically?  A few idles wouldn't surprise me right now as the pool is growing far faster than the current server can handle it, but constant disconnects are a completely different issue.

Feature request:
Would you consider having the "My Workers" view flag the worker field "Last Share" that have gone ~300 seconds (5 min) with a yellow background and ~900 seconds (15 min) with red? In your spare time of course 

This functionality is coming soon, I was waiting to implement it until I had emails & confirmations added, since there is an additional premium service (email alerts) that will be tied into it.

[milesc]

Keep up the good work!  Any chance you'd consider open-sourcing the backend RPC server code?

The server is running a (mostly) standard pushpool, so open sourcing my pool would not accomplish too much .

I think he may have been referencing your PHP code that interacts with bitcoind and pushpool, does the user management, etc. Since that's the one chunk every pool is developing on their own, it'd be great to see someone release the "front half" since pushpool (the "back half") was open sourced.

This is exactly what I was referring to. 

[Sukrim]

Happy 100 btw.!

[eleuthria]

Keep up the good work!  Any chance you'd consider open-sourcing the backend RPC server code?

The server is running a (mostly) standard pushpool, so open sourcing my pool would not accomplish too much .

I think he may have been referencing your PHP code that interacts with bitcoind and pushpool, does the user management, etc. Since that's the one chunk every pool is developing on their own, it'd be great to see someone release the "front half" since pushpool (the "back half") was open sourced.

This is exactly what I was referring to.  

Few problems with that one:
  1) I'm a computer hobbyist, not a professional.  I'd be embarrassed to release my PHP code .
  1a) I'm a procedural style programmer.  Separating design from the processing engine is something I'm working on, but they still get mixed together quite frequently.
  2) The only major defining feature of a pool is its front-end.  On the back end, most pools are fairly similar.  If I released my PHP code, there would be nothing my pool offers that couldn't be cut & pasted somewhere else.



On the update side of things:  I've reworked how the system handles emails, and it is now sending valid MIME emails with both plaintext or HTML.  A few users were having their confirmation emails rejected by systems that refused to accept a non-MIME formatted email.

[fnord123]

Has anybody tried Diablominer with BTCGuild from behind a proxy firewall?

I can get diablominer to work with Eligius, but would rather use BTCGuild. Here's my command line that works just fine on Eligius:

Code:

C:\Program Files (x86)\Bitcoin\DiabloMiner>DiabloMiner-Windows.exe --proxy XXX.XXX.com:911 -u myaddress -p password -o mining.eligius.st -r 8337 VECTORS BFI_INT FASTLOOP AGGRESSION=6

However, when I try the following on BTCGuild, I get:

Code:

C:\Program Files (x86)\Bitcoin\DiabloMiner>DiabloMiner-Windows.exe -dd --proxy XXX.XXX.com:911 -u workername -p workerpw -o btcguild.com -r 8332 VECTORS BFI_INT FASTLOOP AGGRESSION=6
[5/24/11 11:08:42 AM] Started
[5/24/11 11:08:42 AM] Connecting to: http://btcguild.com:8332/
[5/24/11 11:08:43 AM] Added XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
[5/24/11 11:08:43 AM] ERROR: Can't connect to Bitcoin: Bitcoin returned unparsable JSON
[5/24/11 11:08:43 AM] ERROR: Can't connect to Bitcoin: Bitcoin returned unparsable JSON

[eleuthria]

Has anybody tried Diablominer with BTCGuild from behind a proxy firewall?

I can get diablominer to work with Eligius, but would rather use BTCGuild. Here's my command line that works just fine on Eligius:

There's an update to pushpool I have to roll into the server that should fix the proxy issue.  I'm waiting to find out when I can move to a dedicated host to make the switch.

[w128]

 1) I'm a computer hobbyist, not a professional.  I'd be embarrassed to release my PHP code .

That's one of the neat things about "opening" up your code. There are far more people who are willing and able to find and fix all the suboptimal bits of existing code than there are folks like yourself who can build that useful code from scratch in the first place.

[kjj]

The payout lock warning doesn't actually go away when I click the link to hide it.

[grue]

Few problems with that one:
  1) I'm a computer hobbyist, not a professional.  I'd be embarrassed to release my PHP code .
  1a) I'm a procedural style programmer.  Separating design from the processing engine is something I'm working on, but they still get mixed together quite frequently.
  2) The only major defining feature of a pool is its front-end.  On the back end, most pools are fairly similar.  If I released my PHP code, there would be nothing my pool offers that couldn't be cut & pasted somewhere else.



On the update side of things:  I've reworked how the system handles emails, and it is now sending valid MIME emails with both plaintext or HTML.  A few users were having their confirmation emails rejected by systems that refused to accept a non-MIME formatted email.

you could at least release a "stripped" version of the code, with only the basic functionality. just enough to set up a small private pool.

[d3athrow]

So you have any idea why its doing this?

Code:

[24/05/2011 02:42:46] Disconnected from server
[24/05/2011 02:43:01] Result: e9866ea1 accepted
[24/05/2011 02:43:02] Warning: work queue empty, miner is id
[24/05/2011 02:43:02] Failed to connect, retrying...
[24/05/2011 02:43:18] Connected to server
[24/05/2011 02:43:19] Disconnected from server
[24/05/2011 02:43:31] Result: 5ecda2f6 rejected

I haven't heard any other reports of that level of idle/disconnects showing up.  What speed is your miner running at, and where are you located geographically?  A few idles wouldn't surprise me right now as the pool is growing far faster than the current server can handle it, but constant disconnects are a completely different issue.

Feature request:
Would you consider having the "My Workers" view flag the worker field "Last Share" that have gone ~300 seconds (5 min) with a yellow background and ~900 seconds (15 min) with red? In your spare time of course 

This functionality is coming soon, I was waiting to implement it until I had emails & confirmations added, since there is an additional premium service (email alerts) that will be tied into it.

I'm in central USA, 5830 at 1000mhz core getting ~305mh/s with phoenix. Get the same issues with diablo and poclbm, This was working perfectly a few days ago though.