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

[eleuthria]

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.

[1715464299]

1715464299

[1715464299]

1715464299

[1715464299]

1715464299

[1715464299]

1715464299

[ChaosFox]

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:

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 <your bitcoin address> -p <whatever>

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.
 

[shat]

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  

[eleuthria]

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  

Have you tried stopping/starting?  We're still running strong with over 25 gH/sec right now.

[eleuthria]

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.

[Muhahahahaz]

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.

Wow, thank you! This will help many lower production users.

[JohnDn]

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 

[eleuthria]

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  

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.

[BitLex]

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).

[eleuthria]

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).

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.

[cschmitz]

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:
http://bitcointalk.org/index.php?topic=7071.0
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

[JohnDn]

@cschmitz you could otherwise use my own tool and add it into your android bookmarks

[eleuthria]

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:
http://bitcointalk.org/index.php?topic=7071.0
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.

[cschmitz]

@cschmitz you could otherwise use my own tool and add it into your android bookmarks

brilliant, thx, will use it!

[steelhouse]

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

[ape]

Just updated my stats gadget to show the correct pool hashrate again (since it changed from gH to kH).

[matteumayo]

Just joined with 305 m/hash since deepbit has been giving me shitty shares

[Inaba]

Okay the miner status gadget is done, let me know what you guys think. You need .net 4.0 runtimes to use it.
I'm probably going to add a tab with graphs for hash rate and stale % tomorrow.
https://github.com/apeape/BTCGuild-Stats-Gadget

Nice app, but I have a few things that are causing problems:

1.  I have a lot of miners, the scrolling is tedious and annoying, you can only display 6.5 miners on the screen at a time.  It would be nice to be able to resize it. This includes vertical and horizontal, since there's lots of extra room on the right, so I have a completely mismatched window with not enough room vertically and too much room horizontally and no way to change it.
2. Miner colors configurable.  Maybe green for good and red for broken.  Being able to set thresholds for colors would be nice, too.  I have occasionally had miners overheat and start throttling, I'd like to see them listed in yellow.
3. Some graphical glitches when you try to resize the columns.  Makes the window borders blocky and broken.

This should probably be in another thread, though, so I apologize for hijacking this thread.

[Muhahahahaz]

The BTC Guild's average (expected) generation time is just 6 hours now!

[BitLex]

update on that WorkerSpeed bug:

have been mining some namecoins for a few hours,
when i switched my miners to it, the Worker Speed finaly changed and dropped from that 978.30Mhps to 0Mhps. 
however, put them back on the guild right after my namecoin-session, the WorkerSpeed went up to 944.89Mhps and now, about 30minutes later, still shows exactly 944.89Mhps (while workers crunch at ~1.7Ghps, based on share-calc).

it's 6 miners on a single worker-account, just for info.