Topic: [OLD] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 # - page 108. (Read 458518 times)

You're gonna have to update your miner, I think... Give MacMiner a try (https://bitcointalksearch.org/topic/the-official-macminer-thread-btcltc-cpugpufpgaasic-197110)

So i see I wish I understood mining a little better. Using diablo on a mac pro. This might be why I have so many issues. Most pools I get nowhere with. Guild....slush etc. Only one I have any joy with is eligius' getwork, 50btc and bitminter. Bitminter was a no-no after the endless DDOSing.

I just get error messages and nothing happening when I try to connect to others.

Sorry I realise this should be somewhere else....anyone wanna send me somewhere I can get some help?

No connection issues on this end that I can see. Thousands of workers connected.

Can't connect to GBT or Stratum. Getwork worked for me for the last three weeks and now I can't connect to that

stats are not updating for me.

Thank you *very much* for this very detailed explanation. Now I'm convinced you are right

Ironically, a couple of hours after your reply, I see some shelved shares taken to estimated during lucky phase i.e. early in the latest round, for the first time in >2 weeks. Looks like I was impatient (and unlucky, as you pointed out) after all indeed.

Donations are never needed but always appreciated, I guess. You can count on the 0.2 BTC donation as promised, I will post txid in a few days, hopefully from my shelved shares

Thanks again for the time taken responding to this, I appreciate it.

Thanks for the explanations, guys!

To put things in perspective, Eligius used about 30 TB of bandwidth in the first 30 days of using the new server with GBT not redirected to stratum.  Talking about around 100 megabit commit, which is, in general, prohibitively expensive. We had peaks to over 0.5 gigabit outbound during longpoll at peak times, which is ridiculous for something that should be pretty simple.

Since the recent changes we're down to under 1/3rd of previous bandwidth usage.  Still quite a few people using GBT by disabling stratum redirection in their miners, and more power to them.  I think GBT is definitely going to end up as the preferred protocol, but, in it's current bandwidth hungry state, it is pretty wasteful when every miner, big and small, uses it.

*cheers for GBT 2.0*

-wk

There are two reasons stratum has become the preferred protocol:

• GBT uses a fixed amount of bandwidth regardless of hashrate, and was designed for ASICs, not CPUs. For ASICs, fixed bandwidth is a pretty good thing: much less compared to getwork, but for CPUs, it's absurdly high! Unfortunately, the stupid botnets blindly adopted GBT and were creating major bandwidth issues for Eligius.
• GBT is not yet fully implemented. The server is currently expected to send every client a full set of transactions to put in blocks. This adds to the bandwidth needed for it. A full GBT implementation gets this transaction data from your local bitcoind, not the pool. I am working on getting full GBT support into Eloipool (or a rewrite) and BFGMiner, but it takes time to get everything just right.

I expect that when GBT is finished, it can once again become the preferred protocol.

First, let me point out that no donations are needed for this.  I'd much rather you understand the system regardless.

I'm not sure what you mean by "strobes", but I will attempt to explain your personal situation in as much detail as possible.

Lets first take a look at a historical graph of your mining hashrate and balance changes:



And now lets take a closer look at the time after you stopped mining with the pool:



Before I go any further, let me point out that based on these graphs, approximately 0.2 BTC in shelved shares were in fact rewarded to you in the period between the time you stopped mining with us and now.

I believe you somewhat understand the spikes in the estimated balance are the shelved shares that could be paid at the start of a round (lucky) and tapering off as a) no new shares from active mining are added, and b) less of your shelved shares are in the top 25 BTC of the share log as they are pushed further down by active miners' shares.  This is exactly what is happening here in your graph.

So, to set the stage, your most recent shelved share was mined on 2013-06-21.  Then, after that, 0.2 BTC worth were paid/rewarded, making it so your most recent shelved share is even older than that since your newest ones were paid first.  I'll spare you the math in figuring it out (can be estimate with the graphs alone), but as of today your newest shelved share is from approximately 2013-06-17.

So, in order for your shelved shares to be in the top 25 BTC of the share log, and thus have an estimated payout (spike in the estimate balance graph) possible that means that every share from right this moment all the way back to 2013-06-17 would need to be either already paid or total less than 25 BTC.  Consider that is nearly three weeks of time, and there have been many unlucky rounds in that time frame, neither is likely.

It looks like, according to your graph, your shelved shares stopped being in the top of the share log around 2013-06-25.  Specifically, the last block that caused your estimated balance graph to change was 243,363 (compare the times). Lets take a look at the block history from that time frame forward:



Here is the meat of this whole exercise: Notice that block 243,363 was unlucky, 44,469,230 shares at difficulty 19,339,258.  That means this block alone put 25,129,972 newer shares than yours on top of the share log as new shelved.  When block 243,429 was found, the top of the share log (25 BTC, or approximately 19,339,258 shares) was taken as estimated payouts for this new round.  But wait, 25,129,972 in shelved shares were just added on top of your shelved.  25,129,972 > 19,339,258, thus your shelved shares are no longer in the top 25 BTC of the share log.  Looking further up the block list, block 243,429 was also unlucky, adding approximately 23,342,644 more shares on top of your shelved.  So, just the next two blocks alone have buried your shelved shares under over 48 million active miner shares.  Take into consideration that there was a decent run of unlucky blocks to follow, and your shelved shares are so far under currently active miners' shares that there is no way they would be near the top of the share log any time soon.

So, the system is working perfectly, you just stopped mining at a particularly unlucky time, not that you had any way of knowing that.

CPPSRB variance averages out, generally over approximately 60+ days, to level off in the upper 90s% PPS, even 100% PPS at times. (See variance graph on the stats page)  You had only mined with Eligius for about 4 weeks, which, taking into account the bad luck rounds in that time and to follow, is definitely not enough time for variance to average out nicely to a high % PPS.  Even so, according to your stats page you were paid over 90% PPS on average for your work.  This definitely would have been higher had you continued to mine with us, or had the pool been more lucky.

In any case, the system is working perfectly.  Under CPPSRB active miners always have an advantage, since they will always have shares in the top 25 BTC of the share log, and thus are always earning.  When you stop mining you are purely at the mercy of the luck that follows, which in your case was not the best.

I hope this helps you understand the setup better and the details of your particular situation.

-wk

Fair enough. I've been out of contact with bitcoin for a few months, so I wasn't keeping up on all that. I'll just take out those connections as my backups and I'll get a third backup pool for just in case.

I know you weren't born yesterday, because I've seen you around.  That having been said (since I don't think I've seen you trolling):
1) LukeJr doesn't run this pool anymore, Wizkid does
2)

Weird, I would have thought LukeJR's pool would use his protocol(especially when using his miner software)...

The GBT/GW server "suggests" your miner to switch to Stratum server, and your miner accepts it.
You can use --fix-protocol for cgminer or --no-stratum for bfgminer to turn off this feature.

What am I doing wrong? the 3 are connecting by stratum when one should be GBT, one stratum and the other GW.

It is my understanding that leaking of shares might happen when something is going on with the pool which causes your miners to switch over to your backup pool. This flip flop between pools causes a loss in shares as during the switch over a percentage are lost. In this case, via IRC, I read that Eligius was under a DDoS and WizKid057 was doing a fine job combating it. Needless to say though, you would be mining fine for a while, it would hiccup, your miner would switch to a backup, then after a minute or so switch back. My various rigs have stopped doing that since late last night, so I am assuming things were handled, it's been smooth sailing for many hours. (And we've had a nice little slice of luck!) 

Can someone explain what "leaking shares" means? I've been mining for a few months now but there's still quite a bit of the nitty-gritty details I don't fully understand.

Having some nice luck lately!

yeah cgminer has been leaking shares even with --failover-only. stats are reporting that I'm running about ~10% slower than I was for the previous 24 hours.

Something's still not right. I'm getting a whole bunch of these: