Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB

[irrational]

this pool doesn't seem to payout the way it explains itself..  been watching it like a hawk the past week and seems payouts has a mind of its own

a detail on the mechanics (not the theory) would be useful since it doesn't seem to behave in practice as it is intended... basically it seems all accumulated work gets held ransom regardless of current block luck cycles which in theory should be paying out portions past your pay threshold but in practice it just sits there and says you are going further and further behind as if all your current work is old work that has to wait for super luck to include you .. and that doesn't even seem to trigger it either

it is broken

That is how it's designed to operate. Each share will never receive 100% of it's value paid, so therefore each share will forever sit around in some partially unpaid state. It's a highly convoluted way of charging operating fees without using the word "fee".

Not that fees are bad, they're needed to cover all sorts of things - especially in (effectively) a PPS pool... just misleading the way it's currently advertised.

[1714315126]

1714315126

[1714315126]

1714315126

[1714315126]

1714315126

[1714315126]

1714315126

[1714315126]

1714315126

[wizkid057]

this pool doesn't seem to payout the way it explains itself..  been watching it like a hawk the past week and seems payouts has a mind of its own

a detail on the mechanics (not the theory) would be useful since it doesn't seem to behave in practice as it is intended... basically it seems all accumulated work gets held ransom regardless of current block luck cycles which in theory should be paying out portions past your pay threshold but in practice it just sits there and says you are going further and further behind as if all your current work is old work that has to wait for super luck to include you .. and that doesn't even seem to trigger it either

it is broken

Just your understanding of how things work is broken.  The pool is operating as it should.

What some people do not understand is that the payout queue and the rewards from CPPSRB are completely independent things. The payout queue is a way to get actual coins to miners in transactions on the network.  The CPPSRB rewards are the way miner's balances at the pool are increased.

You never are further behind or anything.  The payout queue is generally actual coins that will be paid to your address.  The rewards are separate from that.

[georgem]

this pool doesn't seem to payout the way it explains itself..  been watching it like a hawk the past week and seems payouts has a mind of its own

a detail on the mechanics (not the theory) would be useful since it doesn't seem to behave in practice as it is intended... basically it seems all accumulated work gets held ransom regardless of current block luck cycles which in theory should be paying out portions past your pay threshold but in practice it just sits there and says you are going further and further behind as if all your current work is old work that has to wait for super luck to include you .. and that doesn't even seem to trigger it either

it is broken

Just your understanding of how things work is broken.  The pool is operating as it should.

What some people do not understand is that the payout queue and the rewards from CPPSRB are completely independent things. The payout queue is a way to get actual coins to miners in transactions on the network.  The CPPSRB rewards are the way miner's balances at the pool are increased.

You never are further behind or anything.  The payout queue is generally actual coins that will be paid to your address.  The rewards are separate from that.

For me as a noob this sounds like chinese.

So when it says 13 block delay here at my address http://eligius.st/~wizkid057/newstats/userstats.php/16bWt62xq5rmQuGscq7L7GuZfYmZkkvN5x

how can I get an estimated value about how long it will take before the BTC arrives in my wallet?

Thank you for your service to mother bitcoin.

[pawel7777]

Is the merged mining still working?
Seems I haven't got any Namecoin transfers in a long time.
Is it just me?

Nevermind. Just noticed that the answer is right above.

[davebodger]

this pool doesn't seem to payout the way it explains itself..  been watching it like a hawk the past week and seems payouts has a mind of its own

a detail on the mechanics (not the theory) would be useful since it doesn't seem to behave in practice as it is intended... basically it seems all accumulated work gets held ransom regardless of current block luck cycles which in theory should be paying out portions past your pay threshold but in practice it just sits there and says you are going further and further behind as if all your current work is old work that has to wait for super luck to include you .. and that doesn't even seem to trigger it either

it is broken

Just your understanding of how things work is broken.  The pool is operating as it should.

What some people do not understand is that the payout queue and the rewards from CPPSRB are completely independent things. The payout queue is a way to get actual coins to miners in transactions on the network.  The CPPSRB rewards are the way miner's balances at the pool are increased.

You never are further behind or anything.  The payout queue is generally actual coins that will be paid to your address.  The rewards are separate from that.

For me as a noob this sounds like chinese.

So when it says 13 block delay here at my address http://eligius.st/~wizkid057/newstats/userstats.php/16bWt62xq5rmQuGscq7L7GuZfYmZkkvN5x

how can I get an estimated value about how long it will take before the BTC arrives in my wallet?

Thank you for your service to mother bitcoin.

The way I work it out (very roughly) is that Eligius generally solves 20+ blocks per day, so 13 will likely take around half a day.
The other way of looking at it is to follow the link to the payment queue, find your address therein, check the "Age" column.
Say, for example, your Age is 1 day 22 hours.
Then look at the top of the queue and at the bottom of the first block. Don't look at the actual top of the first block as that may worry you.
There should be a lot of entries there with a similar age (say for example 2 days 10 hours).
Subtract your Age from that Age and the difference (12 hours) is (roughly) how long it will take you to work your way to the top of the queue.
The actual real amount of time is how long the pool actually takes to solve those 13 blocks that will get you to the top, plus the variance of any more people joining the queue ahead of you as their thresholds are passed and they turn out to have been waiting longer than you for a payout.

Hope that helps, but now I write it down it does sound a little tricky and it took me a while to figure it out myself. YMMV.

[un_ordinateur]

this pool doesn't seem to payout the way it explains itself..  been watching it like a hawk the past week and seems payouts has a mind of its own

a detail on the mechanics (not the theory) would be useful since it doesn't seem to behave in practice as it is intended... basically it seems all accumulated work gets held ransom regardless of current block luck cycles which in theory should be paying out portions past your pay threshold but in practice it just sits there and says you are going further and further behind as if all your current work is old work that has to wait for super luck to include you .. and that doesn't even seem to trigger it either

it is broken

That is how it's designed to operate. Each share will never receive 100% of it's value paid, so therefore each share will forever sit around in some partially unpaid state. It's a highly convoluted way of charging operating fees without using the word "fee".

Not that fees are bad, they're needed to cover all sorts of things - especially in (effectively) a PPS pool... just misleading the way it's currently advertised.

Ok...

I'm gonna try to explain this.

Miners submit shares. They are converted to an IOU value, which is equivalent to the fair PPS value. However, they are not paid at that time, they are stored in a share log, last-in, first-out.

When a block is found, the pool goes back into the share log, and "pays" as much shares as it can. If the block was unlucky, some of the earliest shares submitted for that block will be unpaid. If the pool was lucky, it will go over, and pay some shares that were unpaid in an earlier unlucky block.

But those shares are not immediately payed, for various reasons. Instead, they go in a payout queue, and when a miner will have accumulated enough to-be-payed shares, they are payed out.

Notice that the pool has not kept any money. It distributes all the money it finds, not more, not less. So it is NOT a fee.

That is CPPSRB. Now the pool has ANOTHER special thing, which is HOW it pays the reward out. The Eligius operators have devised a novel way of paying out, which is to pay out directly from the generation transactions. It has the advantage that the pool never handles money directly, so there is no "hot wallet" an hacker could compromise ans steal.

It imposes some restrictions on how payments are made though. One is that you cannot pay somebody "anytime", only when you find a block. Another is that the coins thus generated will not be able to be spent for 120 blocks instead of 6 as usual.

So, when a user is ready to be payed out (has crossed it's treshold), it is put in the queue, the ones who recieved their latest payment the furthest first, and when a block is found, the first users in the queue will be payed until the reward is entirely consumed. (so a given miner may be pushed back in the queue if another miner crosses it's treshold and has not been payed for longer than him)

It sometimes happen the pool cannot determine who should get payed in the next block. Instead of throwing it away, it instead mines to an offline address, from which the pool operator will do a manual payout from times to times. In essence, it reverts to a "regular" pool, where you have to trust the operator to not run away with the money, because they control it. However, it is still more secure, because the wallet is not online.

Under normal behavior, the payout queue should always be short; a few blocks max. However, when the pool is in failsafe mode, since it finds rewards, but does not pay them out, the queue grows. However, a manual payment is always done every week or so to sort things out.

I hope this clears things!

[georgem]

The way I work it out (very roughly) is that Eligius generally solves 20+ blocks per day, so 13 will likely take around half a day.
The other way of looking at it is to follow the link to the payment queue, find your address therein, check the "Age" column.
Say, for example, your Age is 1 day 22 hours.
Then look at the top of the queue and at the bottom of the first block. Don't look at the actual top of the first block as that may worry you.
There should be a lot of entries there with a similar age (say for example 2 days 10 hours).
Subtract your Age from that Age and the difference (12 hours) is (roughly) how long it will take you to work your way to the top of the queue.
The actual real amount of time is how long the pool actually takes to solve those 13 blocks that will get you to the top, plus the variance of any more people joining the queue ahead of you as their thresholds are passed and they turn out to have been waiting longer than you for a payout.

Hope that helps, but now I write it down it does sound a little tricky and it took me a while to figure it out myself. YMMV.

Thanks, I will take your advice and try to get a feeling about how I am supposed to approximate those values.

[wizkid057]

I've actually gone through and fixed many of the issues that caused failsafes with CPPSRB.  Since these patches there hasn't been a single CPPSRB-caused failsafe. (Last was 2014-03-28 20:40:04 UTC)

So, after I shutdown the "KnC port" server that can't do normal payouts and only pays the offline wallet (because older KnC firmwares are broken), and fix a couple other minor things, I will do a manual payout again.  Then the queue should stay relatively small for long periods of time and I will try to keep it under 10 blocks.

So, KnC folks, make sure you update you're firmware and start using the normal ports.

-wk

[jamesg]

I've actually gone through and fixed many of the issues that caused failsafes with CPPSRB.  Since these patches there hasn't been a single CPPSRB-caused failsafe. (Last was 2014-03-28 20:40:04 UTC)

So, after I shutdown the "KnC port" server that can't do normal payouts and only pays the offline wallet (because older KnC firmwares are broken), and fix a couple other minor things, I will do a manual payout again.  Then the queue should stay relatively small for long periods of time and I will try to keep it under 10 blocks.

So, KnC folks, make sure you update you're firmware and start using the normal ports.

-wk

Awesome work wizkid. Just a small thanks for all of the hard work.

https://blockchain.info/tx/abb641b1c23447050c7582bddeb92e3e6882f5365ec69656ac67d2d4a066b571

[DPoS]

I've actually gone through and fixed many of the issues that caused failsafes with CPPSRB.  Since these patches there hasn't been a single CPPSRB-caused failsafe. (Last was 2014-03-28 20:40:04 UTC)

So, after I shutdown the "KnC port" server that can't do normal payouts and only pays the offline wallet (because older KnC firmwares are broken), and fix a couple other minor things, I will do a manual payout again.  Then the queue should stay relatively small for long periods of time and I will try to keep it under 10 blocks.

So, KnC folks, make sure you update you're firmware and start using the normal ports.

-wk

thanks to everyone that chimed in, ordinateur et all....  it did seem like some manual intervention might of been used recently.. that's all I was saying

is there an old post/link on the KnC firmware/ports issue?    I am running a pretty recent FW so I think I am ok but would like to double check if it is causing any issues.. I rather not go to FW 1.0 since the 99's work so well with OC and all but will if I have to

[Biomech]

I've actually gone through and fixed many of the issues that caused failsafes with CPPSRB.  Since these patches there hasn't been a single CPPSRB-caused failsafe. (Last was 2014-03-28 20:40:04 UTC)

So, after I shutdown the "KnC port" server that can't do normal payouts and only pays the offline wallet (because older KnC firmwares are broken), and fix a couple other minor things, I will do a manual payout again.  Then the queue should stay relatively small for long periods of time and I will try to keep it under 10 blocks.

So, KnC folks, make sure you update you're firmware and start using the normal ports.

-wk

thanks to everyone that chimed in, ordinateur et all....  it did seem like some manual intervention might of been used recently.. that's all I was saying

is there an old post/link on the KnC firmware/ports issue?    I am running a pretty recent FW so I think I am ok but would like to double check if it is causing any issues.. I rather not go to FW 1.0 since the 99's work so well with OC and all but will if I have to

here's the original thread. I didn't find the series of posts about KNC hardware, but it's in there somewhere. Since I follow the KnC drama, and like your posts, I'm pretty sure you're ok.

[DPoS]

I've actually gone through and fixed many of the issues that caused failsafes with CPPSRB.  Since these patches there hasn't been a single CPPSRB-caused failsafe. (Last was 2014-03-28 20:40:04 UTC)

So, after I shutdown the "KnC port" server that can't do normal payouts and only pays the offline wallet (because older KnC firmwares are broken), and fix a couple other minor things, I will do a manual payout again.  Then the queue should stay relatively small for long periods of time and I will try to keep it under 10 blocks.

So, KnC folks, make sure you update you're firmware and start using the normal ports.

-wk

thanks to everyone that chimed in, ordinateur et all....  it did seem like some manual intervention might of been used recently.. that's all I was saying

is there an old post/link on the KnC firmware/ports issue?    I am running a pretty recent FW so I think I am ok but would like to double check if it is causing any issues.. I rather not go to FW 1.0 since the 99's work so well with OC and all but will if I have to

here's the original thread. I didn't find the series of posts about KNC hardware, but it's in there somewhere. Since I follow the KnC drama, and like your posts, I'm pretty sure you're ok.

Thanks bud for putting me on the right track - and was good work on your video review you did as well

edit..  and here is the message from kendog -  Oct Jupiters with .99 is fine, but Nov Jupiters need the latest

https://bitcointalk.org/index.php?topic=23768.msg3906727#msg3906727

[Biomech]

I've actually gone through and fixed many of the issues that caused failsafes with CPPSRB.  Since these patches there hasn't been a single CPPSRB-caused failsafe. (Last was 2014-03-28 20:40:04 UTC)

So, after I shutdown the "KnC port" server that can't do normal payouts and only pays the offline wallet (because older KnC firmwares are broken), and fix a couple other minor things, I will do a manual payout again.  Then the queue should stay relatively small for long periods of time and I will try to keep it under 10 blocks.

So, KnC folks, make sure you update you're firmware and start using the normal ports.

-wk

thanks to everyone that chimed in, ordinateur et all....  it did seem like some manual intervention might of been used recently.. that's all I was saying

is there an old post/link on the KnC firmware/ports issue?    I am running a pretty recent FW so I think I am ok but would like to double check if it is causing any issues.. I rather not go to FW 1.0 since the 99's work so well with OC and all but will if I have to

here's the original thread. I didn't find the series of posts about KNC hardware, but it's in there somewhere. Since I follow the KnC drama, and like your posts, I'm pretty sure you're ok.

Thanks bud for putting me on the right track - and was good work on your video review you did as well

edit..  and here is the message from kendog -  Oct Jupiters with .99 is fine, but Nov Jupiters need the latest

https://bitcointalk.org/index.php?topic=23768.msg3906727#msg3906727

You're one of about three that thought so Thanks, though. It's amazing how much you can forget in three years of not doing video work.

[brox]

It looks like NMC merged mining stopped to work. Last payment I received was from 2014-03-08. BTC mining and payments still work as expected. Anyone has similar issue?

[georgem]

It looks like NMC merged mining stopped to work. Last payment I received was from 2014-03-08. BTC mining and payments still work as expected. Anyone has similar issue?

Really?... just yesterday I signed for the NMC merge mining... and some people claim it doesn't even work?

That would be so sad!

[freebit13]

It looks like NMC merged mining stopped to work. Last payment I received was from 2014-03-08. BTC mining and payments still work as expected. Anyone has similar issue?

There was a bug in some old stats code that allowed some SQL injection to the web stats (fixed here) and someone used it to mess up the web server side copy of the My Eligius data.  The pool servers were in no way affected by any of this.  The web server, by definition, is considered insecure and not able to affect pool operations.  Everything pulled from the webserver (signatures for options) is re-verified on other servers.  So, even if an attacker were actually able to compromise the web server (which they didn't) it wouldn't have any real effect.

The NMC payout code runs on another server, pulls this data, reverifies the signatures, and then pays out the proper amount of NMC.  The issue was that my code for re-verifying the signatures was broken and I didn't realize, so, one set of payouts got messed up and used corrupt data.  I fixed the stats bug, fixed any broken options from the previous day's backup, and am in the process of completely rewriting and testing the NMC payout code.

My time has been extremely limited.  Combine that with battling constant DDoS attacks against the pool for nearly a week now and I hope you can understand why this isn't quite complete yet.  I am working on it, haven't forgotten about it, and it will get done.  Also, when I do make the next NMC payout it will include backpay from the last valid payout (Mar 8th I believe off the top of my head) to the next valid payout.  The pool is still mining NMC for you guys and everyone will be paid their NMC.

No offense to anyone, but I have been ignoring most questions about whats going on about NMC (via PM, email, IRC, etc) just because answering the same question 1000x is a waste of time I should be using to actually work on the problem.

Stay tuned.  I'm hoping to have it done today, but no promises.

-wk

[brox]

It looks like NMC merged mining stopped to work. Last payment I received was from 2014-03-08. BTC mining and payments still work as expected. Anyone has similar issue?

[...]
I am working on it, haven't forgotten about it, and it will get done.  Also, when I do make the next NMC payout it will include backpay from the last valid payout (Mar 8th I believe off the top of my head) to the next valid payout.  The pool is still mining NMC for you guys and everyone will be paid their NMC.
[...]
Stay tuned.  I'm hoping to have it done today, but no promises.

-wk

Thank you, will stay tuned)

[spooderman]

dat round

[baddw]

this pool doesn't seem to payout the way it explains itself..  been watching it like a hawk the past week and seems payouts has a mind of its own

a detail on the mechanics (not the theory) would be useful since it doesn't seem to behave in practice as it is intended... basically it seems all accumulated work gets held ransom regardless of current block luck cycles which in theory should be paying out portions past your pay threshold but in practice it just sits there and says you are going further and further behind as if all your current work is old work that has to wait for super luck to include you .. and that doesn't even seem to trigger it either

it is broken

I am going to attempt here to write a full description of how Eligius pays pool contributors, including a description of both the CPPSRB system and the payment queue.  My goal is something that can be linked or copied and pasted whenever somebody comes with a question like this.  I want to cover a lot of bases and give some solid examples.  Everybody, please let me know if there are any corrections needed.

(EDITED somewhat May 14, 2014 to add examples and minor corrections.)
(EDITED again July 12, 2014 for more minor corrections and additions.)

CPPSRB SYSTEM:
First, some terms.  CPPSRB stands for Capped Pay Per Share with Recent Backpay.  Given the current Bitcoin difficulty, there is an expected number of shares before Eligius finds a block.  Let's call this number N.  A pure PPS (Pay Per Share) system would immediately credit each and every share with exactly 25/N BTC (because the block reward is currently 25 BTC).  This is called the PPS value.  For example purposes, let's say that the difficulty is super low, and the expected number of shares required to find a block is 1000.  Then the PPS value would be 25/1000 = .025 BTC.  *(See below about PPS Systems)

Under CPPSRB, every share submitted goes into a stack.  The Eligius system refers to it as a "shelf" system, but in basic computer science terms, it is a stack.  I.e., it is a LIFO (Last-in First-Out) system, like a stack of plates in a cafeteria.  You can't take out the bottom plate until you have taken out every plate on top of it, and you can't take out the second plate until you've taken out the first plate.  The shelved shares are like this; the bottom (oldest) shares are not paid until all newer shares have been paid.  Each share is "worth" exactly its PPS value, but it might or might not ever be credited to your balance.

Each time a block is found, the system immediately awards the top N shares in the stack, and each of them is credited with its PPS value; 25/N BTC is credited to the account associated with each share.  In this way, it is somewhat like a PPLNS (Payment Per Last N Shares) system.  **(See below about PPLNS Systems) However, it differs from PPLNS in that once a share is credited, it is removed from the stack permanently.

So let's say that N is still 1000 shares, i.e. we expect to find a block every 1000 shares.  (I'll keep the values low here just to keep things simple.  Multiply by some billions to get the actual numbers.)  Shares are added to the top of the stack as soon as they come in.  First round, the pool finds a block at 1200 shares; longer than expected.    So the newest 1000 shares of that round are credited with their PPS value, and the oldest 200 shares are kept on the stack.  The next round starts, and the incoming shares are added to the top of the stack as they come in.  This round, the pool finds a block at 600 shares; faster than expected.  Since these 600 shares from this current round are  the most recent and therefore on top of the stack, they are credited first and removed from the stack.  Since 600 is 400 less than N, the next 400 shares in the stack are paid out.  These 400 shares are all from previous rounds.  This includes the 200 shares that were put there in the last round.  The next 200 shares in the stack will then be credited, from whenever they were accumulated.

If the pool were ever to empty the stack (which would require extraordinarily good luck) then the pool would save the BTC earned for future bad-luck times.

So, you accumulate credits in your account in this way.  This is the first stage.  The next stage is the payout queue.  

PAYOUT QUEUE:
You can enter the payout queue once your account balance reaches its threshold, which can be set manually.  Once you hit your threshold, you are entered into the payout queue.  The queue is just that: a queue, not a stack.  It is generally not FIFO or LIFO like the CPPSRB system.  Instead, your position in the queue is determined solely by when you were last paid out.  If you were last paid out 36:00:00 hours ago, you will be ahead of anybody who was last paid out 35:59:59 hours ago, or more recently.  So your position in the queue will change all the time, as the payout queue is reduced (when blocks are found and people are paid out) or when the queue ahead of you gets bigger (because people who have not been paid as recently, have hit their threshold and entered the queue ahead of you).

In setting your payout threshold, you have to weigh the benefits of making it long or short, relative to your hashrate.  If you set it to be paid more frequently, your payouts will be very inconsistent as there will constantly be people jumping the queue ahead of you as they hit their thresholds.  It can be quite discouraging to be close to the front of the payout queue, and then for some whale to hit their threshold and their payments will be 150BTC or something, consuming the next 6 blocks and putting you 6 blocks further back in the queue.  On the other hand, if your threshold is set high, so that you are paid out (say) once a week, you will generally be at or near the very front of the queue every time you hit your threshold.  

So there is a definite trade-off: setting your threshold high (longer time between payouts) means less variance in when you actually receive your payouts; they should come very consistently on schedule.  The downside to this is that obviously you will receive payments less frequently.  However, setting your payout threshold very low means that while you will generally receive payments more frequently, there will sometimes be great variance in when you get paid out.  It seems that the typical choice is to set it to pay out approximately once every day, or 24 hours.  If you set your threshold to hit roughly every 7 days, you are fairly well assured of being paid out in a very timely manner on that 7-day schedule.  If you set your threshold to hit roughly every 12 hours, your payments could frequently be delayed by 24, 48, even 72 hours.  More frequent = more variance, less predictable; Less frequent = less variance, more predictable.

It is important to note that as your unpaid balance grows, the amount that you will receive in your next payout grows as well.  Just because you hit your threshold doesn't mean the system stops crediting your shares; and the system will pay out the full owed amount (as of the previous block) whenever you come up to the front of the queue.  So say you have your threshold set to pay you out roughly every 24 hours, which is equal to ~0.1 BTC given your hashrate.  Somehow there is a backlog in the queue, and you don't actually get paid for 48 hours.  When that payout occurs, you will be paid out ~0.2 BTC.  The next time, it takes 36 hours for you to make your way to the front of the queue, so you are paid out ~.15 BTC.  So your payment per mining hour will be consistent, but the payments might be inconsistently spaced.

Payouts are typically handled in the coinbase transaction when the block is mined.  This means that the coins are mined directly to your mining address, and the pool never holds the coins in its wallet addresses.  However, sometimes something gets screwed up, and the CPPSRB system goes into failsafe mode, and mined coins from the affected blocks are sent into Eligius's cold wallet until they are paid out in a manual payout by wizkid057.  This can happen due to an orphan block, or sometimes when Eligius finds a block very quickly and has not yet had time to calculate the proper coinbase transaction to pay the block to miners.  (It does this because, every time when a block is found, Eligius quickly sends a quick-and-dirty block to all miners, because it would be a shame to waste any extra seconds of hashtime.  After the proper payout has been calculated, new work is sent to miners which include the proper payout in the coinbase transaction.)


*Continuing with this example, a pure PPS (Pay Per Share) based mining pool would just automatically credit you with .025 BTC for every share you submit.  Such a pool would pay you out of its own BTC balance, and it would be set up such that hopefully the pool would never run out of BTC to pay you with.  You could withdraw your BTC earnings at any time from such a pool, because the BTC would be credited to you with each share.  It is important to note that the pool would continue to pay you for each share, regardless of whether blocks are actually found.  This is why pure PPS pools usually charge high fees, in the 5-10% range.

**A PPLNS (Pay Per Last N Shares) system will double-pay some shares some of the time (when the round is shorter than N shares, it will double-pay the more recent shares from the last round), and discard shares some of the time (when the round is longer than N shares, any shares older than N are discarded and never paid).  CPPSRB never discards shares, so you can potentially have earnings from shares submitted long in the past.

[RicRock]

I wish Wiz and everyone that takes the time to explain how the pool works received .01BTC for every-time someone has to explain it.

Hell, I wish I got paid for every other post were someone comes in saying it doesn't work only to have someone take the time to explain it AGAIN.

You all have WAY more patience than I do.

Stay Gold, Ponyboy.