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

fnord123

newbie

Activity: 47

Merit: 0

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

legendary

Activity: 1750

Merit: 1007

Quote from: milesc on May 24, 2011, 11:45:11 AM

Quote from: lebish on May 24, 2011, 12:41:44 AM

Quote from: eleuthria on May 23, 2011, 08:29:22 AM

Quote from: milesc on May 23, 2011, 07:18:55 AM

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.

Sukrim

legendary

Activity: 2618

Merit: 1007

Happy 100 btw.!

milesc

newbie

Activity: 7

Merit: 0

Quote from: lebish on May 24, 2011, 12:41:44 AM

Quote from: eleuthria on May 23, 2011, 08:29:22 AM

Quote from: milesc on May 23, 2011, 07:18:55 AM

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.

eleuthria

legendary

Activity: 1750

Merit: 1007

Quote from: d3athrow on May 24, 2011, 02:46:18 AM

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.

Quote from: xanadu on May 24, 2011, 12:21:55 AM

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 Wink

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.

EpicBacon

member

Activity: 94

Merit: 10

Quote from: andrepcg on May 24, 2011, 03:19:56 AM

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.

andrepcg

full member

Activity: 230

Merit: 100

i have this question regarding block confirmations.

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

thanks!

d3athrow

newbie

Activity: 24

Merit: 0

Quote from: eleuthria on May 23, 2011, 11:51:25 PM

Quote from: steelhouse on May 23, 2011, 11:36:13 PM

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

lebish

newbie

Activity: 36

Merit: 0

Quote from: eleuthria on May 23, 2011, 08:29:22 AM

Quote from: milesc on May 23, 2011, 07:18:55 AM

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.

IlbiStarz

full member

Activity: 336

Merit: 100

Quote from: xanadu on May 24, 2011, 12:21:55 AM

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 Wink

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.

xanadu

member

Activity: 63

Merit: 10

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 Wink

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

full member

Activity: 336

Merit: 100

Quote from: eleuthria on May 23, 2011, 11:51:25 PM

Quote from: steelhouse on May 23, 2011, 11:36:13 PM

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 Sad

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

eleuthria

legendary

Activity: 1750

Merit: 1007

Quote from: steelhouse on May 23, 2011, 11:36:13 PM

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.

steelhouse

hero member

Activity: 717

Merit: 501

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

d3athrow

newbie

Activity: 24

Merit: 0

been getting a lot of this today

Quote

[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

IlbiStarz

full member

Activity: 336

Merit: 100

Wow 6 hours for one block and counting...unlucky Sad

zapeta

full member

Activity: 180

Merit: 100

I've had about 1.5% stale shares over the last ~24 hours. Is this high, or about a normal percentage?

I'm using Phoenix miner 1.48 on a 5850 and 5870.

eleuthria

legendary

Activity: 1750

Merit: 1007

There is going to be a change to the 24 hour payout lock when a wallet is changed. Since some people take payouts directly to sites like MtGox which generate a new address for each deposit, the lock would disable that capability.

Later this evening, I will push a change that turns the lock off by default. When you log in to your account, you will see a warning on the left side stating: "Your balance is not protected from a wallet address change, click here for more information.".

On that page will be two options:
1) Turn on balance locking
2) Leave balance locking off.

Turning the balance locking on is a permanent change that cannot be undone. Once turned on, payouts are disabled for 24 hours after a wallet address is changed. This is the encouraged option. Leaving this off creates a potential vulnerability if your system were compromised and somebody logged into your account.

w128

newbie

Activity: 14

Merit: 0