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

[jjiimm_64]

sweet, blocks found info in my account page now, ty

i saw that too. i found 1 block for btc so far.

all i can say is that I am glad I am not solo mining...  when I first started  with 1 rig at slush.  I found a block on my second day.  I have been here a month avg over 4G and NO blocks yet.

[frozen]

sweet, blocks found info in my account page now, ty

i saw that too. i found 1 block for btc so far.

I have found 1 block as well.

Does anyone know if there is a way to determine the block number(s) of the blocks that we have solved?

To possibly answer my own question, I believe the "all blocks" page* shows which blocks we've solved. Invalid rows are colored pink, solved block rows might be colored light blue/gray. If this is the case, it looks like I am responsible for solving block 135600.

* https://www.btcguild.com/all_blocks.php

[eleuthria]

sweet, blocks found info in my account page now, ty

i saw that too. i found 1 block for btc so far.

I have found 1 block as well.

Does anyone know if there is a way to determine the block number(s) of the blocks that we have solved?

To possibly answer my own question, I believe the "all blocks" page* shows which blocks we've solved. Invalid rows are colored pink, solved block rows might be colored light blue/gray. If this is the case, it looks like I am responsible for solving block 135600.

* https://www.btcguild.com/all_blocks.php

Yes, I had a few minutes to spare and decided to get the Blocks Found to sync up with the master server when a round ends, and decided to take a couple minutes to color code block lists/block details:

If you found a block, it shows up with a blue background color in the block list/all blocks table.
When looking at block details, the block finder is highlighted in blue, you are highlighted in yellow.
If you found the block, your row will be highlighted in green.

[jjiimm_64]

E.
  thanks for the enhancements.  I for one am here for the stats and interface that you provide.

Any chance on implimenting a small reward for the worker that finds the block..  it would be a neat thing to look for. 1 btc would be kool, but even .25 would be fun to get, and or see someone else get for finding the block.

[Coolhwip]

I'd go along with that suggestion only if that bonus was restricted and prorated to people that donated to the pool. In other words, if anyone in the pool finds a block and they donate 0% no one gets anything extra.

[jjiimm_64]

I'd go along with that suggestion only if that bonus was restricted and prorated to people that donated to the pool. In other words, if anyone in the pool finds a block and they donate 0% no one gets anything extra.

or even prorate the reward depending on your donation

5% donation    1 btc
2.5%              .5 btc
1%                 .1


edit:  full disclosure i've been donating 5% since E ordered the workers

[Eri]

Been thinking on the pool hopper problem and came up with a few thoughts.

Why not just award shares to miners that mined for more than 50% of the block? During short blocks they don't hop away anyway, so there is no bad effect there. For slightly longer rounds, they are there for the majority of the round, so they have 'earned' their reward. The real problem is the longer rounds where they mine for 10 to 15 minutes and then leave. By the time an hour long block finishes, they are long gone. BUT, if you require a 50%+ participation in the block then it wouldn't matter. Their shares would simply be forfeit to those that stayed and mined the entire block, essentially they did free work for the pool.

This wouldn't even need to be calculated for every block, just those to run longer than average hopping time (20 min?). Also no need to play with delayed stats or other masking. Like they say in the lottery: You have to be in it to win it. Or in our case: You have to stay to get the pay 

on the surface i like this idea, but I'm not sure if it would really work. one problem i see with it that could be solved is, if you don't mine 24/7 then when you show up and just happen to be late for a round you would lose the work you did. the other half of this problem is when you leave, leaving because your turning off your PC, if less then 50% of the round would lose you some shares. the first half of the problem could be solved by looking at the past rounds. if you havn't been in them at all then it is highly likely you are not hopping and should get the shares from that round. the other half of the problem, if you have a high % of time in the recent rounds you have participated in then you would be allowed to keep the shares. ie, i have been in 10 rounds, all near 100% except 1 round, the likelihood that i am a hopper is extremely low. whether this would truly work i don't know, but it sounds good to me. anyone have any opinions on whether this would work or could work?

[eleuthria]

In the end, a stat delay is what we're going with.  Proportional is the most FAIR distribution - Every valid share is worth the same as every other in the round.



One of the things I did when trying to find out why the load balancer was crashing at long polls was remove the 'hub mode' feature from our bitcoind in case it was trying to spam too many p2p connections with other nodes.  I re-deployed JoelKatz's bitcoind "hub-mode patch" this evening after our invalid.  The two invalids in the last 24 hours were real invalids (the previous 4 from earlier last week were bugged bitcoind/load balancer crashing related).  The new invalids were simply other pools producing a block very close to our own, and the block chain favoring the other block.  Hub mode essentially makes bitcoind aggressively connect to other nodes to maintain a certain number of peers.

With hub mode re-enabled, we should now spread our blocks out among the other nodes on the bitcoin network significantly faster, and we will get the new blocks faster as well to reduce the odds of an invalid being produced.  After a few hours, it has been running strong and not causing any unusual long poll performance issues.

[zimpixa]

huhu I have found block... After 18.26 paid out and as backup pool

[BookLover]

Hey eleuthria, when you first installed the "super-server" my stale share rate went from ~2.5% to ~1% , but during the last few days my stale share rate has consistently been ~10% .  Do you have any ideas what could have happened to cause this?  I was not at home when it first started so I don't believe it was caused by a change I made, but I am open to any suggestions because I don't want to leave your pool.

P.S. Are you still planning on implementing difficulty two shares? I was really looking forward to those before the DDOS happened.

P.P.S I'm running poclbm through guiminer on a windows7 system.

Thanks for every thing eleuthria!

[sirky]

Hey eleuthria, when you first installed the "super-server" my stale share rate went from ~2.5% to ~1% , but during the last few days my stale share rate has consistently been ~10% .  Do you have any ideas what could have happened to cause this?  I was not at home when it first started so I don't believe it was caused by a change I made, but I am open to any suggestions because I don't want to leave your pool.

P.S. Are you still planning on implementing difficulty two shares? I was really looking forward to those before the DDOS happened.

P.P.S I'm running poclbm through guiminer on a windows7 system.

Thanks for every thing eleuthria!

I believe that he did implement difficulty 2 shares quite a while ago.

Have you tried stopping and restarting your miners? Or getting the newest version of guiminer?

[BookLover]

Really, I thought eleuthria said when he implemented difficulty two shares that each share show up as two on the site and the site is still showing odd numbers of shares. 
Yes I've restarted my miners.  I use a combination of a .bat file and task scheduler to restart my miners every half hour. 
No I haven't updated guiminer recently but this version had been working just fine.

[Xephan]

Hey eleuthria, when you first installed the "super-server" my stale share rate went from ~2.5% to ~1% , but during the last few days my stale share rate has consistently been ~10% .  Do you have any ideas what could have happened to cause this?  I was not at home when it first started so I don't believe it was caused by a change I made, but I am open to any suggestions because I don't want to leave your pool.

Could it be just pure bad luck? I was at around 0.4% for the first couple of days, then in the last two days, I'm pretty much at the 0.1% range with like only about 10 new stales for 10K+ completed shares.

[sirky]

Really, I thought eleuthria said when he implemented difficulty two shares that each share show up as two on the site and the site is still showing odd numbers of shares. 
Yes I've restarted my miners.  I use a combination of a .bat file and task scheduler to restart my miners every half hour. 
No I haven't updated guiminer recently but this version had been working just fine.

I would upgrade guiminer for no other reason than the newer versions of poclbm are significantly faster than they used to be (depending on how old your version is).

[hugolp]

In the end, a stat delay is what we're going with.

+1

EDIT: Btw, I dont know if Im just having bad memory, but it feels like lately we are having more variance. 2'2 TH/s we should be around 45 minutes each block on average, but we are getting several very long blocks (4+ hours) and then several very very short blocks (less than 10 minutes). I dont remember so much variance before. Probability is a bitch I guess.

[jjiimm_64]

Hey eleuthria, when you first installed the "super-server" my stale share rate went from ~2.5% to ~1% , but during the last few days my stale share rate has consistently been ~10% .  Do you have any ideas what could have happened to cause this?  I was not at home when it first started so I don't believe it was caused by a change I made, but I am open to any suggestions because I don't want to leave your pool.

P.S. Are you still planning on implementing difficulty two shares? I was really looking forward to those before the DDOS happened.

P.P.S I'm running poclbm through guiminer on a windows7 system.

Thanks for every thing eleuthria!

OK, i give up.  what is   "difficulty two shares"

[pdawg]

When do idle warnings come back?

[PcChip]

OK, i give up.  what is   "difficulty two shares"

Difficulty 2 shares mean your miner submits half the shares, but gets double the credit.  It basically cuts the network overhead/bandwidth in half and is much easier on the server (and will probably save on the bandwidth bill)

He almost implemented it a while back, and then after changing something in his system he realized it was no longer needed



Even though it's not needed anymore, I'm all for it if it improves effeciency and helps out on the server load and bandwidth bill!

[flower1024]

does this work with all miners?
i think i heard that some versions of diablo miner only calculates difficulty 1 shares - regardless what their getwork gave them

[sirky]

Hey eleuthria, when you first installed the "super-server" my stale share rate went from ~2.5% to ~1% , but during the last few days my stale share rate has consistently been ~10% .  Do you have any ideas what could have happened to cause this?  I was not at home when it first started so I don't believe it was caused by a change I made, but I am open to any suggestions because I don't want to leave your pool.

P.S. Are you still planning on implementing difficulty two shares? I was really looking forward to those before the DDOS happened.

P.P.S I'm running poclbm through guiminer on a windows7 system.

Thanks for every thing eleuthria!

OK, i give up.  what is   "difficulty two shares"

Basically instead of solving bitcoin difficulty 1.5 million, which is what we are actually trying to do, a share is when you solve a hash with difficulty 2.

Since we are getting double credit for each share, we should in theory find the block after 1.5 million shares are found (or 750,000 hashes of diff 2 are done).

That is how I understand it anyway. Feel free to correct me!