I think you should have
Pool Information
o Block Statistics
o Hall of Fame
o Api Support
BTCGuild
o What is BTC Guild
o How to Connect
o FAQ - Frequently Asked Questions
Topic: [~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 149. (Read 379078 times)
May 12, 2011, 06:11:25 PM
May 12, 2011, 05:14:54 PM
brilliant, thx, will use it!
May 12, 2011, 05:09:24 PM
click, added 1gh/s to pool.
i have 2 requests/ideas for features though:
allow to check worker status via api so this very nice sidebar gadget can be used:
https://bitcointalksearch.org/topic/windows-sidebar-gadget-supports-deepbitslusheligiusbtcminebtcguild-7071
and also i would love if i could check miner status on the go with the android app
http://www.appbrain.com/app/miner-status/me.davidgreene.minerstatus
i have 2 requests/ideas for features though:
allow to check worker status via api so this very nice sidebar gadget can be used:
https://bitcointalksearch.org/topic/windows-sidebar-gadget-supports-deepbitslusheligiusbtcminebtcguild-7071
and also i would love if i could check miner status on the go with the android app
http://www.appbrain.com/app/miner-status/me.davidgreene.minerstatus
Worker status is part of the API (go to "My API Settings" for your URL). My pool was added to the sidebar gadget you linked this morning
. I'll send a message to the guys that make the miner status app to see if they can get BTC Guild included. May 12, 2011, 05:06:51 PM
@cschmitz you could otherwise use my own tool and add it into your android bookmarks 
May 12, 2011, 04:58:30 PM
click, added 1gh/s to pool.
i have 2 requests/ideas for features though:
allow to check worker status via api so this very nice sidebar gadget can be used:
https://bitcointalksearch.org/topic/windows-sidebar-gadget-supports-deepbitslusheligiusbtcminebtcguild-7071
and also i would love if i could check miner status on the go with the android app
http://www.appbrain.com/app/miner-status/me.davidgreene.minerstatus
i have 2 requests/ideas for features though:
allow to check worker status via api so this very nice sidebar gadget can be used:
https://bitcointalksearch.org/topic/windows-sidebar-gadget-supports-deepbitslusheligiusbtcminebtcguild-7071
and also i would love if i could check miner status on the go with the android app
http://www.appbrain.com/app/miner-status/me.davidgreene.minerstatus
May 12, 2011, 01:22:59 PM
something with your Worker Speed calculations must be wrong (or maybe it just doesn't do anything at all).
it's only the Speed display though, nothing for users to worry about.
i just noticed that it shows very low numbers according to my miners and actually doesnt change at all, even after half an hour (which seemed strange if it's an estimate based on the last 15minutes),
so i did a short test,
reset my worker-stats, wrote down the Round Duration Time,
waited a couple of minutes and reloaded the page,
checked the Round Duration Time, Shares in that timeframe and did some maths.
share-count is fine and fits to my workers work (aprox. 1.7Ghash/s), Worker Speed still shows 978.30Mhash/s (like written in stone, for about the last hour or so).
it's only the Speed display though, nothing for users to worry about.
i just noticed that it shows very low numbers according to my miners and actually doesnt change at all, even after half an hour (which seemed strange if it's an estimate based on the last 15minutes),
so i did a short test,
reset my worker-stats, wrote down the Round Duration Time,
waited a couple of minutes and reloaded the page,
checked the Round Duration Time, Shares in that timeframe and did some maths.
share-count is fine and fits to my workers work (aprox. 1.7Ghash/s), Worker Speed still shows 978.30Mhash/s (like written in stone, for about the last hour or so).
I'll take a look when I get home from work today. I just checked on my account and my worker speed changes every minute in line with the pool stats update.
May 12, 2011, 01:21:00 PM
something with your Worker Speed calculations must be wrong (or maybe it just doesn't do anything at all).
it's only the Speed display though, nothing for users to worry about.
i just noticed that it shows very low numbers according to my miners and actually doesnt change at all, even after half an hour (which seemed strange if it's an estimate based on the last 15minutes),
so i did a short test,
reset my worker-stats, wrote down the Round Duration Time,
waited a couple of minutes and reloaded the page,
checked the Round Duration Time, Shares in that timeframe and did some maths.
share-count is fine and fits to my workers work (aprox. 1.7Ghash/s), Worker Speed still shows 978.30Mhash/s (like written in stone, for about the last hour or so).
it's only the Speed display though, nothing for users to worry about.
i just noticed that it shows very low numbers according to my miners and actually doesnt change at all, even after half an hour (which seemed strange if it's an estimate based on the last 15minutes),
so i did a short test,
reset my worker-stats, wrote down the Round Duration Time,
waited a couple of minutes and reloaded the page,
checked the Round Duration Time, Shares in that timeframe and did some maths.
share-count is fine and fits to my workers work (aprox. 1.7Ghash/s), Worker Speed still shows 978.30Mhash/s (like written in stone, for about the last hour or so).
May 12, 2011, 01:08:30 PM
Hi,
I've added support for your pool in my Worker status monitor, but I'm having a few problems with your API:
-No unit for pool hash rate and worker hash rate: pool=24.95, my worker=171.80
obviously I can't be faster than the pool, so I could manage that on my side (but, then, what to say about users doing 10Ghash/s or 10Mhash/s, how to tell?), I think it would be better to put both speeds in Mhash/s
-Time since last share: easy to read, but it could be better if it were formatted differently, for example hh:mm or something like that
OR maybe you could incorporate a dead/alive status (as in Deepbit, depending on time since last share
Besides that, great job on the web site, I really like how all the important information can be seen in a glimpse on the account page
I've added support for your pool in my Worker status monitor, but I'm having a few problems with your API:
-No unit for pool hash rate and worker hash rate: pool=24.95, my worker=171.80
obviously I can't be faster than the pool, so I could manage that on my side (but, then, what to say about users doing 10Ghash/s or 10Mhash/s, how to tell?), I think it would be better to put both speeds in Mhash/s
-Time since last share: easy to read, but it could be better if it were formatted differently, for example hh:mm or something like that
OR maybe you could incorporate a dead/alive status (as in Deepbit, depending on time since last share
Besides that, great job on the web site, I really like how all the important information can be seen in a glimpse on the account page
Pool hash rate is in gH/sec, since it will never drop below 1 gH/sec unless something breaks. Worker hash rates are mH/sec. I set them that way for easy printing for people who didn't want to convert speeds based on size. I will swap them both to mH/sec though for consistency. Anybody who is parsing out a JSON API should have the ability to divide by 1000 as needed
.I'll convert time since last share to HH:MM:SS as well.
UPDATE: The changes mentioned above are now in effect. Time since last share is now H:MM:SS, pool speed is sent as mH/sec to stay consistent with worker speeds.
May 12, 2011, 01:01:50 PM
Hi,
I've added support for your pool in my Worker status monitor, but I'm having a few problems with your API:
-No unit for pool hash rate and worker hash rate: pool=24.95, my worker=171.80
obviously I can't be faster than the pool, so I could manage that on my side (but, then, what to say about users doing 10Ghash/s or 10Mhash/s, how to tell?), I think it would be better to put both speeds in Mhash/s
-Time since last share: easy to read, but it could be better if it were formatted differently, for example hh:mm or something like that
OR maybe you could incorporate a dead/alive status (as in Deepbit, depending on time since last share
Besides that, great job on the web site, I really like how all the important information can be seen in a glimpse on the account page
I've added support for your pool in my Worker status monitor, but I'm having a few problems with your API:
-No unit for pool hash rate and worker hash rate: pool=24.95, my worker=171.80
obviously I can't be faster than the pool, so I could manage that on my side (but, then, what to say about users doing 10Ghash/s or 10Mhash/s, how to tell?), I think it would be better to put both speeds in Mhash/s
-Time since last share: easy to read, but it could be better if it were formatted differently, for example hh:mm or something like that
OR maybe you could incorporate a dead/alive status (as in Deepbit, depending on time since last share
Besides that, great job on the web site, I really like how all the important information can be seen in a glimpse on the account page
May 12, 2011, 12:51:57 PM
Thank you for all the support, especially the generous donators giving above and beyond the 2.5% amount I've set as the "invalid protection+instant payout" threshold.
When I started the pool, I did not expect to see anywhere near this level of generosity, which is why I decided to consider the pool 0% fee (nothing off the top), and just rounding the user rewards down at the 0.000X level. The donations being received completely dwarf the rounding kept by the pool, which was already very insignificant [0.024%]. As a result, I will be changing the pool to round down to the 8th decimal, the limit of what BitCoin supports.
This change will be going live this evening, and be applied to all future blocks.
When I started the pool, I did not expect to see anywhere near this level of generosity, which is why I decided to consider the pool 0% fee (nothing off the top), and just rounding the user rewards down at the 0.000X level. The donations being received completely dwarf the rounding kept by the pool, which was already very insignificant [0.024%]. As a result, I will be changing the pool to round down to the 8th decimal, the limit of what BitCoin supports.
This change will be going live this evening, and be applied to all future blocks.
Wow, thank you! This will help many lower production users.
May 12, 2011, 12:44:27 PM
Thank you for all the support, especially the generous donators giving above and beyond the 2.5% amount I've set as the "invalid protection+instant payout" threshold.
When I started the pool, I did not expect to see anywhere near this level of generosity, which is why I decided to consider the pool 0% fee (nothing off the top), and just rounding the user rewards down at the 0.000X level. The donations being received completely dwarf the rounding kept by the pool, which was already very insignificant [0.024%]. As a result, I will be changing the pool to round down to the 8th decimal, the limit of what BitCoin supports.
This change will be going live this evening, and be applied to all future blocks.
When I started the pool, I did not expect to see anywhere near this level of generosity, which is why I decided to consider the pool 0% fee (nothing off the top), and just rounding the user rewards down at the 0.000X level. The donations being received completely dwarf the rounding kept by the pool, which was already very insignificant [0.024%]. As a result, I will be changing the pool to round down to the 8th decimal, the limit of what BitCoin supports.
This change will be going live this evening, and be applied to all future blocks.
May 12, 2011, 12:11:48 PM
Yesterday I was running strong and now for whatever reason neither of my GPUs are doing squat against the pool:
I average ~320Mh/s on each GPU but I either get connection issues or only a few Khash/s.
Ideas
I average ~320Mh/s on each GPU but I either get connection issues or only a few Khash/s.
Ideas
Have you tried stopping/starting? We're still running strong with over 25 gH/sec right now.
May 12, 2011, 12:08:49 PM
Yesterday I was running strong and now for whatever reason neither of my GPUs are doing squat against the pool:
http://b.oss.im//a6/a7wvlita80gsw.png
I average ~320Mh/s on each GPU but I either get connection issues or only a few Khash/s.
Ideas
http://b.oss.im//a6/a7wvlita80gsw.png
I average ~320Mh/s on each GPU but I either get connection issues or only a few Khash/s.
Ideas
May 12, 2011, 11:52:20 AM
Hmm, I'm having a different sort of problem, though. 
I can't connect using the Ufasoft bitcoin-miner 0.10 CPU miner, it stays at 0 MHash/sec.
These are the contents of the .bat I'm using to connect:
I can't spot any mistake, and it's pretty much the same I've been using to connect to other pools before.
EDIT: I found the possible cause of the issues:
I can't connect using the Ufasoft bitcoin-miner 0.10 CPU miner, it stays at 0 MHash/sec.These are the contents of the .bat I'm using to connect:
Code:
start /D "C:\Users\ChaosFox\Documents" bitcoin-miner.exe -o http://btcguild.com:8332 -u ChaosFox_xxxxxxxx -p xxxxxxxx
I can't spot any mistake, and it's pretty much the same I've been using to connect to other pools before.
EDIT: I found the possible cause of the issues:
After some work with luke-jr, I can now say that ufasoft now works with his pool (Eligius).
Typical command line
bitcoin-miner.exe -a 5 -o http://pool.bitcoin.dashjr.org:8337 -u -p
what i like about luke's pool is that you can use port 80 too (great for NATs) and you don't need to register on a website,
you just send the payment address in the user and you receive payments when they go above 1 BTC.
I saw there were posts here having problems with bitpenny pool too so i will write what solved the issue here (it might be the same problem there).
The problem used to be:
after running bitcoin-miner.exe, it would just get stuck on 0 MH/sec.
the problem was with the pool because it didn't obey this requirement:
"The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource."
This was fixed.
Typical command line
bitcoin-miner.exe -a 5 -o http://pool.bitcoin.dashjr.org:8337 -u
what i like about luke's pool is that you can use port 80 too (great for NATs) and you don't need to register on a website,
you just send the payment address in the user and you receive payments when they go above 1 BTC.
I saw there were posts here having problems with bitpenny pool too so i will write what solved the issue here (it might be the same problem there).
The problem used to be:
after running bitcoin-miner.exe, it would just get stuck on 0 MH/sec.
the problem was with the pool because it didn't obey this requirement:
"The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource."
This was fixed.
May 12, 2011, 11:42:11 AM
For anybody that saw RPC errors last night around 9-10 PM (PST), this was due to a database update on the shares table which may have caused share/authentication issues during a few small windows of 2 minutes.
Another small window of RPC errors this morning around 6 AM (PST) when the mysql server was restarted. There may have been a few miner idles around 9 AM, due to the pool calculating rewards on 2 blocks in quick succession. This will be resolved this weekend when I optimize the way the server calculates rewards to split the processing time into multiple small chunks rather than all at once.
For now, the only time you should see a communication error or miner idle is when: A) Your connection (or a node en route to the server) goes down or B) A block was just solved and is being calculated.
Another small window of RPC errors this morning around 6 AM (PST) when the mysql server was restarted. There may have been a few miner idles around 9 AM, due to the pool calculating rewards on 2 blocks in quick succession. This will be resolved this weekend when I optimize the way the server calculates rewards to split the processing time into multiple small chunks rather than all at once.
For now, the only time you should see a communication error or miner idle is when: A) Your connection (or a node en route to the server) goes down or B) A block was just solved and is being calculated.
May 12, 2011, 10:58:31 AM
And another? very lucky round!
Yeah, it looks like 3 different blocks were found in the span of about 2 minutes, hahaha.
(And a 4th block only 3 minutes after that.)
Actually, that 4th block was *another* one of ours! Too bad I didn't find any shares during the intervening 3 minutes...
May 12, 2011, 10:57:56 AM
And another? very lucky round!
Yeah, it looks like 3 different blocks were found in the span of about 2 minutes, hahaha.
(And a 4th block only 3 minutes after that.)
Not quite. 3 blocks were found in the course of an hour and a half. One was a long block that finally ended, then a 1h 23m, and then a 3m block
. May 12, 2011, 10:57:46 AM
Woohoo,
Found my first block ever.
Found my first block ever.
May 12, 2011, 10:56:21 AM
And another? very lucky round!
Yeah, it looks like 3 different blocks were found in the span of about 2 minutes, hahaha.
(And a 4th block only 3 minutes after that.)
May 12, 2011, 10:55:06 AM
Whooooo! Another new block! Good job guys.
And another!!!
Wow, 2 full blocks generated in 1h 26m, not bad for how small the pool is right now, VERY lucky
. Jump to: