Topic: Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB - page 29. (Read 1061365 times)

I am sorry, but i must disagree...I am watching my stats months without change and paid shares was at 85% now they show 91%, so there is something wrong.

Lets do some math:

Current numbers:
Maximum reward: 115.78 BTC
Shelved shares "worth": 9.33 BTC
Paid: 106.45 BTC
Paid percent (aka "Shares Rewarded"): 106.45 / (115.78 / 100) = 91.94%

Old numbers (before halving):
Maximum reward: 125.11 BTC
Shelved shares "worth": 18.66 BTC
Paid: 106.45 BTC
Paid percent (aka "Shares Rewarded"): 106.45 / (125.11 / 100) = 85.09%


See? Difference in shelved shares "value" just changed percentage of "Shares Rewarded" because of "halving of shelved share value". I understand it (and it is correct) because its calculated based on "owed amount" and "paid amount" so mathematically its totally correct. I just want to point out that STATS PERCENTAGE changed and that confused me when I saw it first time, thats all...

Misiak

Shares are and have always been valued as a portion of the block subsidy that eventually rewards them (work_difficulty / network_difficulty).  (http://eligius.st/wiki/index.php/Capped_PPS_with_Recent_Backpay) As of the recent subsidy halving, the stats and stats estimates accurately reflect this since the subsidy of future potential blocks has changed.  The percent shares rewarded is no different, since it is represented as the sum of the rewarded value of all previous shares which have been paid/rewarded divided by the sum of the same plus the current estimated value of all shelved shares should they be rewarded now.  When a block is found and a share is to be rewarded/paid, it is rewarded/paid as ((work_difficulty / network_difficulty) * found_block's_subsidy) BTC.

The previous halving also left some ambiguity into how shares would be rewarded (check posts from 4 years ago for that drama), but there really is no statistically sane way to handle share rewards besides representing them as a portion of the block subsidy that rewards them, otherwise even on a law-of-large numbers statistical model it would be impossible for a pool to have a path for potential reward of all shelved shares.

All of that said, I wouldn't get too worked up about the current stats and reward system.  The upcoming changes will fundamentally alter virtually everything about how the pool works on both the back end and the front end.  Also keep in mind that shelved shares are fiat.  They have no real value unless a block rewards them.  They are not in any way shape or form owed by the pool as they are shares for which the pool has not yet actually mined blocks which could reward them.  There is and never has been any actual funds associated with shelved shares, by definition.

As for work difficulty issues, check back after I get the pool revisions online in a few weeks.

-wk

Hey wizkid,

I am not sure if someone said this already, but I have problem.

Just to describe it a little. Currently I have almost 15% of unpaid shares worth of approx 19 BTC (because they are "shelved shares") they all were mined when block was paying 25 BTC.

As of now when block pays half of that, stats shows BAD numbers, all my shares are counted as mined after halving and now stats show I got paid 91% (instead of true 85%) and "unpaid balance" now shows only 9 BTC. All my past stats has just been "halved" thats an big issue for me as 9 BTC is a lot.

I know there is little chance I will get that shelves shares paid, but I dont even like "stats halving". Please look at it.

Feel free to contact me via PM if you need more informations.

Btw I PMd you in the past as I wanted to use rented hashing power, but your pool dont meet nicehash criteria of minimal difficuilty, can you fix it? (Or please allow to set fixed difficuilty via password commands like other pools doo).

Thank you!

Good Day.

I am interested in joining Eligius. What is the average payout per TH's on this pool per day after the halving?

So long as the conditions (minimum payout, etc) are met, the reward is mined directly to miners.
[/quote]

Ok I have more noob questions , is that payment system automatic that when some earning line cross pool will send coins to that adress what miner using? And what is that 120 confirmation, after that pool get that reward and tx fees? I dont still 100% get that CPPSRB payment system. Let's think about situation that pool had a bad luck like last 10 blocks and then miners join the pool after that so is that new miner going to pay shares didnt get paid last blocks? And If pool have good luck so are miners getting paid more than usually or does pool save those extra for future that could pay when is not so good luck? Hopefully you understand my thoughts

I have been mining in Eligius last three blocks, I guess I came here with good luck
483.5%
183.0%
111.2%

EDIT:

Have been mining here since 11.7 (3.75days) and been part of mining power for 4 rewarded blocks.

273.4%
483.5%
183.0%
111.2% (part of that)

So average luck should be ~262%.
My stat page shows:
Estimated Total:    0.02675039 BTC   100.00%.

0.00824840 (calculated daily amount for 7ths with 100% luck)*3.75 (my time in eligius) = 0.0309BTC
So if that stat page is rigth for my earnings it is only 86% what it should be for 7ths with 100% for that period. Pool luck has been 262% average at this time and my actual hashrate in Eligius pool about 7.3ths. So  there was no benefit for good pool luck for me?

So long as the conditions (minimum payout, etc) are met, the reward is mined directly to miners.

Hi All,

I just join your pool with 8ths.

I have a question. When pool find the block, do that pay reward right away for miners?

NMC payouts are done every 1-3 months.  I believe he has to do them manually hence the irregular timing.

So there is no nmc payouts? or are they going somewhere else? as i have yet to see any or get a answer to that question
It does seem that this pool is strangely unlucky so i say thank you and take my leave from it. o/

btcaddress_workername

Can you allow us to assign unique ids to each worker? If I have many workers mining on the same address, I can't break down the stats by workers.

I got 4 x S5 antminers = 4.5 TH sitting on a shelf, but it will only consume around 2.2 kwatts. if ya want them, message me, you can have them if you can pay the shipping from Canada via post i think is the cheapest. If you only need to get rid of power, im sure if you mine to my address, i'll pay the shipping

@wizkid057
I have a Bitmine CCD 600GH/s, consumes ~600Watts at the wall.
What's your location?

@wizkid057

Thank you for the continued updates! Keep up the good work! Also, for certain aspects of the site that are not as core that you dont have time on feel free to ask the community for our talent, I bet many of us would write GUI, API's, other code or host servers for you for free.

This is unrelated, however, this does affect myself in where I point some of my miners. In regards to the options, I understand at the moment the only way to use them is to sign a message with the options we want using our miners.

This makes sense, however, I recently moved some of my miners to hashplex facility due to them having a cheaper source of energy. Since I do not have command line access, I cant specify options for these miners.

I could ask the operations staff to see if they could sign a message for me or ask them to create an interface that allows me to sign on their online interface. However, another way for people who do not have full access to there miners would be to be able to just update our options by specifying the same options parameters as the password in connecting to the pool and have it parsed there.

Just curious on your thoughts on this. Anyways, keep up the good work!

There is something that I am curious about.....  this isn't really a complaint because I know it always seems to catch up but really more of a curiosity.  Frequently I end up at the point where I am right now where my user stats pages shows:

Approximately 0.00000000 BTC remaining to enter payout queue. Maintaining your 3 hour hashrate average, this will take at least another a few seconds at current network difficulty of 209,453,158,595.38.

It's been showing this for at least the past 12 hours and I have previously seen that message for days straight....  my balance seems to increase throughout this but I don't actually enter the payout queue for some time.

As for the updates I am looking forward to them and can certainly appreciate the position your are in wizkid.....   I just want you to know that I am happy to support a pool that is run by someone who is "just like us" in a sense.... so, thanks! 

Shipped to US or elsewhere?
If it's in the US I have a BTC Garden AM V2 610, it's running now kicking out the big $0.85 a day but since I have free power for it it's better then nothing...

-Dave

Hi everyone,

I know I'm way behind on this refresh project, and it's disappointing.  After a very limited pre-alpha test of some of the new code........ I've ended up working on fully rewriting a lot of that code in an effort to make some aspects of the new system as good as they really should be.  I had reused a lot of things I used in Eligius's CPPSRB implementation with the new code, but it turns out that it's just not as efficient as it can be with the new changes.  The result of that, though, is more time in development.  I think these updates are well worth it, though, but I'm starting to worry it's going to end up just being a little too late to matter by the time I get everything actually up and running.    I don't think anyone is going to be disappointed once the new code is done and is up and running publicly... but I'm well aware of the declining user base.  While some miners have left the pool for now in search of better prospects, my hope is that they're keeping an eye on things here and will return once they see the new Eligius.  Time will tell I suppose.

I wish there were more hours in the day so I could keep up with my normal work and have plenty of time to work on Eligius.  If anyone sees Doc Brown send him my way, will yah?  

Coming along though!

-wk

Unrelated note:  Does anyone have any old miners sitting around collecting dust that they're looking to get rid of?  I'm trying to perhaps use more miners as part of my solar dump load for my off-grid setup, but it doesn't make sense to buy them new, or old hardware for the prices people are trying to sell them for on eBay and such since I'd only be running them for up to 5-10 hours per day and only on good weather days... at best ~25% of normal run-time on average. Basically anything more efficient than BFL era hardware would probably be worthwhile to setup.  I currently have all of my old hardware hooked up for this (about 4Th worth at about ~1.5W/Gh average), but it's not wasting enough power... I need something like 15kW more in waste loads during the peak of the day.  PM or email me if you have any suggestions!  Thanks!

Eligius and P2Pool are using generated coins to pay to miners. Because of that their first (coinbase) transaction is much bigger than from other pools (Ant and Slush) and if your miner can't handle it well, your actual hashrate is dropping even the miner shows it's OK.

I had somewhat of the same scenario playing out for a while on my Antminer S5 and it turned out to be related to my network connection.  I'm unable to plug my miner directly into a wired internet connection so I was using a wireless bridge....  I honestly don't know the details or the technical explanation as to why communications seemed to be fine on another device behind the same bridge and how the S5 saw completed submissions that didn't seem to be making it to eligius but when I replaced that bridge with one from another company things started working perfectly.  Perhaps it has something to do with the way your internet connection is routing to eligius vs other pools....  I unfortunately don't have any answers but maybe this will help point in the right direction.

Had an issue with one of the pool servers this morning and it had to be restarted.  Things should be back to normal shortly as load balancing recovers.  Apologies for the bit of short term instability.  I was busy mitigating a DDoS last night and hadn't caught on to the one server having some minor issues.  I'll be working on figuring out why this one machine was having issues in order to prevent it in the future.