[CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers

[MoreBloodWine]

Also, I'm no so sure that acts as a minimum in the dragon settings and here's why...

Difficulty Sel : 512 --Current difficulty:512

It's like whatever you set is what it's told to always run at  

I'm not sure if newer dragon miners have fixed it, but I know all the early ones were a hard setting.  If the pool changed the difficulty, the miner would ignore it.  Many early users were complaining about this because dragon miners on every pool were showing only a fraction of the speed they should.  This was because the pools were only crediting them for  diff 2-32 (depending on the pool default), but the miner was only sending 1024+.

So chances are I have three of the buggy ones and can lose my shirt on em lol

Unless firmware update would fix everything. Not even sure how to do that safely or know if its needed.

Setting the diff to 1024 on both ends will guarantee the problem doesn't happen, I changed it on the miners end after your initial post.  512 is unlikely to cause a problem, other than the one I mentioned where a burst of luck could bump you to 1024, at which point 50% of your submissions get tossed under 'Unknown' rejects.  You would still get full credit for your mining though (you'd be submitting twice as many shares since you're set to 512, and roughly half would meet the 1024, getting credited for 2x512, while the other half would be rejected for not meeting 1024).So

So 1024 in the miner and on worker page of the pool guarantees no issues outside of a problem with the pool or the miner. That said, am I correct with the worker setting of 128 for my Prospector200 machine since the next jump up is 256 for 256Gh + ?

[1713571787]

1713571787

[1713571787]

1713571787

[1713571787]

1713571787

[1713571787]

1713571787

[eleuthria]

So 1024 in the miner and on worker page of the pool guarantees no issues outside of a problem with the pool or the miner. That said, am I correct with the worker setting of 128 for my Prospector200 machine since the next jump up is 256 for 256Gh + ?

Yes, 1024 for a dragon is the recommended setting, and should guarantee proper results while mining without any weird stats popping up.  I'm not familiar with the prospector 200, but if it's under 250 GH/s, then 128 is the recommended setting, yes.

However, as far as I'm aware, the only ASIC where the setting *can* cause a problem is the Dragon Miners.  Anything else is just a recommendation, it should have no material effects on other hardware.

[MoreBloodWine]

So 1024 in the miner and on worker page of the pool guarantees no issues outside of a problem with the pool or the miner. That said, am I correct with the worker setting of 128 for my Prospector200 machine since the next jump up is 256 for 256Gh + ?

Yes, 1024 for a dragon is the recommended setting, and should guarantee proper results while mining without any weird stats popping up.  I'm not familiar with the prospector 200, but if it's under 250 GH/s, then 128 is the recommended setting, yes.

However, as far as I'm aware, the only ASIC where the setting *can* cause a problem is the Dragon Miners.  Anything else is just a recommendation, it should have no material effects on other hardware.

Good to know, I also have an rPi for fun with 17 BE's and 3 U2's giving 10-12Gh/s... I keep the worker setting for that with a minimum of 2 since the hash can vary based on what I add or remove.

So right now on that we have a worker min of 2, this for speed (10.40/11.58/10.23Gh/s) and what is apparently a working diff of 4 if thats whats after the xx/

[2014-07-03 23:27:30] Accepted 2835a7f0 AMU 0  pool 0 Diff 6/4
 [2014-07-03 23:27:31] Accepted 0ee403d8 BES 4  pool 0 Diff 17/4
 [2014-07-03 23:27:34] Accepted 3915a821 BES 3  pool 0 Diff 4/4
 [2014-07-03 23:27:35] Accepted 123b9a37 BES 1  pool 0 Diff 14/4
 [2014-07-03 23:27:37] Accepted 308bd6a6 BES 3  pool 0 Diff 5/4
 [2014-07-03 23:27:42] Accepted 0944166a BES 3  pool 0 Diff 27/4
 [2014-07-03 23:27:42] Accepted 0a3cf7b5 BES11  pool 0 Diff 25/4
 [2014-07-03 23:27:47] Accepted 341026ea AMU 1  pool 0 Diff 4/4
 [2014-07-03 23:27:48] Accepted 1957cc12 AMU 1  pool 0 Diff 10/4
 [2014-07-03 23:27:50] Accepted 197f608c BES 7  pool 0 Diff 10/4


Edit: visionman-btc.com/pages/getting-started-prospector-200-start-up-guide-quick-start-instructions

[psahx]

... With only about 12 blocks/day expected, it doesn't take much to swing those numbers anymore. ...

I am just curious, shouldn't pool adjust round length, based on how many blocks do we expect to find per 24H? I mean, if we expect 12 blocks a day, shouldn't the rounds be 2 hour long?

If we get 12 blocks a day, distributed evenly in the 24 hour period, we will have to place them every 2 hours to fit the 24 hour frame. In this conditions, the shifts will close with 5-6 blocks, thus giving us about 60% of the real luck.

Please correct me, as I do not believe I may be right

[MoreBloodWine]

... With only about 12 blocks/day expected, it doesn't take much to swing those numbers anymore. ...

I am just curious, shouldn't pool adjust round length, based on how many blocks do we expect to find per 24H? I mean, if we expect 12 blocks a day, shouldn't the rounds be 2 hour long?

If we get 12 blocks a day, distributed evenly in the 24 hour period, we will have to place them every 2 hours to fit the 24 hour frame. In this conditions, the shifts will close with 5-6 blocks, thus giving us about 60% of the real luck.

Please correct me, as I do not believe I may be right

This should keep from not earning on a round (no lost shares) with bad luck I think.

[MoreBloodWine]

Damn orphans... just had a 4:xxpm block that was waiting for conf and is now gone ;-(

[psahx]

... With only about 12 blocks/day expected, it doesn't take much to swing those numbers anymore. ...

I am just curious, shouldn't pool adjust round length, based on how many blocks do we expect to find per 24H? I mean, if we expect 12 blocks a day, shouldn't the rounds be 2 hour long?

If we get 12 blocks a day, distributed evenly in the 24 hour period, we will have to place them every 2 hours to fit the 24 hour frame. In this conditions, the shifts will close with 5-6 blocks, thus giving us about 60% of the real luck.

Please correct me, as I do not believe I may be right

Anyone?

[eleuthria]

... With only about 12 blocks/day expected, it doesn't take much to swing those numbers anymore. ...

I am just curious, shouldn't pool adjust round length, based on how many blocks do we expect to find per 24H? I mean, if we expect 12 blocks a day, shouldn't the rounds be 2 hour long?

If we get 12 blocks a day, distributed evenly in the 24 hour period, we will have to place them every 2 hours to fit the 24 hour frame. In this conditions, the shifts will close with 5-6 blocks, thus giving us about 60% of the real luck.

Please correct me, as I do not believe I may be right

Anyone?

The round length was always targetting 1 block per shift minimum, with a 1hour shift length maximum.  This is no longer possible since the pool is under 10% of the network.  The options are longer shifts, which means more blocks per shift but they last a LOT longer, or keeping shifts the same, which means fewer blocks per shift.

The earnings for the user does not change in either situation.  More shifts with fewer blocks per shift or fewer shifts with more blocks per shift.  Pick your poison.  I have no plans to increase shift length beyond what it already is because they already last too long in my opinion.  It already takes about 16 hours for a share submitted to fully mature (stop getting paid).

[psahx]

The round length was always targetting 1 block per shift minimum, with a 1hour shift length maximum.  This is no longer possible since the pool is under 10% of the network.  The options are longer shifts, which means more blocks per shift but they last a LOT longer, or keeping shifts the same, which means fewer blocks per shift.

The earnings for the user does not change in either situation.  More shifts with fewer blocks per shift or fewer shifts with more blocks per shift.  Pick your poison.  I have no plans to increase shift length beyond what it already is because they already last too long in my opinion.  It already takes about 16 hours for a share submitted to fully mature (stop getting paid).

Thanks for the lesson Does this affect the pool luck though?

[MoreBloodWine]

Lucks lookin a bit better today, actually made what I was supposed to with my hash plus a tad.

Anyway, question for ya Michael...

On the main page where it shows Recent PPLNS Shift Statistics & Recent Block Rewards. Right now it's limited to showing 11 items, do you think we could maybe expand that 4 more so it shows 15 please ?

[eleuthria]

Lucks lookin a bit better today, actually made what I was supposed to with my hash plus a tad.

Anyway, question for ya Michael...

On the main page where it shows Recent PPLNS Shift Statistics & Recent Block Rewards. Right now it's limited to showing 11 items, do you think we could maybe expand that 4 more so it shows 15 please ?

No plans on changing that/making it selectable currently.  It's at 11 items because it's showing you the currently open shifts and the current (not yet completed) shift progress.  The recent blocks uses 11 just so they're symmetrical since it would look odd if one was longer than the other (empty space on one side or the other).

The point of the dashboard is quick live stats, not historical data.

[MoreBloodWine]

Lucks lookin a bit better today, actually made what I was supposed to with my hash plus a tad.

Anyway, question for ya Michael...

On the main page where it shows Recent PPLNS Shift Statistics & Recent Block Rewards. Right now it's limited to showing 11 items, do you think we could maybe expand that 4 more so it shows 15 please ?

No plans on changing that/making it selectable currently.  It's at 11 items because it's showing you the currently open shifts and the current (not yet completed) shift progress.  The recent blocks uses 11 just so they're symmetrical since it would look odd if one was longer than the other (empty space on one side or the other).

The point of the dashboard is quick live stats, not historical data.

Figured I'd ask, assuming we find <= 15 blocks a day that "quick glance" would show us the last 15 block found for the last 24hrs with the associated reward(s).

https://www.btcguild.com/index.php?page=pplns

or

https://www.btcguild.com/index.php?page=pool_stats

Doesnt really give that info... I mean the first link I guess is the closest thing but you'd have to do a lot o math on which shifts belong to which block etc to get accurate figures.

Edit: Basically I want to be able to add this up on my own rather easy.

24 Hour Earnings 0.08094381

Which allowing for 15 would do, assuming we find <= 15 blocks a day which we usually seem to find less of with today being a good day.

[MoreBloodWine]

Also, at what intervals (every half hr, every hr on the hr etc) does the 24 Hour Earnings figure update ?

[hurricandave]

Also, at what intervals (every half hr, every hr on the hr etc) does the 24 Hour Earnings figure update ?

The latest 24 hrs. of closed shifts, that doesn't include the latest(most recent) closed shift because it sometimes can still gain share value from blocks 'waiting on conformation' when the latest open shift ended.

[MoreBloodWine]

Also, at what intervals (every half hr, every hr on the hr etc) does the 24 Hour Earnings figure update ?

The latest 24 hrs. of closed shifts, that doesn't include the latest(most recent) closed shift because it sometimes can still gain share value from blocks 'waiting on conformation' when the latest open shift ended.

So whenever a shift is closed that figure updates ?

[hurricandave]

Also, at what intervals (every half hr, every hr on the hr etc) does the 24 Hour Earnings figure update ?

The latest 24 hrs. of closed shifts, that doesn't include the latest(most recent) closed shift because it sometimes can still gain share value from blocks 'waiting on conformation' when the latest open shift ended.

So whenever a shift is closed that figure updates ?

Yes.

[MoreBloodWine]

Also, at what intervals (every half hr, every hr on the hr etc) does the 24 Hour Earnings figure update ?

The latest 24 hrs. of closed shifts, that doesn't include the latest(most recent) closed shift because it sometimes can still gain share value from blocks 'waiting on conformation' when the latest open shift ended.

So whenever a shift is closed that figure updates ?

Yes.

I know I didn't really have to ask that, but Ty for answering

Right now it seems like shifts last around 72/73 minutes.

[guytechie]

Not having PPS makes it hard to determine how many blocks per shift is normal now.  Can you add something that says something like 10 blocks for 100% luck?

And what are the blocks per shift that is 100%?  It looks much lower than 8 now.

[MoreBloodWine]

Not having PPS makes it hard to determine how many blocks per shift is normal now.  Can you add something that says something like 10 blocks for 100% luck?

And what are the blocks per shift that is 100%?  It looks much lower than 8 now.

Speaking of PPS, did you ever see this Michael ?

I'm not sure merged mining coins is the answer. If BTC Guild could offer a low cost PPS variant (as suggested in a thread by Meni Rosenfeld) in conjunction with some other pools, I think GHash.IO would be in trouble.

[eleuthria]

Not having PPS makes it hard to determine how many blocks per shift is normal now.  Can you add something that says something like 10 blocks for 100% luck?

And what are the blocks per shift that is 100%?  It looks much lower than 8 now.

You can calculate it yourself once each difficulty.  Shifts are currently 11b shares long (approximately).  So 10 shifts lasts for ~110b shares.   Divide that by network difficulty to get the neutral luck blocks per shift. 110b / 16.b = 6.55 blocks would be perfect neutral luck.

Speaking of PPS, did you ever see this Michael ?

I'm not sure merged mining coins is the answer. If BTC Guild could offer a low cost PPS variant (as suggested in a thread by Meni Rosenfeld) in conjunction with some other pools, I think GHash.IO would be in trouble.

That proposed solution will never see the light of day.  The complexity of implementing is just too high and no pool operator with a brain is ever going to touch a PPS reward system again.