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

[IlbiStarz]

Nvm

[1713549881]

1713549881

[1713549881]

1713549881

[1713549881]

1713549881

[Veldy]

Wow, I hope you have funds in an exchange to buy coins if you fall short.  "Futures" on bitcoins seem extremely risky to me.

I've got a stash of coins in a savings wallet, I'm just doing my damnedest to not dip in to it!

Good man

[swerving]

So wait, now that there are 3 servers with 3 separate hashing speeds, does that mean that the rewards variance is higher?

Or, in other words, is BTC Guild now 3 300 ghash/sec pools instead of one 900 one for rewards purposes? Yeah, I know it'll all even out in a week anyway but the difficulty increases about that often and I want to reduce my risk.

[eleuthria]

So wait, now that there are 3 servers with 3 separate hashing speeds, does that mean that the rewards variance is higher?

Or, in other words, is BTC Guild now 3 300 ghash/sec pools instead of one 900 one for rewards purposes? Yeah, I know it'll all even out in a week anyway but the difficulty increases about that often and I want to reduce my risk.

Rewards are combined between the 3 pool servers.  This is the exact same as running on a single large pool, I've just split it across multiple datacenters in order to provide members with the option to manually point to a closer server.

[swerving]

So wait, now that there are 3 servers with 3 separate hashing speeds, does that mean that the rewards variance is higher?

Or, in other words, is BTC Guild now 3 300 ghash/sec pools instead of one 900 one for rewards purposes? Yeah, I know it'll all even out in a week anyway but the difficulty increases about that often and I want to reduce my risk.

Rewards are combined between the 3 pool servers.  This is the exact same as running on a single large pool, I've just split it across multiple datacenters in order to provide members with the option to manually point to a closer server.

Ah, cool, thanks for answering.

[TheMoneyStorm]

Awesome job, Everthing looks great. Just turned up my donation. Keep up the great work 

[chris2OOx9]

Turned up my donation too 

[Burt]

Getting this error: HTTP Error 500 (Internal Server Error): An unexpected condition was encountered while the server was attempting to fulfill the request.

while trying to acess my_account.php

[pun1sh3r]

Nice job with this pool and the interface, i like it a lot. Just upped my donation to 2.5% as well.

[Kirks]

What is up with all the long poll messages?
Normal or no?  (There are two miners worth there)

Code:

2011-06-08 19:42:19: Listener for "6952": 08/06/2011 19:42:19, Problems communicating with bitcoin RPC
2011-06-08 19:43:02: Listener for "6952": 08/06/2011 19:43:02, warning: job finished, miner is idle
2011-06-08 19:43:05: Listener for "6951": 08/06/2011 19:43:05, warning: job finished, miner is idle
2011-06-08 19:45:27: Listener for "6952": 08/06/2011 19:45:27, long poll: new block 0000114ee8a5443c
2011-06-08 19:45:27: Listener for "6951": 08/06/2011 19:45:27, long poll: new block 0000114ee8a5443c
2011-06-08 19:45:53: Listener for "6952": 08/06/2011 19:45:53, long poll: new block 000011747f866043
2011-06-08 19:45:55: Listener for "6951": 08/06/2011 19:45:55, long poll: new block 000011747f866043
2011-06-08 19:47:58: Listener for "6951": 08/06/2011 19:47:58, warning: job finished, miner is idle
2011-06-08 19:48:15: Listener for "6951": 08/06/2011 19:48:15, warning: job finished, miner is idle
2011-06-08 19:48:56: Listener for "6952": 08/06/2011 19:48:56, warning: job finished, miner is idle
2011-06-08 19:49:28: Listener for "6952": 08/06/2011 19:49:28, Problems communicating with bitcoin RPC
2011-06-08 19:49:33: Listener for "6951": 08/06/2011 19:49:33, warning: job finished, miner is idle
2011-06-08 19:50:13: Listener for "6951": 08/06/2011 19:50:13, warning: job finished, miner is idle
2011-06-08 19:50:13: Listener for "6952": 08/06/2011 19:50:13, warning: job finished, miner is idle
2011-06-08 19:51:22: Listener for "6952": 08/06/2011 19:51:22, long poll: new block 0000098bea933ad9
2011-06-08 19:51:24: Listener for "6951": 08/06/2011 19:51:24, long poll: new block 0000098bea933ad9
2011-06-08 19:53:43: Listener for "6952": 08/06/2011 19:53:43, long poll: new block 000011106f08af34
2011-06-08 19:53:43: Listener for "6951": 08/06/2011 19:53:43, long poll: new block 000011106f08af34
2011-06-08 19:57:52: Listener for "6951": 08/06/2011 19:57:52, long poll: new block 00000d9c759bee77
2011-06-08 19:57:52: Listener for "6952": 08/06/2011 19:57:52, long poll: new block 00000d9c759bee77
2011-06-08 20:07:56: Listener for "6951": 08/06/2011 20:07:56, long poll: new block 00001c427502ea51
2011-06-08 20:07:56: Listener for "6952": 08/06/2011 20:07:56, long poll: new block 00001c427502ea51
2011-06-08 20:09:37: Listener for "6952": 08/06/2011 20:09:37, long poll: new block 000008ca2aea3c2b
2011-06-08 20:09:38: Listener for "6951": 08/06/2011 20:09:38, long poll: new block 000008ca2aea3c2b
2011-06-08 20:13:25: Listener for "6951": 08/06/2011 20:13:25, long poll: new block 000011a1aaf8d56e
2011-06-08 20:13:27: Listener for "6952": 08/06/2011 20:13:27, long poll: new block 000011a1aaf8d56e
2011-06-08 20:18:46: Listener for "6951": 08/06/2011 20:18:46, warning: job finished, miner is idle
2011-06-08 20:18:47: Listener for "6952": 08/06/2011 20:18:47, long poll: new block 00001c42d2e97991
2011-06-08 20:18:47: Listener for "6951": 08/06/2011 20:18:47, long poll: new block 00001c42d2e97991
2011-06-08 20:18:47: Listener for "6951": 08/06/2011 20:18:47, Problems communicating with bitcoin RPC
2011-06-08 20:19:25: Listener for "6952": 08/06/2011 20:19:25, long poll: new block 00000710b6d36cd3
2011-06-08 20:19:25: Listener for "6951": 08/06/2011 20:19:25, long poll: new block 00000710b6d36cd3
2011-06-08 20:26:32: Listener for "6952": 08/06/2011 20:26:32, long poll: new block 000012aebf5e374a
2011-06-08 20:26:32: Listener for "6951": 08/06/2011 20:26:32, long poll: new block 000012aebf5e374a
2011-06-08 20:36:36: Listener for "6952": 08/06/2011 20:36:36, Problems communicating with bitcoin RPC
2011-06-08 20:36:38: Listener for "6951": 08/06/2011 20:36:38, long poll: new block 00000fd9a0f09bc0
2011-06-08 20:36:41: Listener for "6952": 08/06/2011 20:36:41, long poll: new block 00000fd9a0f09bc0
2011-06-08 20:40:33: Listener for "6951": 08/06/2011 20:40:33, long poll: new block 00000f83b32eb8ff
2011-06-08 20:40:33: Listener for "6952": 08/06/2011 20:40:33, long poll: new block 00000f83b32eb8ff
2011-06-08 20:41:32: Listener for "6952": 08/06/2011 20:41:32, long poll: new block 00000240166312b4
2011-06-08 20:41:32: Listener for "6951": 08/06/2011 20:41:32, long poll: new block 00000240166312b4

[CubedRoot]

This was the exact reason I moved to   different pool.  All those LP pushes were killing my GPU's

[Burt]

lolwut 5 min block

[ThatCoolCat]

What is up with all the long poll messages?
Normal or no?  (There are two miners worth there)

Code:

2011-06-08 19:42:19: Listener for "6952": 08/06/2011 19:42:19, Problems communicating with bitcoin RPC
2011-06-08 19:43:02: Listener for "6952": 08/06/2011 19:43:02, warning: job finished, miner is idle
2011-06-08 19:43:05: Listener for "6951": 08/06/2011 19:43:05, warning: job finished, miner is idle
2011-06-08 19:45:27: Listener for "6952": 08/06/2011 19:45:27, long poll: new block 0000114ee8a5443c
2011-06-08 19:45:27: Listener for "6951": 08/06/2011 19:45:27, long poll: new block 0000114ee8a5443c
2011-06-08 19:45:53: Listener for "6952": 08/06/2011 19:45:53, long poll: new block 000011747f866043
2011-06-08 19:45:55: Listener for "6951": 08/06/2011 19:45:55, long poll: new block 000011747f866043
2011-06-08 19:47:58: Listener for "6951": 08/06/2011 19:47:58, warning: job finished, miner is idle
2011-06-08 19:48:15: Listener for "6951": 08/06/2011 19:48:15, warning: job finished, miner is idle
2011-06-08 19:48:56: Listener for "6952": 08/06/2011 19:48:56, warning: job finished, miner is idle
2011-06-08 19:49:28: Listener for "6952": 08/06/2011 19:49:28, Problems communicating with bitcoin RPC
2011-06-08 19:49:33: Listener for "6951": 08/06/2011 19:49:33, warning: job finished, miner is idle
2011-06-08 19:50:13: Listener for "6951": 08/06/2011 19:50:13, warning: job finished, miner is idle
2011-06-08 19:50:13: Listener for "6952": 08/06/2011 19:50:13, warning: job finished, miner is idle
2011-06-08 19:51:22: Listener for "6952": 08/06/2011 19:51:22, long poll: new block 0000098bea933ad9
2011-06-08 19:51:24: Listener for "6951": 08/06/2011 19:51:24, long poll: new block 0000098bea933ad9
2011-06-08 19:53:43: Listener for "6952": 08/06/2011 19:53:43, long poll: new block 000011106f08af34
2011-06-08 19:53:43: Listener for "6951": 08/06/2011 19:53:43, long poll: new block 000011106f08af34
2011-06-08 19:57:52: Listener for "6951": 08/06/2011 19:57:52, long poll: new block 00000d9c759bee77
2011-06-08 19:57:52: Listener for "6952": 08/06/2011 19:57:52, long poll: new block 00000d9c759bee77
2011-06-08 20:07:56: Listener for "6951": 08/06/2011 20:07:56, long poll: new block 00001c427502ea51
2011-06-08 20:07:56: Listener for "6952": 08/06/2011 20:07:56, long poll: new block 00001c427502ea51
2011-06-08 20:09:37: Listener for "6952": 08/06/2011 20:09:37, long poll: new block 000008ca2aea3c2b
2011-06-08 20:09:38: Listener for "6951": 08/06/2011 20:09:38, long poll: new block 000008ca2aea3c2b
2011-06-08 20:13:25: Listener for "6951": 08/06/2011 20:13:25, long poll: new block 000011a1aaf8d56e
2011-06-08 20:13:27: Listener for "6952": 08/06/2011 20:13:27, long poll: new block 000011a1aaf8d56e
2011-06-08 20:18:46: Listener for "6951": 08/06/2011 20:18:46, warning: job finished, miner is idle
2011-06-08 20:18:47: Listener for "6952": 08/06/2011 20:18:47, long poll: new block 00001c42d2e97991
2011-06-08 20:18:47: Listener for "6951": 08/06/2011 20:18:47, long poll: new block 00001c42d2e97991
2011-06-08 20:18:47: Listener for "6951": 08/06/2011 20:18:47, Problems communicating with bitcoin RPC
2011-06-08 20:19:25: Listener for "6952": 08/06/2011 20:19:25, long poll: new block 00000710b6d36cd3
2011-06-08 20:19:25: Listener for "6951": 08/06/2011 20:19:25, long poll: new block 00000710b6d36cd3
2011-06-08 20:26:32: Listener for "6952": 08/06/2011 20:26:32, long poll: new block 000012aebf5e374a
2011-06-08 20:26:32: Listener for "6951": 08/06/2011 20:26:32, long poll: new block 000012aebf5e374a
2011-06-08 20:36:36: Listener for "6952": 08/06/2011 20:36:36, Problems communicating with bitcoin RPC
2011-06-08 20:36:38: Listener for "6951": 08/06/2011 20:36:38, long poll: new block 00000fd9a0f09bc0
2011-06-08 20:36:41: Listener for "6952": 08/06/2011 20:36:41, long poll: new block 00000fd9a0f09bc0
2011-06-08 20:40:33: Listener for "6951": 08/06/2011 20:40:33, long poll: new block 00000f83b32eb8ff
2011-06-08 20:40:33: Listener for "6952": 08/06/2011 20:40:33, long poll: new block 00000f83b32eb8ff
2011-06-08 20:41:32: Listener for "6952": 08/06/2011 20:41:32, long poll: new block 00000240166312b4
2011-06-08 20:41:32: Listener for "6951": 08/06/2011 20:41:32, long poll: new block 00000240166312b4

I'm not getting that anywhere close to that level of LPs, (using US East)

[ThatCoolCat]

lolwut 5 min block

The best kind of block

[gll]

shares(stales)
76 (60)    

lol

[PcChip]

So wait, now that there are 3 servers with 3 separate hashing speeds, does that mean that the rewards variance is higher?

Or, in other words, is BTC Guild now 3 300 ghash/sec pools instead of one 900 one for rewards purposes? Yeah, I know it'll all even out in a week anyway but the difficulty increases about that often and I want to reduce my risk.

Rewards are combined between the 3 pool servers.  This is the exact same as running on a single large pool, I've just split it across multiple datacenters in order to provide members with the option to manually point to a closer server.

That's not why he was asking; he was asking to find out if it is now three separate independent hashing pools, each trying to find a block separately at 200 GH/s, or if the hashes are being directed to one main pool for a rate of 600 GH/s.  Three smaller pools would find blocks slower each, so the variance would be high

[ThatCoolCat]

So wait, now that there are 3 servers with 3 separate hashing speeds, does that mean that the rewards variance is higher?

Or, in other words, is BTC Guild now 3 300 ghash/sec pools instead of one 900 one for rewards purposes? Yeah, I know it'll all even out in a week anyway but the difficulty increases about that often and I want to reduce my risk.

Rewards are combined between the 3 pool servers.  This is the exact same as running on a single large pool, I've just split it across multiple datacenters in order to provide members with the option to manually point to a closer server.

That's not why he was asking; he was asking to find out if it is now three separate independent hashing pools, each trying to find a block separately at 200 GH/s, or if the hashes are being directed to one main pool for a rate of 600 GH/s.  Three smaller pools would find blocks slower each, so the variance would be high

Uh no eleuthria answered the question

This is the exact same as running on a single large pool

[iCEBREAKER]

lolwut 5 min block

The best kind of block

When The Guild controls over 50% of bitspace, we can sneak ourselves all the 5 minute blocks we want.  /evil plot

[eleuthria]

API is currently polling some stats incorrectly. This should be fixed early tomorrow morning.

[CubedRoot]

lolwut 5 min block

The best kind of block

When The Guild controls over 50% of bitspace, we can sneak ourselves all the 5 minute blocks we want.  /evil plot

To bad that block was invalid... I hope everyone was donating 2.5%