[CLOSED] BTCMine - ZERO fee mining pool (LP, SSL, JSON API, P2SH)

[SgtSpike]

Awesome, thanks dbitcoin!

[shivansps]

make some room, im adding another 2 5850 in a few minutes... 1.7Ghash here i go.

[Veldy]

Requesting a feature:  24 hr production statistic

Deepbit has this, and it was a very convenient metric to have.  I could easily take that number and determine whether I was still operating in the range of profitability, how profitable it was, etc.  As it is, on BTCMine, I have no way to really know how much I am making per day, without tracking it manually.

I would prefer to see a "last 24 hours" measurement, but if you can only do it on a per day basis (i.e., all the bitcoins mined on 5/31 = 5.5BTC), then that's ok too.  Just SOMETHING for me to be able to track how much I am currently generating per day!

24h stats currently available by email, if you enable option "Send me pool stats every 24h" in your profile.
In the next update I will add these numbers to profile.

Is this implemented the same way it has been?  It always showed my hash rate as of the time the email was sent [it didn't average the hash rate for the entire day]. 

[dbitcoin]

Is this implemented the same way it has been?  It always showed my hash rate as of the time the email was sent [it didn't average the hash rate for the entire day]. 

Overall hashrate not averaged for 24h. Only for last hour.
I slowly rewrite all stats calculation, so this maybe changed in the future.

[xf2_org]

At 1:16 am EST (right now), my 2xpoclbm setup has been showing several minutes worth of "invalid or share" shares.

Switching over to slush's pool yields valid shares again, as expected.

This long string of invalid shares happened earlier tonight as well, though I did not record the time.

Code:

01/06/2011 01:07:03, ad105eba, accepted                     
01/06/2011 01:07:06, 7b5b48ff, accepted                     
01/06/2011 01:07:29, 76f35c6f, invalid or stale             
01/06/2011 01:07:50, 6300017c, invalid or stale             
01/06/2011 01:08:07, 27e4f248, invalid or stale             
01/06/2011 01:08:09, 59bfd477, invalid or stale             
[...]

[btcLeger]

uhmmm.... actual round has 2204037 shares submitted? How unlikely is that? Sure everythings working fine atm?

[eleuthria]

uhmmm.... actual round has 2204037 shares submitted? How unlikely is that? Sure everythings working fine atm?

A 2m round, while uncommon, is not a sign of anything being broken.  I can recall a few pools which had even longer rounds back when the difficulty was half of what it is now.  It's just an unlucky round for the pool.

[russelljohnson]

another looooooooooong round =[

[btcLeger]

A 2m round, while uncommon, is not a sign of anything being broken.  I can recall a few pools which had even longer rounds back when the difficulty was half of what it is now.  It's just an unlucky round for the pool.

I see its unlikely but not impossible. I was wondering because I also had a huge amount of stale shares during that round.

[Horkabork]

I'm also still getting large numbers of stales. About 6.5% on average, most of them right before Long Poll work pushes.

[Veldy]

I'm also still getting large numbers of stales. About 6.5% on average, most of them right before Long Poll work pushes.

What miner are you using?  The reason that I ask is that Phoenix 1.48 was giving me far more rejected shares than poclbm (latest).  I suspect this is because how many more shares there are in a round, but I am not sure why that should make any real difference. 

[Horkabork]

I'm also still getting large numbers of stales. About 6.5% on average, most of them right before Long Poll work pushes.

What miner are you using?  The reason that I ask is that Phoenix 1.48 was giving me far more rejected shares than poclbm (latest).  I suspect this is because how many more shares there are in a round, but I am not sure why that should make any real difference. 

Phoenix 1.48 with phatk. It worked perfectly fine before the DDOS event, and it's only this pool that has the problem. I'll try poclbm in a bit, though. Thanks for the advice.

[Veldy]

I'm also still getting large numbers of stales. About 6.5% on average, most of them right before Long Poll work pushes.

What miner are you using?  The reason that I ask is that Phoenix 1.48 was giving me far more rejected shares than poclbm (latest).  I suspect this is because how many more shares there are in a round, but I am not sure why that should make any real difference. 

Phoenix 1.48 with phatk. It worked perfectly fine before the DDOS event, and it's only this pool that has the problem. I'll try poclbm in a bit, though. Thanks for the advice.

I think BTCMine is probably a bit slower with long polling push due to the rapid expansion that occurred when deepbit.net went down from the DDOS and so many of its users flooded into BTCMine [and didn't leave after deepbit came back up].  poclbm should help, but it probably won't be the magic panacea that you are looking for ... maybe it will though; I would certainly like to see the results (I hope that you indicate that over say, 3000 shares, you see a reduction of 50% rejected).  dbitcoin indicated that registration was closed until the pool was moved to a new server and I assume that has not taken place yet. 

There is only one catch.  You will not be able to tell how many are rejected if you use the command line version unless you pipe the output and capture the information [or use GUIMiner v2011-05-21 assuming you are on Windows]. 

And then my pipe dream bubble below that isn't exactly related:

If I get the time, perhaps I will write a little .NET application to gather all information about pool (address, port, maybe some JSON stats), worker, miner configuration, hardware stats (i.e. video card [with miner], CPU, usage stats, GPU temp ....),  submitted shares, rejected shares, date and time of each submission, the hash value itself, long polling pushes, idle time waiting for work (including date time and duration) and of course communication failures.  That may not be all that "storage" friendly however, so I may have to decide whether to keep a window of data [configurable?], what type of database to put it in [I think MySQL would work, since the app could then run on Mono under X11 and be happy].  It probably wouldn't be an easy to install application for the average user if I wrote it as I indicate, however, reducing the storage and and using a light weight local DB could work as well, but personally, I would love to see information for months or years at a time just out of curiosity.  I don't think putting the back end hosted on the Internet would be cost effective though since most people wouldn't use it and almost certainly wouldn't pay monthly for it.  I'll write it for myself at some point and maybe a few people will have interest in it   I wish I had more time to do it in the near term, I have a lot going on in my life right now [Daughter graduating high school and heading off to college, overtime with work, yada yada].

[shivansps]

epic 971 shares round lol

[russelljohnson]

way too many stale shares. I'm outa here. If you get more than 1% stale shares, do yourself a favor and leave.

[SgtSpike]

I am getting 4.8, 4.4, 4.8, and 2.0% stales on four of my miners.

Going to give BTCGuild a try I guess...  :\

[russelljohnson]

I am getting 4.8, 4.4, 4.8, and 2.0% stales on four of my miners.

Going to give BTCGuild a try I guess...  :\

I moved 2.4GH/s over to Guild. Looks clean.

[fireside]

So I am fairly new and i do not know if this is normal or if i am having a problem but it seems like a problem. At 6pm i had 1.84 total bounty. At 12:15am i still have 1.84 total bounty but my round shares keep going up. Says my estimated score is 1.80098586388e+19 and my round shares are 1339. Estimated bounty for the last 4 hrs has been .36 (256mh/s) but have not gotten a thing for 4hrs. Is something stuck or am i just on a ridiculously long block?? I did notice that Block# 128091 was there for like 4hrs i believe but in the last 2hrs we have done all the way up to block# 128104 if i am reading the statistics right. So is it just taking a while to get the bounty from the work because there was a long block, or am i reading it wrong and something is screwy with my account??  Or am i just working on my very own block all by myself?? lol

[russelljohnson]

So I am fairly new and i do not know if this is normal or if i am having a problem but it seems like a problem. At 6pm i had 1.84 total bounty. At 12:15am i still have 1.84 total bounty but my round shares keep going up. Says my estimated score is 1.80098586388e+19 and my round shares are 1339. Estimated bounty for the last 4 hrs has been .36 (256mh/s) but have not gotten a thing for 4hrs. Is something stuck or am i just on a ridiculously long block?? I did notice that Block# 128091 was there for like 4hrs i believe but in the last 2hrs we have done all the way up to block# 128104 if i am reading the statistics right. So is it just taking a while to get the bounty from the work because there was a long block, or am i reading it wrong and something is screwy with my account??  Or am i just working on my very own block all by myself?? lol

You guys just had a 7 hour round. Call it bad luck. =[

[Kluge]

Could we please have an ability to set # miners in "Miners" tab displayed per page via web GUI instead of having to set it to 25/50 manually every time I open the page?